角色实例都需要更长的时间比预期开始 [英] Role Instances are taking longer than expected to start

问题描述

当我尝试在本地机器上它给下面error.How在Windows Azure上运行模拟器ASP.net MVC应用程序，我可以摆脱这种？

在输出窗口错误

 的Windows Azure工具：警告：公众重新映射端口80至81，以避免仿真过程中发生冲突。
Windows Azure的工具：警告：角色'PawLoyalty.Web重映私有端口80至82，以避免仿真过程中发生冲突。
Windows Azure的工具：警告：证书标识设置Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption'的角色PawLoyalty.Web服务配置文件中指定在证书或作为SSL的一部分服务定义文件不宣endpont
 

解决方案

从时间我们也遇到过这个问题的时间。通过试验和误差，我们发现它也可以通过高速缓存引起的。

我们所做的是禁用缓存，运行应用程序（和它运行良好的话），并再次启用高速缓存（并再次运行良好）。

它的一个非常蹩脚的解决方案，可能不适合你的工作，但请给它一个尝试。你可以做的另一件事就是删除本地存储模拟器cacheclusterconfigs BLOB容器。使用这些2的组合通常导致问题得到解决。

When I try to run ASP.net MVC app on Windows Azure emulator on local machine it gives below error.How can I get rid of this ?

Error on Output window

Windows Azure Tools: Warning: Remapping public port 80 to 81 to avoid conflict during emulation.
Windows Azure Tools: Warning: Remapping private port 80 to 82 in role 'PawLoyalty.Web' to avoid conflict during emulation.
Windows Azure Tools: Warning: Certificate identification setting 'Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption' for role 'PawLoyalty.Web' specified in the service configuration file is not declared in the service definition file in the Certificate or as part of an SSL endpont

解决方案

From time to time we also encountered this issue. By trial-and-error we found it to be caused by caching.

What we did was disabled caching, ran the application (and it ran fine then) and enabled caching again (and it ran fine again).

Its a really lame solution and may not work for you but please give it a try. Other thing you could do is delete the cacheclusterconfigs blob container in local storage emulator. Using a combination of these 2 usually resulted in the problem getting resolved.

这篇关于角色实例都需要更长的时间比预期开始的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！