I deploying the webRole application. It is successfully deployed. But after applying the Azure caching(Preview) to my default cache of the Web role its not deployed..Shown the following the message more than 1 hr. Instance 0 of role WebRole1 is in an unknown state.. System startup tasks are Initializing and running properly. But the webrole is busy for long time.
My azure SDK version 1.7. i just enabled caching in caching tab of the web role properties. The web.config file looks like,
<tracing sinkType="DiagnosticSink" traceLevel="Error" />
<autoDiscover isEnabled="true" identifier="WebRole1" />
<!--<localCache isEnabled="true" sync="TimeoutBased" objectCount="100000" ttlValue="300" />-->
servicedefinitionfile lks like,
<Import moduleName="Diagnostics" />
<Import moduleName="RemoteAccess" />
<Import moduleName="RemoteForwarder" />
<Import moduleName="Caching" />
<LocalStorage name="Microsoft.WindowsAzure.Plugins.Caching.FileStore" sizeInMB="1000" cleanOnRoleRecycle="false" />
Configuration settings of cloud configuration file looks like,
<Setting name="Microsoft.WindowsAzure.Plugins.Caching.Loglevel" value="" />My Web role name is WebRole1. Am uninstall all previous version of azure sdk and try only sdk version 1.7 only. Because i read the version compatablity error like. At last uninstall the azure sdk version1.7 and reinstall it and check. It wont work..
<Setting name="Microsoft.WindowsAzure.Plugins.Caching.CacheSizePercentage" value="30" />
<Setting name="Microsoft.WindowsAzure.Plugins.Caching.ConfigStoreConnectionString" value="UseDevelopmentStorage=true" />
3:00:41 PM - Instance 1 of role WebRole1 is in an unknown state
3:01:47 PM - Instance 0 of role WebRole1 is starting the virtual machine
3:01:47 PM - Instance 1 of role WebRole1 is starting the virtual machine
3:03:57 PM - Instance 0 of role WebRole1 is busy
3:03:57 PM - Instance 1 of role WebRole1 is busy
Instance 1 of role WebRole1 is cycling atlast..
Atlast shown the following the error message. Solution to this type of error.
There was no endpoint listening at https://management.core.windows.net/7690051c-c52b-4c6d-865e-591a05788f5a/operations/382c6bcd6a6b4867b6cd4fc9c0f9ab44 that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Role instances recycled for a certain amount of times during an update or upgrade operation. This indicates that the new version of your service or the configuration settings you provided when configuring the service prevent role instances from running. The most likely reason for this is that your code throws an unhandled exception. Please consider fixing your service or changing your configuration settings so that role instances do not throw unhandled exceptions. Then start another update or upgrade operation. Until you start another update or upgrade operation, Windows Azure will continue trying to update your service to the new version or configuration you provided
3:21:05 PM - Deployment failed with a fatal error
- 已編輯 Global Software Resources 2012年7月19日 上午 11:58
Can you make sure this is caused by caching? Check if caching related assembly references have copy local set to true. Also try to use remote desktop to login to the instance, and check various logs, such as Windows events, to see where the problem might be.
You can refer to http://msdn.microsoft.com/en-us/library/windowsazure/gg443832.aspx
Lante, shanaolanxing This posting is provided "AS IS" with no warranties, and confers no rights.
If you have feedback about forum business, please contact email@example.com. But please do not ask technical questions in the email.
yes. Before applying caching the the Project is deployed correctly. After applying caching the role is busy atlast cycling and i cant unable to deploy completely. Web Role is waiting to start for a long time. The dll is already been copy to local is true.How to solve this issue without any error mesage.
I have the same problem. Can't RDC in. How do I know what's going on? The Web Role was also deploying fine, until I enabled Caching. Now it sits on busy for quite some time, while the Worker Role, which is not using Caching, is running fine. My WebRole also works fine on the emulator.
Right after I posted this I was able to RDC in. The event viewer shows the following from the Application Error Source:
Faulting application CacheService.exe, version 1.0.4655.0, time stamp 0x4fb0f3fe, faulting module KERNEL32.dll, version 6.0.6002.18005, time stamp 0x49e041d1, exception code 0xc0000006, fault offset 0x00000000000176fd, process id 0x%9, application start time 0x%10.
Followed by another entry from CacheStatusIndicator:
Service started successfully.
And another by CacheService:
Service started successfully.
I opened IE from within the server and tried to access the web app using the IP Address specified on the Bindings (IIS) and it results in a Bing search as if it can't find it.
The instances go from Busy to Recycling over and over again.
What else do you need me to look at?
After another try of accessing the website from within the website I finally got a yellow screen of death with details on the error. It turns out I also had added MVC 3 support to the application and the DLLs are not part of the Azure VM. I had to follow this post: http://blog.smarx.com/posts/asp-net-mvc-in-windows-azure to locally copy the DLLs.
It was my understanding that the current VMs on Azure have MVC 3 installed. Am I wrong?