Edit

Share via

Troubleshoot Azure Cloud Services (Classic) deployment problems

  • Article

Important

Cloud Services (classic) is now deprecated for all customers as of September 1st, 2024. Any existing running deployments will be stopped and shut down by Microsoft and the data will be permanently lost starting October 2024. New deployments should use the new Azure Resource Manager based deployment model Azure Cloud Services (extended support).

When you deploy a cloud service application package to Azure, you can obtain information about the deployment from the Properties pane in the Azure portal. You can use the details in this pane to help you troubleshoot problems with the cloud service, and you can provide this information to Azure Support when opening a new support request.

You can find the Properties pane as follows:

  • In the Azure portal, choose the deployment of your cloud service, select All settings, and then select Properties.

Note

You can copy the contents of the Properties pane to the clipboard by clicking the icon in the upper-right corner of the pane.

If your Azure issue is not addressed in this article, visit the Azure forums on Microsoft Q & A and Stack Overflow. You can post your issue in these forums, or post to @AzureSupport on Twitter. You also can submit an Azure support request. To submit a support request, on the Azure support page, select Get support.

Problem: I can't access my website, but my deployment is started and all role instances are ready

The website URL link shown in the portal doesn't include the port. The default port for websites is 80. If your application is configured to run in a different port, you must add the correct port number to the URL when accessing the website.

  1. In the Azure portal, choose the deployment of your cloud service.
  2. In the Properties pane of the Azure portal, check the ports for the role instances (under Input Endpoints).
  3. If the port isn't 80, add the correct port value to the URL when you access the application. To specify a nondefault port, type the URL, followed by a colon (:), followed by the port number, with no spaces.

Problem: My role instances recycled without me doing anything

Service healing occurs automatically when Azure detects problem nodes and therefore moves role instances to new nodes. When these moves occur, you might see your role instances recycling automatically. To find out if service healing occurred:

  1. In the Azure portal, choose the deployment of your cloud service.
  2. In the Properties pane of the Azure portal, review the information and determine whether service healing occurred during the time that you observed the roles recycling.

Roles recycle roughly once per month during host-OS and guest-OS updates.
For more information, see the blog post Role Instance Restarts Due to OS Upgrades

Problem: I can't do a VIP swap and receive an error

A VIP swap isn't allowed if a deployment update is in progress. Deployment updates can occur automatically when:

  • A new guest operating system is available and you configured for automatic updates.
  • Service healing occurs.

To find out if an automatic update is preventing you from doing a VIP swap:

  1. In the Azure portal, choose the deployment of your cloud service.
  2. In the Properties pane of the Azure portal, look at the value of Status. If it's Ready, then check Last operation to see if one recently happened that might prevent the VIP swap.
  3. Repeat steps 1 and 2 for the production deployment.
  4. If an automatic update is in process, wait for it to finish before trying to do the VIP swap.

Problem: A role instance is looping between Started, Initializing, Busy, and Stopped

This condition could indicate a problem with your application code, package, or configuration file. In that case, you should be able to see the status changing every few minutes and the Azure portal may say something like Recycling, Busy, or Initializing. This fluctuation of status indicates that there's something wrong with the application that is keeping the role instance from running.

For more information on how to troubleshoot for this problem, see the blog post Azure PaaS Compute Diagnostics Data and Common issues that cause roles to recycle.

Problem: My application stopped working

  1. In the Azure portal, choose the role instance.
  2. In the Properties pane of the Azure portal, consider the following conditions to resolve your problem:
    • If the role instance recently stopped (you can check the value of Abort count), the deployment could be updating. Wait to see if the role instance resumes functioning on its own.
    • If the role instance is Busy, check your application code to see if the StatusCheck event is handled. You might need to add or fix some code that handles this event.
    • Go through the diagnostic data and troubleshooting scenarios in the blog post Azure PaaS Compute Diagnostics Data.

Warning

If you recycle your cloud service, you reset the properties for the deployment, effectively erasing the information for the original problem.

Next steps

View more troubleshooting articles for cloud services.

To learn how to troubleshoot cloud service role issues by using Azure PaaS computer diagnostics data, see Kevin Williamson's blog series.