Geek Answers Handbook

Azure roles - bike - WaHostBootstrapper.exe error, ntdll.dll module error

It drives me crazy: we have a Windows Azure cloud service with an ASP.NET MVC 3 project. There have been a lot of changes lately, so we have to deploy it every few days.

Sometimes (for example, now) we stick to the following deployment error:

Role instances recycled for a certain amount of times during an update or upgrade operation...

manage.windowsazure.com tells us that instance 0 of our deployment deployment does not matter:

 Recycling (Role has encountered an error and has stopped)

However, instance 1 is fine, the web services on instance 1 are running , so the reason for the error is not our code .

We performed RDP on the instance and reviewed the application event log, which displays the following error several times:

 Faulting application name: WaHostBootstrapper.exe, version: 6.0.6002.18488, time stamp: 0x505cf7da Faulting module name: ntdll.dll, version: 6.1.7601.17696, time stamp: 0x4e8147f0 Exception code: 0xc0000008 Fault offset: 0x00000000000d4995 Faulting process id: 0x970 Faulting application start time: 0x01ce474976d706d2 Faulting application path: E:\base\x64\WaHostBootstrapper.exe Faulting module path: D:\Windows\SYSTEM32\ntdll.dll Report Id: c26d8be8-b33c-11e2-a9be-00155d3ab8c9

When that happens, we

  • Redisplay instance
  • Reload instance
  • Deployment again
  • Create a support ticket

A few hours later, everything works again. We have not changed anything in the deployment, it just works again, as before . While Microsoft Support is reacting, everything is fine again, so we cannot show them the problem.

It is so funny and frustrating. We lose days of work just because of this stupid mistake.

Does anyone else have these problems? Any ideas how we could stop this?

+4
source share
2 answers

Check the following:
1. You have the latest Azure SDK and your solution uses the correct dll links. For example, make sure that if you have v2.0, all links use the same version. If not, recreate.
2. All links (including packages and own libraries) are activated using "Copy local" = True, and they are included in the package box.
3. If you use storage, check the connection strings and the validity of the keys.
4. Check if the service setup has the correct osFamily and osVersion that you are aiming for.
5. If all else fails, try intelliTrace .

+4
source

for such problems we found http://blogs.msdn.com/b/kwill/archive/2013/10/03/troubleshooting-scenario-7-role-recycling.aspx to be a good debugging resource.

+2
source

More articles:


All Articles