2
votes

I have a deployment that was working successfully previously. Since then I have upgraded to the June 2012 SDK and when I deploy it is continually recycling. If I remote desktop into the instance i can open the application manually and it runs (no yellow screen of death), so there must be something about the deployment.

In the event viewer I see the error:

Faulting application WaHostBootstrapper.exe, version 6.0.6002.18488, time stamp 0x4fcaabe9, faulting module ntdll.dll, version 6.0.6002.18520, time stamp 0x4e811810, exception code 0xc0000008, fault offset 0x00000000000b6ff8, process id 0x%9, application start time 0x%10.

But this isn't particularly useful. I have totally recreated the Cloud project with SDK 1.7. It is a ASP.NET MVC 4 RC application.

What can I do to see the exact reason for this error?

2
Are you running on a Server 2008 instance or 2008 R2 instance? We had issues with our MVC app and server 08 -> changes to 08 R2 and never had another problem. Neither config gave us issue on the local emulator during this time.Tommy
It is 2008 SP2 currently. I will try on R2 and see if it makes a difference.Craig
Yeah let me know. Since I do not know the specifics of why/how this worked for us, I didn't want to post as an answer.Tommy
I changed to R2 but no difference.Craig

2 Answers

2
votes

Based on your statement "I have totally recreated the Cloud project with SDK 1.7. It is a ASP.NET MVC 4 RC application.", I am not sure if 1) you are really using MVC4.0 RC bits or 2) you are using MVC 4.5 BETA bits. MVC 4.0 is already released and installing June 2012 SDK actually installs ASP.NET MVC 4.0 based Cloud Template and binaries, so you must be using release bits of MVC 4.0 with Windows Azure Cloud Project. If you are using RC bits, this could be your first problem.

I have seen the exact same error in past and described the reason and a potential fix for such problem in my blog: Windows Azure Web Role Error: "Faulting application WaHostBootstrapper.exe

I believe your package does not have necessary DLL so please check which DLL are missing in your deployment and redeploy your application to solve this problem.

Also if you want to run your application with Windows Server 2008 R2 as default, you can modify osFamily=2 (1:Windows Server 2008 SP2, 2:Windows Server 2008 R2) setting in your ServiceConfiguration.cscfg as below to configure at deployment:

<ServiceConfiguration 
    serviceName="<service-name>" 
    xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration" 
    osFamily="2" 
    osVersion="*" 
    schemaVersion="2012-05.1.7">
1
votes

I had the same issue after upgrading to v1.7, but upon looking at the Windows Azure logs in the Azure VM I noticed the following exception:

An unhandled exception occurred. Type: System.ArgumentException Process ID: 2340
Process Name: DiagnosticsAgent
Thread ID: 1
AppDomain Unhandled Exception for role Backend_IN_0
Exception: Endpoint http://xxxx.blob.core.windows.net/ is not a secure connection.

So I changed the Diagnostics connection string to use https instead of http and voilá, that solved my problem.

Hope that works for you, I've been pulling my hair off for two days.