Role instances are taking longer than expected to start. Do you want to continue waiting?

Question

I installed the windows azure 1.4 sdk and tools on my new 64 bit machine. win7. VS 2010 ultimate. storage emulator and compute emulator are running but still not able to run any of my azure project. neither worker, web or wcf role. geting error aas under. i follow this but no luck. please help urgent.

---------------------------

Microsoft Visual Studio

---------------------------

Windows Azure Tools for Microsoft Visual Studio

Role instances are taking longer than expected to start.  Do you want to continue waiting?

---------------------------

Yes   No   

---------------------------

Answer 1

I uninstall and reinstall VS sdks but nothing helps.

Please anybody show me right way?

Answer 2

I also keep on facing this issue off and on. Sometime saying "yes" to continue a couple of times solves the issue. And sometime need to rebuild the solution.  Sometime it seems to be for genuine reason but sometime it seems to be a bug.

You can try deleting <Sites> section from ServiceDefinition.csdef file in case you are not using full IIS capabilities. 

You can also try out different things from the below thread:

http://social.msdn.microsoft.com/Forums/en-US/windowsazuredevelopment/thread/9991a152-ca15-416c-bcc3-a507884f5964/

--Parkash K.

Answer 3

Remove the <sites> section too but no success. on the sdk download page it has been written that this problem has been solved. but it still exist. 

Answer 4

Hi Munish,

I understand that you installed the windows azure 1.4 sdk but are still experiencing the "Role instances are taking longer than expected to start." issue.

I found a blog that discribes this issue and also the workaround. Here is the quotation from Azure sdk 1.3 "Role instances are taking longer than expected to start." bug still exists in 1.4 and I'll tell you why.:

On Start Debugging the following errors always occurs:

The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

And

Role instances are taking longer than expected to start. Do you want to continue waiting.

1)Exit Both Azure Emulators, clean solution, and redeploy

2)If your project is under source control and your web.config is readonly, make it writable.

Or

Add this to your Post-build event command line in your project properties.

attrib –r $web.config    

…Case sensitive

3)Enable enableNativeCodeExecution in the ServiceDefinition.csdef

4)Made sure only one web role in solution.

5)Made sure only 1 instance count is set.

6)Double checked Copy Local on assemblies

7)Ensure WCF Activation is enabled

8)Run visual studio in administrative mode

9)After running, open iis, and make sure directory browsing is enabled

   Apply network service permissions to root folder which allows azure to dynamically enable directory browsing in iis on vs dev fabric start.

10).net full trust in iis

11)Checked cloud project  .net framework version

12)make sure your cloud project is the start up project

13)make sure your website properties has a start up page set

14) waiishost.exe 60second time out

#14 Solution)

Delete the <Sites> section from ServiceDefinition.csdef and the emulator reverts to using the Hostable Web Core (HWC) rather than Full IIS, and the timeout is avoided.

You might have a try and see if it could resolve your problem.

Thanks,

 

---

Wengchao Zeng
Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact [e-mail].
Microsoft One Code Framework

Answer 5

Hi Zeng,

It looks my career with windows azure is finished. I lost one of my client for this. two of my machine are showing the same exceptions. i tried everything you suggested but i have no luck. I am now very frustrated now with microsoft. if there if bug in sdk then what is the need of new release. neither of my azure project is working.  

Answer 6

You might try removing the Diagnostics module from the Service Definition file. I have occasionally encountered problems with the Diagnostics Monitor not starting in a timely manner causing the roles are taking too long to start error. This is not a great solution - and, to be honest, I have no idea why it should happen.

Answer 7

Hi Munish,

I am very sorry to hear that.

Windows Azure is a new project which will excite us. Micorsoft is working hard to improve it.

Since your local environment is unique, causing that we are hard to reproduce the issue on our side, we would give possible solutions to you instead of the exact solution/walkaround. If the issue is still not resolved, I would suggset you directly contact our azure support team via http://www.microsoft.com/windowsazure/support/. That will allow the issue to be tracked and escalated.

Before contacting the support team, may I ask you to try the following steps:

1. Try again and ensure deleting Sites section does not help solve the issue. See http://blogs.msdn.com/b/windowsazure/archive/2010/12/02/new-full-iis-capabilities-differences-from-hosted-web-core.aspx for why this workaround may work.

