Azure post questions - Busy - Restart - Busy - Cycling

Question

Azure gives me a headache.

I started with a textbook. Created a new MVC 3 project. Took about 9 minutes, then it worked perfectly on my production VM.

Then I tried to publish the project I was working on (MVC 3). It has the following dependencies:
Service.dll
Domain.dll
Autofac.dll

It works great when I debug using emulator.
It works great when I unzip a package and deploy it to another server.

But when I publish to Azure Production, I get the following:
1:42:31 PM - Preparing the deployment for a site with a subscription ID: ...
1:42:31 PM - Connecting ...
1:42:35 PM - Verifying the repository account "..."

1:42:38 PM - Downloading the package ...
1:44:46 PM - Creating ...
1:45:56 PM - Deployment ID Created: ....
1:45:56 PM - Launch ...
1:46:34 PM - Initialization ...
1:46:34 PM - Instance 0 roles Site is in an unknown state
1:46:34 PM - Instance 1 roles Site is in an unknown state
1:47:06 PM - Instance 0 Roles Site Creates a Virtual Machine
1:47:06 PM - instance of 1 role. The site creates a virtual machine.
1:47:37 PM - Instance 0 Roles Website Launches Virtual Machine
1:47:37 PM - Instance 1 Roles Site Launches Virtual Machine
1:50:13 PM - Instance 0 roles Site is in an unknown state
1:50:13 PM - Instance 1 roles Site is in an unknown state
1:50:44 PM - Instance 0 roles Site busy
1:50:44 PM - Instance 1 roles Site busy
1:54:31 PM - instance of 1 role The site is rebooting
1:55:02 PM - Instance 1 roles Site busy
1:56:40 PM - Instance 1 roles Website on a bike
1:57:43 PM - Instance 0 roles. The site is cycling.

I have tried many times. Without success.

Update

I forgot to mention that I have a C # sdk facebook library

I used the trial version and error to detect that the Facebook.Web.Mvc dll was causing me problems. It was included in the bin folder, but still nothing good.

Answer 1

There are no MVC 3 assemblies in the Azure environment. You need to make sure that you reference all of them in your project and set CopyLocal = true so that the assemblies are included in your Azure package. Azure will go through this endless cycle if it cannot find all the dependencies for your project.

The links you need to specify:

• Microsoft.Web.Infrastructure
• System.Web.Helpers
• System.Web.MVC
• System.Web.Razor
• System.Web.WebPages
• System.Web.WebPages.Deployment
• System.Web.WebPages.Razor

One blog I also mentioned the need for WebMatrix.Data , but I found that I did not need this in my project.

If you have other assemblies that you reference that are not part of the .NET Framework, you will also need to set CopyLocal = true.

Also, make sure that the Azure storage option is not set to "Use development storage" when deploying to Azure - this will cause the same problem.

If the above does not solve the problem, check this site for a number of other possible reasons.

Answer 2

As Brian Rogers notes the asp.net MVC build requirement and points to a good resource for role-cycling reasons. One additional thing can help with MVC on purpose. You can right-click on the Proejct web application and select "Add Deployable Settings", and then select ASP.NET MVC3. This ensures that all MVC3 required for the build will be associated with your project when it is disabled.

Answer 3

Set the link attribute "copy local" to "true" for each link used in the project. It worked for me.

Answer 4

I had a similar problem after updating my project to use the Azure.NET SDK version 2.0.

The upgrade procedure changed the configuration files, but did not update the versions referenced by the projects. I solved this by manually deleting links to older versions 1.8. * DLL, and then adding links to 2.0. version.

Answer 5

Please check for any third-party DLLs that were created only for 32-bit or 64-bit in your solution. These types of DLLs have caused recurrence and employment.