0
votes

I'm trying to update a cloud service deployment on azure. I can deploy fine to a test cloud service. However, when I try to deploy to our production cloud service's staging slot the publish to azure from visual studio completes with no errors but in azure I don't see the new deployment in the staging slot.

I have verified that it deployed to the staging slot instances because I can Remote Desktop into each of the servers and see the new code in IIS.

The only errors I see are on the servers, where there are IIS event warnings regarding:
The application / belonging to site xxx has an invalid AppPoolId.
Site xxx was disabled because the root application defined for the site is invalid.
A process serving application pool xxx terminated unexpectedly.

Sure enough, when I browse the website the old site is running and not the new one.

Greatly appreciate any pointers!

1

1 Answers

0
votes

Making sure we are on the same page... - if you RDP into the staging deployment, you can verify that new code has been published - when you browse to the website, you see the old code.

A couple of things to check... When you say 'browse to the website', do you mean you attempted to reach the website via (1) a custom domain that points to the xxxxx.cloudapp.net, (2) directly at xxxx.cloudapp.net, or (3) {some long guid}.cloudapp.net?

Did you attempt to perform a VIP SWAP, and if so, when you click on SWAP, does the portal correctly reflect the date and time that the staging was deployed?