Web Deploy migration stuck at "Updating applicationDefaults"

Mark Allen
Mark Allen used Ask the Experts™
on
Web Deploy stuck

I am currently migrating one of our web servers using Web Deploy. The command used is shown below.

msdeploy.exe -verb:sync -source:webServer,computername=computername -dest:webServer -enableLink:AppPoolExtension >log.txt

Open in new window


The above command worked as expected for a previous migration, bur during the current migration it seems to hang.
I've noticed the folder structures are created successfully, the sites and application are created, but no files were copied over.

I then tried the following command with the same results
msdeploy.exe -verb:sync -source:webServer,computername=sp-web02 -dest:auto -enableLink:AppPoolExtension >log.txt

Open in new window


The migration seems to be stuck at "Updating applicationDefaults"  I've attached the log.  log.txt

It is also important to note that on the source server the bindings defines the allocated IP address.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Author

Commented:
Okay, I take that back it just took forever to sync (the site size to 325 gigs, mainly photos), and apparently, it wrote to a payload file in my temp directory, I was unaware of this.

Now that it has completed I cannot connect via IIS, nor can I launch Server Manager.
Chinmay PatelChief Technology Ninja
Distinguished Expert 2018

Commented:
Hi Mark,

This does not look very practical to me. I have seen Visual Studio collapsing in situations where there are too many files. What exactly these 325 Gigs data is? Is it actually needed by the Project? or those images can be kept separately and your project will still be able to run?

Regards,
Chinmay.
Hi Chinmay,

I completely agree, and that has been my argument as well. This application is our in a house ERP solution. We have discussed moving the photos to a cloud platform, but this has not been visited as of yet. Photos and, PDF files consume hundreds of gigs of space.

I was able to work around the crash by replacing the machine.config file from a working 2016 server and the applicationHost from the original machine. I then set the default application pool to .NET 4.0 and ran webdeploy again. This time it was successful.

It appears that if your migrating sites from an older OS with the default application pool set to .NET 2.0 it will cause serious issues once migrated. Hopefully, this helps someone in the future if they run into this problem.

Things to note:
  • Large migration with multiple smaller files will take an extended amount of time (monitor payload files in your temp directory)
  • Always set your default application pool to .NET 4.0 before migrating your site or sites.

Author

Commented:
Thank you for your response Chinmay
Chinmay PatelChief Technology Ninja
Distinguished Expert 2018

Commented:
Glad we came to the same conclusion. One of my colleague burnt his hands by trying to pack 17,000 files(very small, docs, Visios, Gifs,Jpgs - but 17,000 is the magic number) back in 2007. It backfired so badly. It was fun troubleshooting it though. :)

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial