Azure Cloud Service Troubleshooting Series

Original product version:   Cloud Services (Web roles/Worker roles)
Original KB number:   4466645

Summary

Cloud service is one of most popular Azure PaaS service among web developers. These blog series includes some of the common problems faced by the customers while dealing with cloud service and how to troubleshoot those issues using various tools and logs. This blog focuses on some more common scenarios that you may face while developing and deploying cloud service solution to Azure.

In order to simulate the issues we have developed three cloud service applications and below are the links for instructions that you need to follow to set up the labs for each application:

• Compressor
• Super Convertor
• Visitor Tracker

Let's deep dive into the troubleshooting series on Azure Cloud Service:

• Scenario 1: An instance of ZipEngine role is looping between Restarting and Busy state throwing an unhandled exception.
• Scenario 2: AssemblyBinder role instances is throwing System.IO.IOException.
• Scenario 3: Autoscale is not triggering for FileUploader role.
• Scenario 4 : ProcessorEngine role is stuck in Busy state.
• Scenario 5 : My website is throwing HTTP Error 503.
• Scenario 6 : Can't RDP to only 'HealthMonitor' worker role instance.
• Scenario 7 : Can't access the website, although all role instances are in running state.
• Scenario 8 : ASP.NET SignalR application is not working.

Contact us for help

If you have questions or need help, create a support request, or ask Azure community support. You can also submit product feedback to Azure feedback community.