System Center Operations Manager< Storage Account for Windows Azure Could Not be Discovered

I was trying to get System Center Operations Manager (SCOM) to monitor my Windows Azure subscription using the SCOM Windows Azure Management Pack and ran into an interesting error when SCOM tried to connect to my Windows Azure storage account.

When I first started my Azure development project, I let Visual Studio create my Windows Azure storage connection string through the Configuration properties within the Windows Azure Web Role. This automatically inserted the following configuration setting in my ServiceConfiguration.cscfg file:

<Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value=..." />

This is all fine and dandy, except when you try to set up System Center Operations Manager using the Windows Azure Management Pack, the default connection string won’t work because SCOM is looking for a connection string with a different name.

Storage account for Windows Azure Diagnostics could not be discovered because the configuration setting named ‘DiagnosticsConnectionString’ does not exist in the service configuration file or does not contain the storage account information.

Subscription ID: ffffffff-ffff-ffff-ffff-ffffffffffff Service name: hosted_service Deployment slot: Production Role name: WindowsAzureProject

Workflow name: Microsoft.SystemCenter.Azure.HostedService.TotalDiscovery.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Instance name: azureinstance Instance ID: {FFFFFFFF-FFFF-FFFF-3333-123456789012} Management group: SCOM_QA

If you are trying to monitor your Windows Azure subscription using SCOM and see this error, either rename your existing Windows Azure storage account connection string, or add a duplicate connection string named DiagnosticsConnectionString

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

After setting this up, SCOM should start grabbing your event log information from your Windows Azure subscription.

Creative Commons License

What do you think?