Windows Azure: How to diagnose and fix Storage Service Issues?

Here’re some general guidelines on how to diagnose and resolve issues when using the development storage services. The assumption is that you are using the StorageClient sample library from the Windows Azure SDK for accessing the storage services. (a) If your first access to any storage service fails, it could be due to any of the […]

Here’re some general guidelines on how to diagnose and resolve issues when using the development storage services. The assumption is that you are using the StorageClient sample library from the Windows Azure SDK for accessing the storage services.

  • (a) If your first access to any storage service fails, it could be due to any of the following explanations:
    1. the service is not started (local development storage scenario)
    2. you did not configure account information or storage endpoints correctly in the configuration files for your service
    3. there is an error reading the account information
  • (b) The easiest thing to check is issue (a1). 
    1. Make sure the development storage tool is running (icon in the status bar; if not you can run it over the entry points in the Start menu)
    2. Make sure all services are running; right-click the development storage item and bring up the UI; the status for all services must be "running"
    3. If you use table storage locally, make sure that you selected the right database; again in the Development Storage UI you can see which database is selected in the Name column in the table storage row. The development storage has certain restrictions with respect to the table name; follow the instruction in the Windows Azure documentation.
    4. to make sure everything is in a initial state you can reset all services in development storage using the UI
    5. In rare cases you might have to clean up some port reservations by running: netsh http delete urlacl url=http://+:10002/

Full Article