Azure辅助角色陷入未知角色状态
Azure 工具包 1.5
- 创建新项目
- 添加辅助角色
- 按 F5
部署陷入困境：
[fabric] 角色实例：deployment(189).WindowsAzureProject1.WorkerRole1.0
[fabric] 角色状态未知
最终部署超时。
关于如何调试这个有什么想法吗？
Azure toolkit 1.5
- Create New project
- Add worker role
- Hit F5
The deployments get stuck in:
[fabric] Role Instance: deployment(189).WindowsAzureProject1.WorkerRole1.0
[fabric] Role state Unknown
Eventually the deployment times out.
Any ideas on how to debug this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
我个人通过删除 IIS 管理器中默认网站的 *:808 绑定解决了这个问题。
I personally solved this problem by removing *:808 binding in IIS Manager for Default Website.
部署到 Azure 的包中可能缺少所需的 Azure 程序集。
仔细检查项目引用的每个 Azure 程序集是否将“复制到本地”属性设置为 true。
以下文章可能有助于调试问题：
调试 MSDN 文章
The required Azure assemblies may be missing from the package you are deploying to Azure.
Double check that each Azure assembly your project is referencing has the copy to local property set to true.
The following article may help to debug the problem:
Debugging MSDN article
让它工作起来，结果发现 Windows Process Activation Service 没有在我的计算机上正常运行。重新安装并启用 TCP 激活，现在可以正常工作了！
Got it working, turned out that Windows Process Activation Service wasn't running correctly on my machine. Reinstalled and enabled tcp activation and now its working!
我遇到了同样的问题：角色永久陷入未知状态并且从未正确启动。事实证明，Net.Tcp 端口共享服务 (SMSvcHost.exe) 占用了端口 808，这导致开发结构无法启动角色。我重新启动了服务，现在我的角色在开发结构中运行良好。
因此，如果您遇到同样的问题，请查看端口 808 是否已被其他进程占用。
I had the same problem: roles were permanently stuck in Unknown state and never started properly. Turns out that Net.Tcp Port Sharing Service (SMSvcHost.exe) had taken port 808 and this prevented dev fabric from starting the roles. I restarted the service, and now my roles run fine in dev fabric.
So if you run into the same problem, see if port 808 has been taken by some other process.
Andreas，
您可能缺少程序集引用或存在启动脚本问题，继续的最佳方法是尝试启用 intellitrace 的部署。
Andreas,
You're probably missing an assembly reference or have a startup script issue, best way to continue is to try the deployment with intellitrace enabled.