2. Keep the Sites section, when you start the debugging and the dialog shows up, please don't click any button. Open IIS manager, check if there is a new site with name like "deployment(440).WindowsAzureProject4.WebRole1.0_Web" or not. If the new site exists, please select the site and click "Browser domainname on *:5100 (http)" button in the right pane. And the site will be opened in the browser, showing the actual error in IIS. Please show us the error and we will assist you.

Thanks,

 

---

Wengchao Zeng
Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact [e-mail].
Microsoft One Code Framework

Answer 8

Neil I try the trick suggested by you but again same result with long waiting message again and again.

Zeng I tried the your second point but there is no site created in IIS till the message appear.

Also i find one disaster my neither on WCF service is working in VS2010 is not working.

Service throwing exception "Exception of type 'System.ExecutionEngineException' was thrown"

What is happening with me. 

Answer 9

Do you have any Startup tasks? I've seen this happen when a task fails to execute.

 

Also, try opening the Compute Emulator UI and looking at the console window. If the console window is tiny you can expand it to full size by clicking the little round "i" icon in the upper right. See if there's any information in there.

 

If it shows that the role is continually stopping and starting again, then you have some problem in your startup process.

Answer 10

Brian the role is showing the busy status not stoping and starting. here is complete log at the compute emulator

[fabric] Role Instance: deployment(121).WindowsAzureProject1.WebRole1.0

[fabric] Role state Busy

[Diagnostics]: UpdateState(Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorStartupInfo, Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorConfiguration, )

[Diagnostics]: Acquired mutex

[Diagnostics] Information: C:\Users\Munish Bhargav\AppData\Local\dftmp\s0\deployment(121)\res\deployment(121).WindowsAzureProject1.WebRole1.0\directory\DiagnosticStore\Monitor

[Diagnostics] Information: C:\Users\Munish Bhargav\documents\visual studio 2010\Projects\WindowsAzureProject1\WindowsAzureProject1\bin\Debug\WindowsAzureProject1.csx\roles\WebRole1\diagnostics\x64\monitor\MonAgentHost.exe -LocalPath "C:\Users\Munish Bhargav\AppData\Local\dftmp\s0\deployment(121)\res\deployment(121).WindowsAzureProject1.WebRole1.0\directory\DiagnosticStore\Monitor" -StaticConfigFile "C:\Users\Munish Bhargav\AppData\Local\dftmp\s0\deployment(121)\res\deployment(121).WindowsAzureProject1.WebRole1.0\directory\DiagnosticStore\Monitor\Configuration\mastaticconfig.xml" -ConfigFile "C:\Users\Munish Bhargav\AppData\Local\dftmp\s0\deployment(121)\res\deployment(121).WindowsAzureProject1.WebRole1.0\directory\DiagnosticStore\Monitor\Configuration\maconfig.xml" -ShutDownEvent WADDM-ShutDown-33c7c1a60c864bea9d38091aaecb7c3c -InitializedEvent WADM-StartUp-33c7c1a60c864bea9d38091aaecb7c3c -parent 5492 -events

[Diagnostics]: Creating config channel server

[MonAgentHost] Output: Agent will exit when WADDM-ShutDown-33c7c1a60c864bea9d38091aaecb7c3c is signaled.

[MonAgentHost] Output: Will signal WADM-StartUp-33c7c1a60c864bea9d38091aaecb7c3c after the agent is initialized.

[MonAgentHost] Output: Registered as an event consumer.

[MonAgentHost] Output: Agent will exit when parent process 5492 exits.

[MonAgentHost] Output: Monitoring Agent Started

[Diagnostics]: Starting configuration channel polling

[Diagnostics]: Checking for configuration updates 04-24-2011 06:01:54 PM.

[Diagnostics]: Signalling process restart on event = WADDM-ShutDown-33c7c1a60c864bea9d38091aaecb7c3c

[MonAgentHost] Output: Exiting the monitoring agent after the shutdown event was signaled.

[MonAgentHost] Output: Monitoring Agent Stopped

[Diagnostics] Information: Diagnostic process exited with code: 0

[Diagnostics] Information: C:\Users\Munish Bhargav\AppData\Local\dftmp\s0\deployment(121)\res\deployment(121).WindowsAzureProject1.WebRole1.0\directory\DiagnosticStore\Monitor

