无法在运行 Windows 的 Azure VM 上配置 Azure Insights

Question

I am attempting to configure the Log Analytics agent for Insights on my Azure VM running Windows. When I attempt to deploy the monitoring configuration, the DependencyAgentWindows VM extension fails to install. I have the same solution working on a similar VM and am stumped on what the issue is for the failing VM.

{"code":"DeploymentFailed","message":"At least one resource deployment> operation failed. Please list deployment operations for details.> Please see https://aka.ms/DeployOperations for usage details.","details":"code":"VMExtensionHandlerNonTransientError","message":"The handler for VM extension type 'Microsoft.Azure.Monitoring.DependencyAgent.DependencyAgentWindows' has reported terminal failure for VM extension 'DependencyAgentWindows' with error message: 'Install failed for plugin (name: Microsoft.Azure.Monitoring.DependencyAgent.DependencyAgentWindows, version 9.10.16.22650) with exception Command C:\Packages\Plugins\Microsoft.Azure.Monitoring.DependencyAgent.DependencyAgentWindows\9.10.16.22650\scripts\RunPs1.cmd of Microsoft.Azure.Monitoring.DependencyAgent.DependencyAgentWindows has exited with Exit code: 52'.\r\n \r\n'Install handler failed for the extension. More information on troubleshooting is available at 8 8105633527088://aka.ms/VMExtensionDependencyAgentWindowsTroubleshoot'"}]}

I have tried to deploying the Monitoring Configuration and installing the DepencyAgentWindows VM Extension through the Portal and through PowerShell. I am expecting the DepencyAgentWindows VM Extension to install properly and be able to enable Insights successfully.

Answer 1

Exit code: 52" typically indicates that there was an issue installing the Dependency Agent on a Windows server. The error message "Install handler failed for the extension" suggests that the installation failed during the extension handler installation step.

There could be multiple reason why the installation failed:

If the server doesn't meet the requirement like Operating system version, PowerShell version etc. If there are some other software/extensions already installed on the server which are conflicting with the Dependency Agent. An issue with the execution policy. Inadequate permissions, issues with accessing the inte.net, or issues with the storage account. You can follow the below steps to troubleshoot the issue:

Ensure that the operating system version, PowerShell version, and other dependencies of the Dependency Agent are met. Make sure that there are no conflicting software/extensions installed on the server that could be causing the problem. Check that the execution policy is set correctly. Check the Network Security Group and Firewall rules to make sure that it allows traffic to Azure and Azure Monitor. Ensure that you have the permissions necessary to install the extension, and that you have a storage account configured for use with Azure Monitor. You can also look for more detailed logs in the Azure Portal which should provide more information about the root cause of the issue. If you are still not able to figure it out, you can open a support request with Azure Support team. They can help you troubleshoot the issue and assist you in resolving it.

Answer 2

I tried to reproduce same in my environment I got the results successfully like below.

This issue usually occurs if.network connectivity issues preventing the plugin from being downloaded and if the extension won't work properly if the vm agent is failing to report a status to the Azure platform..

To resolve this issue:

Try to delete if any other extension is already exists in your vm

In virtual machine -> extension -> uninstall

In monitor -> virtual machine -> configure insights -> enable -> monitoring configuration -> configure

When I try to deploy, it deployed successfully like below:

If still issue persists, try to uninstall the vm and Redeploy it and also check the MsDoc to know the supported operating system versions.