Edit

Share via

Common issues that cause Azure Cloud Service (classic) roles to recycle

  • 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).

This article discusses some of the common causes of deployment problems and provides troubleshooting tips to help you resolve these problems. An indication that a problem exists with an application is when the role instance fails to start, or it cycles between the initializing, busy, and stopping states.

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.

Missing runtime dependencies

If a role in your application relies on any assembly that isn't part of the .NET Framework or the Azure managed library, you must explicitly include that assembly in the application package. Keep in mind that other Microsoft frameworks aren't available on Azure by default. If your role relies on such a framework, you must add those assemblies to the application package.

Before you build and package your application, verify the following statements are true:

  • If using Visual Studio, make sure the Copy Local property is set to True for each referenced assembly in your project that isn't part of the Azure SDK or the .NET Framework.
  • Make sure the web.config file doesn't reference any unused assemblies in the compilation element.
  • The Build Action of every .cshtml file is set to Content. This setting ensures that the files appear correctly in the package and enables other referenced files to appear in the package.

Assembly targets wrong platform

Azure is a 64-bit environment. Therefore, .NET assemblies compiled for a 32-bit target aren't compatible with Azure.

Role throws unhandled exceptions while initializing or stopping

Any exceptions thrown by the methods of the RoleEntryPoint class, which includes the OnStart, OnStop, and Run methods, are unhandled exceptions. If an unhandled exception occurs in one of these methods, the role recycles. If the role is recycling repeatedly, it may be throwing an unhandled exception each time it tries to start.

Role returns from Run method

The Run method is intended to run indefinitely. If your code overrides the Run method, it should sleep indefinitely. If the Run method returns, the role recycles.

Incorrect DiagnosticsConnectionString setting

If application uses Azure Diagnostics, your service configuration file must specify the DiagnosticsConnectionString configuration setting. This setting should specify an HTTPS connection to your storage account in Azure.

To ensure that your DiagnosticsConnectionString setting is correct before you deploy your application package to Azure, verify the following statements are true:

  • The DiagnosticsConnectionString setting points to a valid storage account in Azure.
    By default, this setting points to the emulated storage account, so you must explicitly change this setting before you deploy your application package. If you don't change this setting, an exception is thrown when the role instance attempts to start the diagnostic monitor. This event may cause the role instance to recycle indefinitely.
  • The connection string is specified in the following format. (The protocol must be specified as HTTPS.) Replace MyAccountName with the name of your storage account, and MyAccountKey with your access key:
DefaultEndpointsProtocol=https;AccountName=MyAccountName;AccountKey=MyAccountKey

If you're developing your application by using Azure Tools for Microsoft Visual Studio, you can use the property pages to set this value.

Exported certificate doesn't include private key

To run a web role under Transport Layer Security (TLS), you must ensure that your exported management certificate includes the private key. If you use the Windows Certificate Manager to export the certificate, be sure to select Yes for the Export the private key option. The certificate must be exported in the .pfx format, which is the only format currently supported.

Next steps

View more troubleshooting articles for cloud services.

View more role recycling scenarios at Kevin Williamson's blog series.