使用 Windows Azure Accelerator for WebRoles 的 Web 部署问题
我是用于 Web 角色的 Azure 加速器的新手，我已按照网络指导执行了每个步骤，但当我尝试部署我的网站时出现错误。我重新检查了所有内容 WMSvc 正在运行并设置为自动和用户名，密码是正确的，但我不明白问题出在哪里。
错误 1 Web 部署任务失败。（远程代理（URL http://2f96c9ab6cda4281bcf25a899d66955d.cloudapp.net/MSDEPLOYAGENTSERVICE）无法联系到远程代理服务已在目标计算机上安装并启动。）确保站点名称、用户。名称和密码正确。如果问题未解决，请联系您的本地或服务器管理员。错误详细信息：远程代理（URL http://2f96c9ab6cda4281bcf25a899d66955d.cloudapp.net/MSDEPLOYAGENTSERVICE）可能不被联系。确保目标计算机上安装并启动了远程代理服务。收到了不支持的回复。响应标头“MSDeploy.Response”为“”，但预期为“v1”。远程服务器返回错误：(401) 未经授权。 0 0 QuickMVCdep
请帮助我找到解决方案，以便我可以将我的项目交付给客户。
I am new to Azure Accelerator for web roles I have performed each step on the guidance from the net but I am getting an error when I try to deploy my website.Everything is rechecked by me WMSvc is running and is set to auto and username and password is correct but I dont understand where is the problem.
Error 1 Web deployment task failed.(Remote agent (URL http://2f96c9ab6cda4281bcf25a899d66955d.cloudapp.net/MSDEPLOYAGENTSERVICE) could not be contacted. Make sure the remote agent service is installed and started on the target computer.) Make sure the site name, user name, and password are correct. If the issue is not resolved, please contact your local or server administrator. Error details: Remote agent (URL http://2f96c9ab6cda4281bcf25a899d66955d.cloudapp.net/MSDEPLOYAGENTSERVICE) could not be contacted. Make sure the remote agent service is installed and started on the target computer. An unsupported response was received. The response header 'MSDeploy.Response' was '' but 'v1' was expected. The remote server returned an error: (401) Unauthorized. 0 0 QuickMVCdep
Please help me to find the solution so that I can deliver my project to Client.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我遇到了同样的问题。
作为部署过程的一部分，VS Azure 工具中的发布操作似乎可以正确设置 MSDeploy，但从 VS 创建包然后使用 Azure 门户升级服务器则不会。这很糟糕，因为 VS 发布操作会删除部署，然后重新创建它，这将重新分配您的 VIP 地址。
我无法指出其中的区别，但我注意到的一件事是，如果您从 VS 进行发布，则会为您安装 MS Web Deploy 2.0，而我不相信当您运行升级。也就是说，我从未设法在 Azure 服务器上手动安装/配置正确的位以启用 MSDeploy（我怀疑主机外部发生了一些 LB/防火墙配置以允许流量到达 8172）。
总而言之，MSDeploy 在开发过程中非常有用，因此我更喜欢这种痛苦（这需要我每次进行重大升级时更改 DNS 中的 A 记录），而不是替代方案（使用门户进行升级并失去使用 MSDeploy 的能力） ）。
我很想了解一种鱼与熊掌兼得的解决方案（允许 MSDeploy 构建 Web 角色的升级包）。
I have run into the same issue.
It appears that the Publish action from the VS Azure tools will set up the MSDeploy correctly as part of the deployment process, but creating a package from VS and then upgrading the server using the Azure portal will not. Which is a bummer since the VS Publish action deletes the deployment and then recreates it, which will reassign your VIP address.
I haven't been able to pinpoint the difference, but one thing I've noticed is that if you do a Publish from VS, MS Web Deploy 2.0 will be installed for you, whereas I don't believe it is when you run an Upgrade. That said, I've never managed to manually install/configure the right bits on an Azure server to enable MSDeploy (I suspect that there is some LB/firewall configuration that happens outside of the host to allow traffic to 8172).
All in all, MSDeploy is useful enough during development that I prefer that pain (which requires me to change my A record in my DNS every time I do a major upgrade) over the alternative (Upgrade using the portal and lose the ability to use MSDeploy).
I would love to learn of a solution where we can have our cake and eat it too (an upgrade package that allows MSDeploy'ing a web role).