• About
    • Bio
    • Contact
t h e D a v i d A i k e n Not Statistically Significant

Remember to update your DiagnosticsConnectionString before deploying

May 28, 2010 2:47 pm / theDavidAiken

In the ServiceConfiguration.cscfg file, you have a DiagnosticsConnectionString which as a default is linked to local storage.

    <Setting name="DiagnosticsConnectionString" value="UseDevelopmentStorage=true" />

When you deploy your package it will never start correctly (stuck in Busy/Initializing), because you could will be trying to log to the local storage, which doesn’t exist in the cloud.

Fixing this is easy:

  1. Create a storage account if you don’t already have one.
  2. In Visual Studio, bring up the properties of your project, then click settings.
  3. Click on the … next to the DiagnosticsConnectionString.image
  4. Enter your storage details in the dialog.image
  5. Save then deploy.

THIS POSTING IS PROVIDED “AS IS” WITH NO WARRANTIES, AND CONFERS NO RIGHTS

Posted in: Windows Azure / Tagged: Busy, Windows Azure

Comments are closed.

Post Navigation

← Previous Post
Next Post →

Recent Posts

  • Blah, Blah, Blah, Blah De Blah, and I’m back in the room!
  • How to use Diagnostics.wadcfg to configure Windows Azure diagnostics collection
  • Encrypting and Decrypting in Windows Azure
  • Ten Basic Troubleshooting Tips for Windows Azure
  • How To Clean up old Windows Azure diagnostics
  • How To Easily Enable Windows Azure Diagnostics Remotely
  • How To Block un-validated Windows Azure Deployments
  • Implementing Windows Azure Retry Logic
  • Our datacenters are awesomeness in a box
  • Please scale your storage too
© Copyright 2013 - t h e D a v i d A i k e n
Infinity Theme by DesignCoral / WordPress