Debugging & TroubleShooting: Development Fabric Roles are busy,Certificate installation error in Windows Azure Toolkit for Windows Phone
November 22, 2011 Leave a comment
As a part of Windows Azure Troubleshooting , it ‘s important to get Windows Azue roles as Busy, Aborted or Stopped in dev fabric. Primary reasons are underlying behind the development error.
Cases of Staged environments or Production environment is quite different because in that case we need to troubleshoot the VM on which the instance is running.
For development fabric , there is a common error of getting Azure Roles get Busy, Aborted or Stopped. Such a case quite common for Windows Azure Toolkit for Windows Phone.
After installing Windows Azure Toolkit for Windows Phone, you might get a Project option in Visual Studio like this:
After that , you might get a prompt like this :
You can select default Storage account name & key or Use development Storage Emulator.
In Next screen , you will be prompted with the options to select Azure asp.net membership role or Use ACS account credentials.
If you select to create a new ASP.NET membership store in Windows Azure Tables. Then , the project loads & start F5 to dubug. But , you will see the Busy status of Windows Azure Roles & there is a issue in connecting the Azure instance with Windows Phone. check the storage emulator for endpoints addresses:
as over HTTPS on port 443 and HTTP on port 10080, both on IP address 127.0.0.1. If it is running on a different port or IP address, stop the deployment, and exit the Windows Azure Compute Emulator.
Now , Try to install the certificate in Windows Phone , even its got installed but after it will throw exception as Azure Web Role got stuck in Busy state in dev fabric.
In development Fabric , Check the Role Status as Busy & Exception Details:
To fix this issue you need to remove users created with the old authentication method in the Windows Azure Storage tables used by the application. To do this, you can use a tool like https://www.myazurestorage.com to remove the old users in the PushUserEndpoints table (if you are using the Storage Emulator you can use other tools like the Azure Storage Explorer).
More hotFix are here: http://watwp.codeplex.com/wikipage?title=Troubleshooting