Initialization - Busy - Stop "problems with LOOP when deploying Azure

Question

I am trying to deploy an azure cloud application on Windows Azure. Application Specifications →

• It has one WebRole application - ASP.Net MVC (this MVC application uses the ASP.Net chart control)
• It does not contain any working role.
• Third-party links are set with the attribute "Copy Local" to "true" (MVC, ASP Charting and ASP Provider DLL).
• There is no DiagnosticsConnectionString in the service configuration file
• It uses an ASP provider to manage session state.

This application runs successfully in the local dev structure, but when I try to deploy it on Windows Azure, it gets stuck in a loop with a status that changes between initialization, busy, stop states. He never goes into a READY state. There seems to be no ERROR logs to convey deployment issues to the user.

So, is there a way to diagnose deployment problems? Is there any way to get ERROR logs for deployment?

Any help would be appreciated.

Thanks Kushal

Answer 1

I had a similar problem a few weeks ago, so maybe you can use what I found out:

Remember that only assemblies that are directly related to your web role will be included in the deployment package. This means that if the project MySolution.WebRole1 refers to a project called MySolution.ServiceLayer, which, in turn, refers to a third-party assembly ThirdParty.SomeAssembly.dll, then this assembly will not be included in the package. In this case, you need to add the link to MySolution.WebRole1 in ThirdParty.SomeAssemlby.dll.

EDIT . As for diagnostics: if you haven’t done this yet, you can take a look at the Windows Azure Platform Training Kit - the December update . It contains a lab exercise called "Deploying and Monitoring Applications in Windows Azure."

Answer 2

Directly referencing the necessary assemblies is really what you need to take care of. But if your third-party dll has different versions for x64 platforms, you also need to make sure that you have enabled the correct version of the assembly as the Azure role in x64 instances. That was the problem I experienced.

Check this post for more information on how to do this. There is also great information here about what might cause a loop in your Azure deployment.