« Previous Next »

• 02-12-2008, 10:04 AM

  alexthissen Joined on 02-12-2008, 2:33 PM The Netherlands Posts 5

  Exceptions during migration from IIS6 to IIS7 Reply Contact Hi, For a customer of ours we have used the msdeploy tool to try and migrate 4000+ ASP websites running under IIS6 to IIS7. msdeploy and the remote agent were installed on the source IIS6. On the destination IIS7 machine (Windows Server 2008 RTM) we installed only the msdeploy and not the remote agent. Issue 1: From the destination IIS7 machine we ran the following command-line: msdeploy -whatif -verb:migrate -source:webServer60,targetName=http://192.168.0.167/MSDEPLOY -dest:webServer60 just like the document "Migrating an IIS 6.0 Web Server Remotely" specifies. Running the command resulted in 2 stack dumps for an "Object reference not set to an instance of an object" NullReferenceException (stack dump is available if necessary). After that both the local msdeploy.exe and the remote wdagent.exe seemed to stop working. They were at 1.597 MB (1.6 GB) and 556 MB private memory respectively. Additional question: why do we need to specify the -dest:webServer60 when migrating to IIS7? It seems counter-intuitive. Issue 2: Our next attempt was to migrate a single Web site by running: msdeploy -whatif -verb:migrate -source:metakey=lm/w3svc/1154,targetName=http://192.168.0.167/MSDEPLOY -dest:metakey=lm/w3svc/1154 This seemed to work, because the tool managed to complete succesfully. However, running the command for real (without -whatif) caused a fatal error: Fatal: Sync operation 'Update' failed with destination filePath (C:\inetpub\wwwroot\{removedsensitiveinfo}\images\bedr_hoekje1.gif) Fatal: String was not recognized as a valid DateTime. First this happened on the SmartNav.htm file in the aspnet_client. Since we have an ASP website we removed the folder, which gave the same error on a different file. We have a log file available if this would be helpful. Any help would be appreciated. Thanks, Alex

  Tags: exceptionmsdeployfatal

• 02-15-2008, 11:38 AM

  In reply to

  ksingla Joined on 06-14-2006, 3:02 AM Redmond, WA Posts 863

  Re: Exceptions during migration from IIS6 to IIS7 Reply Contact Hi Alex, Thanks for reporting these issues. Regarding use of webServer60 on IIS7, this was done so that we don't hardcode special logic between different providers. We require that both source and destination (with the exception of archive) providers should always be same. Also as you would guess, migrate from 6 to 7 uses ABOMapper on IIS7 box, use of webServer60 for migrate scenarios felt right. If you use the tool to do a IIS7->IIS7 sync, you should use webServer instead which doesn't go through ABOMapper. Issue1: Is it possible to send us the stack dumps both for wdagent and msdeploy? Memory usage of the tools is a known issue and we are working to address it. Issue2: Can you pls send us the dump of files which are giving this error and also stack dumps when you are hitting the issue? You can use -debug switch in the command to get the full stacktrace. Use "-verb:dump -source:filePath=<pathtofilegivingerror> -xml" to produce xml dump of file. Log will be super helpful. If you can send that to ksingla@microsoft.com, that would be great. Thanks, Kanwal Follow me on twitter at http://twitter.com/kjsingla

• 02-18-2008, 3:46 AM

  In reply to

  Arthur Wijnschenk Joined on 02-18-2008, 8:44 AM Posts 1	Re: Exceptions during migration from IIS6 to IIS7 Reply Contact Alex,  Make sure your the date / time setting in all the tabs under regional / language settings in the control panel do match the settings of your source server.  Arthur

• 03-20-2008, 7:25 PM

  In reply to

  faith_a Joined on 06-02-2004, 4:40 PM Posts 109	Re: Exceptions during migration from IIS6 to IIS7 Reply Contact Hi Alex, Just checking if the second issue got resolved or you were able to send the dumps? Please let me know and feel free to send them to me directly. Thanks, -faith This posting is provided "AS IS" with no warranties, and confers no rights.