EN
Deze inhoud is niet beschikbaar in uw taal, maar wel in het Engels.
Dit onderwerp heeft nog geen beoordeling - Dit onderwerp beoordelen

Unable to Collect Diagnostics Data from a Windows Azure VM Role

Updated: December 5, 2011

Applies to: Windows Azure SDK 1.3 and higher.

Symptom: The Windows Azure diagnostics are not persisted to storage.

Cause: The integration components installer did not install MonConfig.dll.

Resolution: Use the following procedures to install the MonConfig.dll file on the VHD used for the VM role. If you have RDP enabled on the VM role:

  1. Log into the Windows Azure Management Portal.

  2. In the navigation pane, click Hosted Services, Storage Accounts and CDN.

  3. At the top of the navigation pane, click Hosted Services.

    The items list displays all hosted services for which you are an administrator, sorted by subscription. Beneath each service, each service deployment is listed. Before you can delete the service, you must delete all current deployments of the service.

  4. In the items list, expand the subscription and expand the hosted service.

  5. Click the VM role to which the MonConfig.dll file will be copied.

  6. On the ribbon, in the Remote Access group, click Connect.

  7. Navigate to the “%ProgramFiles%\Windows Azure Integration Components\<SDK Version>\Diagnostics\diagnostics\x64\monitor” on the virtual machine.

  8. Navigate to “%ProgramFiles%\Windows Azure SDK\<SDK Version>\bin\runtimes\diagnostics\x64\monitor” on the local computer.

  9. Drag and drop the MonConfig.dll file from the local computer to the virtual machine.

WarningWarning
This procedure does not permanently install the MonConfig.dll file. When the role is recycled the file will be lost. To permanently install the MonConfig.dll file, you must modify the VHD and upload the modified image to Windows Azure.

See Also

Vindt u dit nuttig?
(1500 tekens resterend)

Community-inhoud

Toevoegen
© 2013 Microsoft. Alle rechten voorbehouden.
facebook page visit twitter rss feed newsletter