Azure Cloud Service Troubleshooting Series

I am excited to write my second troubleshooting blog series on Azure Cloud Service after API Management. If you are interested to get your hands dirty on APIM, check out this blog series now !!

Cloud service is one of most popular Azure PaaS service among web developers. So I thought of simulating some labs on various issues faced by the customers commonly. Kevin Williamson's 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. In this blog I am going to focus on some more common scenarios that we may face while developing and deploying cloud service solution to Azure.

In order to simulate the issues I have developed 3 cloud service applications and below are the links for instructions that you need to follow to setup 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: Could not load file or assembly - An attempt was made to load a program with an incorrect format.
  • Scenario 2 : AssemblyBinder role instances is throwing System.IO.IOException -There is not enough space on the disk and stuck between Busy and Restarting state.
  • Scenario 3 : Autoscale is not triggering for FileUploader role although CPU utilization in one of the instance FileUploader_IN_1 always stays at 100%.
  • Scenario 4 : ProcessorEngine role is stuck in Busy state stating - Preparing to start role... System is initializing.
  • Scenario 5 : My website is throwing HTTP Error 503. The service is unavailable when browsed over the default cloud service domain url (*.cloudapp.net).
  • Scenario 6 : Not able to RDP to only 'HealthMonitor' worker role instance and getting an error : This computer can't connect to the remote computer .
  • Scenario 7 : I cannot access my website, although all role instances are in running state.
  • Scenario 8 : ASP.NET SignalR application is not working in azure cloud service.

Hope you have enjoyed and learnt a bit of Cloud Service troubleshooting through this series. I will keep on adding more scenarios to this list, so have a close watch on this blog 🙂

Happy learning !