Home/ Questions/Q 6023211
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T03:58:16+00:00

I am trying to start up a web role on Windows Azure, but it

  • 0

I am trying to start up a web role on Windows Azure, but it initializes, goes to busy/stop and continues the endless loop of busy then stop. I have followed the recommendations of this question : Windows Azure Deployment but still no joy. Of course the application runs nicely in the development fabric when I debug

 I have done these things so far:
  • Turned off the diagnostics to ensure azure storage is not used
  • Made sure that copylocal=true is set for each no microsoft assembly.
  • Added the Microsoft.WindowsAzure.* references that the sample web role adds
  • Did a test run of the basic MVC role and that works.
  • Did a dependency analysis to make sure I am explicity referencing all assemblies using this tool Dependency Visualizer and that they are in the package for deployment. no joy.

Is there a startup log that azure keeps that I can access or similar facility so that I can learn what is failing?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Do you have access to Intellitrace? If you turn that on (VS Ultimate SKU), you can easily download the logs and see why the role is failing to start. Windows Azure Diagnostics is almost certainly not the issue anymore. Back before SDK 1.3, it used to run in the same process as your RoleEntryPoint, which meant you a.) could crash your role if it crashed and b.) if your role crashed, it killed the monitor which made it useless for collecting information. However, the Diagnostics Monitor is now deployed as background task that runs outside of your RoleEntryPoint and it can no longer crash your role. If you turn on Crash Dump collections and Tracing and you should be able to pick those up. In theory your Crash Dump should have the stack trace.

    • 0