Struggling through the migration of a 4.61 site I have now managed to almost get through the migration workflow.
However, it now fails after having created missing template files, with these messages:
[2008-09-23 09:43:34][Information] MissingTemplateFileCreator: Adding new template files to csproj file.[2008-09-23 09:43:34][Warning] MissingTemplateFileCreator: No csproj file.[2008-09-23 09:43:34][Information] Finished creating missing template files[2008-09-23 09:43:36][Information] Migrating links[2008-09-23 09:43:50][Warning] Failed to migrate links:[2008-09-23 09:43:50][Warning] System.Net.WebException: The remote server returned an error: (500) Internal Server Error. at System.Net.HttpWebRequest.GetResponse() at EPiServer.Migration.SiteRequestSupport.MakeSitePostRequest(Uri url, String postData) at EPiServer.Migration.MigrationWorkflow.MakeConvertLinksRequest()[2008-09-23 09:43:50][Warning] Failed to convert links therefore migration is stopped. Check that target site is running and then run migration tool again and choose continue existing process.
Should I perhaps add an empty csproj file in my target (cms 5) site?
Further: If I run the migration wizard again, it gives an option to continue migration. (since it finds the SavedMigrationState.migration file in the same directory as my original site) However,this gives teh error "Validation of migration state file failed"since the web server returns an 500 error. This is of course since the original site is no longer functional. It has 4.62 binaries, but now (after the migration script) points to a 5.1 database.
How do I get around this? If I restore my 4.62 database to a new instance, and point te old site to that one, the migration wizards wants to convert that database as well... Hardly what I have in mind.
Finally, the Migration wizard did something funny with the folders in both the original and target web sites.
For example the /bin folder is displayed as "[20 " instead of "bin" in both the iis manager andwindows explorer. (Though the folder name is not changed, in the adress bar for example, or if I press f2 to rename it, it is still "bin")
There is a bug in current download . check if you got duplicated location path in your web.config. i.e two
remove them then you could try the option "continue migration"
The Migration tool only validates that the target site is running (that is the CMS 5 site), so in your case you have probably run into the issue Ruwen wrote about. Try browse to your CMS5 site directly in browser and you might get more information about the 500.
After fixing the site so it is running you should be able to continue the migration (due to the bug Ruwen pointed out you should though remove all location tags from web.config that refers to location served by VPPS before contining migration)
I have a similar problem:
[2008-10-06 09:37:06][Information] Migrating files...[2008-10-06 09:37:06][Information] Converting native filesystem with root '~/upload/' to versioning filesystem[2008-10-06 09:37:09][Warning] Failed to convert filesystem ~/upload/, reason:[2008-10-06 09:37:09][Warning] System.Net.WebException: The remote server returned an error: (500) Internal Server Error. at System.Net.HttpWebRequest.GetResponse() at EPiServer.Migration.SiteRequestSupport.MakeSitePostRequest(Uri url, String postData) at EPiServer.Migration.FileSystemHandler.MakeConvertFileSystemRequest(String sourceLocation, String targetLocation, String vppRoot)[2008-10-06 09:37:09][Information] Finished converting filesystem '~/upload/'[2008-10-06 09:37:09][Information] Converting versioning filesystem with virtualName 'Documents'[2008-10-06 09:37:10][Information] You can now remove old versioning filesystem located at 'C:\Inetpub\wwwroot\SvNatet451\docrepository\'[2008-10-06 09:37:10][Warning] Failed to convert filesystem therefore migration is stopped. Check that target site is running and then run migration tool again and choose continue existing process[2008-10-06 09:37:10][Information] Migration stop requested[2008-10-06 09:37:10][Information] Migration stopped
During the migration some parts of the migration requires a web context, therefore the migration tool calls in to the CMS 5 site to let it do some of the migration work.
In your case there is some error on your target CMS5 Sp2 site, probably some failed config change done by the migration tool.
Try to make an request for the given siteUrl that you have in your CMS5 SP2 web.config file in an ordnary browser and you can proably get a more detailed explanaition on what's wrong. You might also change the attribute mode on element customErorrs to "Off" in web.config to get a more detailed error message.
After you have got your CMS5 site to work you should be able to start the migration tool again and select "continue existing process" and it should start where it left off.
(By the way: We are planning to relase the Migration tool soon, and in the release version we also support migration of external users/roles)