[Diagnostics] Information: C:\Users\Munish Bhargav\documents\visual studio 2010\Projects\WindowsAzureProject1\WindowsAzureProject1\bin\Debug\WindowsAzureProject1.csx\roles\WebRole1\diagnostics\x64\monitor\MonAgentHost.exe -LocalPath "C:\Users\Munish Bhargav\AppData\Local\dftmp\s0\deployment(121)\res\deployment(121).WindowsAzureProject1.WebRole1.0\directory\DiagnosticStore\Monitor" -StaticConfigFile "C:\Users\Munish Bhargav\AppData\Local\dftmp\s0\deployment(121)\res\deployment(121).WindowsAzureProject1.WebRole1.0\directory\DiagnosticStore\Monitor\Configuration\mastaticconfig.xml" -ConfigFile "C:\Users\Munish Bhargav\AppData\Local\dftmp\s0\deployment(121)\res\deployment(121).WindowsAzureProject1.WebRole1.0\directory\DiagnosticStore\Monitor\Configuration\maconfig.xml" -ShutDownEvent WADDM-ShutDown-cea6c4c0af7b4d0aa72e6ad5e8cdd773 -InitializedEvent WADM-StartUp-cea6c4c0af7b4d0aa72e6ad5e8cdd773 -parent 5492 -events

[MonAgentHost] Output: Agent will exit when WADDM-ShutDown-cea6c4c0af7b4d0aa72e6ad5e8cdd773 is signaled.

[MonAgentHost] Output: Will signal WADM-StartUp-cea6c4c0af7b4d0aa72e6ad5e8cdd773 after the agent is initialized.

[MonAgentHost] Output: Registered as an event consumer.

[MonAgentHost] Output: Agent will exit when parent process 5492 exits.

[MonAgentHost] Output: Monitoring Agent Started

[Diagnostics]: Starting configuration channel polling

[Diagnostics]: Checking for configuration updates 04-24-2011 06:02:59 PM.

[Diagnostics]: Checking for configuration updates 04-24-2011 06:04:00 PM.

[Diagnostics]: Checking for configuration updates 04-24-2011 06:05:00 PM.

[Diagnostics]: Checking for configuration updates 04-24-2011 06:06:00 PM.

[Diagnostics]: Checking for configuration updates 04-24-2011 06:07:00 PM.

[Diagnostics]: Checking for configuration updates 04-24-2011 06:08:01 PM.

 

Please Help me

Answer 11

Hello Munish,

May I ask you simply create a Azure Service project with a web role and see if it works?

Otherwise, please contact azure support team via http://www.microsoft.com/windowsazure/support/ by clicking the "Windows Azure" link. Currently this service is free. After submiting the ticket, please also paste the Details in here so that we can keep discussing.

Thanks, 

---

Wengchao Zeng
Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact [e-mail].
Microsoft One Code Framework

Answer 12

Hi Wenchao,

Even the log that i send you I did the same thing that you are saying.

Just create one new cloud project (WindowsAzureProject1) and one webrole and run. I got the same error.

Answer 13

Huh, that's interesting. It must be something wrong in your environment. Is your development storage running properly? Any interesting errors in your Windows event logs?

I've also seen some problems when the path to the project file is very long, ~250 characters. Maybe try putting your project in a top-level directory ("c:\projects" or something like that).

 

Last idea - you might try running a "HelloWorld" sample from somewhere. There might be one in the Windows Azure Platform Training Kit.

Answer 14

I tried these things too but same result.

Now Is reboot the last option? Which I hate to do? 

 

Answer 15

for me , removing Sites tag from def file worked....  dnt understand why it dint work for you

also I dont see a point in upgrading to 1.3/1.4 from Azure SDK 1.2 , if i dont get to run my app with this tag advantage in def file.

 

 

 

---

S Arora

Answer 16

After Long time i saw my azure projects running on my home machine. but for that i need to destory my whole sunday for reinstall OS on my well performing machine just for one bug. I still need to configure lots of things. Thanks everyone for your time and help.

Answer 17

I'm using 1.6 and also received this error.

 

After just building the project I got the follwoing warning in the output

 

C:\Users\<username>\Documents\Research\Code\RPAClient\RPAClient\BotLab\BotLabSite.Azure\ServiceDefinition.build.csdef(0,0): warning CloudServices078: The web role 'BotLabSite' is configured using a legacy syntax that specifies that it runs in Hostable Web Core. To run your web  role under full IIS, add a <Site> declaration within the service definition file. See http://go.microsoft.com/fwlink/?LinkId=198475

 

After adding the site with just the default values this worked just fine.