Worker 角色非常简单并且可以在模拟器中运行。上传到 Windows Azure 实例后似乎会初始化，然后会变得忙碌，然后重新启动并重新开始。 Azure 诊断不发送任何我们自己的跟踪消息，并不断地一遍又一遍地提供流畅的线条：
信息：RD00155D3629BA：2011-08-22 17:41:26Z OnTimedEvent 开始时间 8/22/2011 5:41:26 PM
信息：RD00155D3629BA：2011-08-22 17:40:26Z OnTimedEvent 已完成
错误：RD00155D3629BA：2011-08-22 17:40:26Z 找不到文件“c:\logs\file2.txt”。
信息：RD00155D3629BA：2011-08-22 17:40:26Z 正在复制 c:\logs\file2.txt
错误：RD00155D3629BA：2011-08-22 17:40:26Z 找不到文件“c:\logs\file1.txt”。
信息：RD00155D3629BA：2011-08-22 17:40:26Z OnTimedEvent 开始时间 8/22/2011 5:40:26 PM
信息：RD00155D3629BA：2011-08-22 17:40:26Z OnTimedEvent 开始时间 8/22/2011 5:40:26 PM
编辑：这个小应用程序中没有代码写入提到的文件
Worker role is pretty simple and runs in emulator OK. After uploading up to Windows Azure instances seems to initialize, become busy then restart and start over again. Azure Diagnostics do not ship any of our own trace messages and keeps delivering flowing lines over and over again:
Information: RD00155D3629BA: 2011-08-22 17:41:26Z OnTimedEvent Start 8/22/2011 5:41:26 PM
Information: RD00155D3629BA: 2011-08-22 17:40:26Z OnTimedEvent Completed
Error: RD00155D3629BA: 2011-08-22 17:40:26Z Could not find file 'c:\logs\file2.txt'.
Information: RD00155D3629BA: 2011-08-22 17:40:26Z Copying c:\logs\file2.txt
Error: RD00155D3629BA: 2011-08-22 17:40:26Z Could not find file 'c:\logs\file1.txt'.
Information: RD00155D3629BA: 2011-08-22 17:40:26Z OnTimedEvent Start 8/22/2011 5:40:26 PM
Information: RD00155D3629BA: 2011-08-22 17:40:26Z OnTimedEvent Start 8/22/2011 5:40:26 PM
Edit: No code in this small application writes to mentioned files
发布评论
评论（1）
有几个“最喜欢”的原因会导致角色无法正确启动并在各个阶段之间循环。这是一篇博客文章，其中包含一个很好的列表：
http://blog.toddysm.com/2010/01/windows-azure-deployment-stuck-in-initializing-busy-stopping-why.html
根据我的经验，最受欢迎的是部署期间未能将所有依赖项包含在角色中。
There are several "favorite" reasons why a role doesn't start up correctly and cycles through the various stages. Here's a blog posting with a pretty good list of them:
http://blog.toddysm.com/2010/01/windows-azure-deployment-stuck-in-initializing-busy-stopping-why.html
The most popular in my experience is failure to include all dependencies in the role during deployment.