Geek Answers Handbook

Stunning Cloud Cloud Service Deployment

I have a very strange problem with deploying the azure cloud service. I have 1 web role with 5 instances and 1 cache role with two instances.

When I deploy my MVC 5 WebRole from the Azure portal, the deployment starts from the first web instance, then it tells me that the “Role cannot be started” due to an error and stops processing other instances. I did RDP for the failed instance, and indeed the MVC application gives an error message that it cannot find a specific file like "Layout page" ... "cannot be found in the following path", although a view in the specified path exists. So I did iisreset and the application worked. after I manually fixed the problem, the deployment continues to the next instance, and the failed instance becomes "Ready."

Does anyone have an idea why things aren't rolling out smoothly or why iisreset is needed?

This is relatively recent, about a month.

My environment:

  • .NET Framework 4.5.1
  • MVC 5
  • Azure SDK 2.4 for VS 2013

Thanks for the help.

+4
source share
1 answer

FINALLY!! I found the problem and fixed it.

I had local storage resources for storing temporary files and local file caches for certain components and was configured to reset when the role was restarted. One of the components (Lucene.NET for azure) was to lock files in this local storage, which caused the deployment problem that IIS needed to reset in order to release the lock.

I configured the component to cache files in the Windows temp repository instead of a local resource, and everything worked out.

+1
source

More articles:


All Articles