I've recently tried to upgrade my WebRole from Azure SDK v1.6 to v1.7. This appears to have worked OK. I can build and run the role in my devfabric just fine. When I try to deploy the upgraded project to the real cloud, the instances never start. They just sit in the "busy" state. Interestingly, they don't do the typical "recycle loop", they just sit at "busy" forever.
When I log into the instances with RDP, I see the following error in the event logs:
The application '/' belonging to site '1' has an invalid AppPoolId 'DefaultAppPool' set. Therefore, the application will be ignored.
Site 1 was disabled because the root application defined for the site is invalid. See the previous event log message for information about the root application is invalid.
Looking in IIS manager confirms that there is no AppPool called "DefaultAppPool". There also are none of the typical AppPools with GUIDs for names that Azure creates. Unsurprisingly, none of my sites exist either.
So how do I resolve this?
How are you deploying? Are you doing it through azure management portal?
Are you doing in place upgrade?
I see from the error that the app pool is corrupted for some reason. Please try to deploy from scratch.
if you doing in place upgrade, can you please try deploying from the scractch?
Please mark the replies as Answered if they help and Vote if you found them helpful.
- Proposed as answer by Veerendra Kumar Thursday, August 09, 2012 1:01 PM
All my testing has been deploying from scratch. I've had mixed results with upgrades in the past, so I don't even try it anymore.
I've been doing the builds on my desktop machine, using the right-click -> Package command. Then I upload the generated files through the manage.windowsazure.com portal.