Can someone give me some guidance on how to get my monitoring extension working? We did a rename and this new VM is from the previous disk, we are going to have a lot of these in our migration. Any help is greatly appreciated. yes I have tried to uninstall from the dashboard- it fails I have tried force removing it with PowerShell and it throws some no content error I have one that shows installed and 1 vm that doesn't, they both show the same error. the one that showed installed, I tried uninstalling it, installing manually with workspace id and keys. still nothing. I need this because I can't turn on, disk encryption, update management, inventory, etc.. If I get the status in PowerShell all I see is Extensions[0] : Name : MicrosoftMonitoringAgent VMAgent : VmAgentVersion : Unknown Statuses[0] : Code : ProvisioningState/Unavailable Level : Warning DisplayStatus : Not Ready Message : VM status blob is found but not yet populated. Time : 11/12/19 8:01:54 PM ANY help would be greatly appreciated. Please. I am out of ideas

Hi Goofoff, i have the same Problem. A Call with the MS Azure Support give me the workaround: Create a Snapshot from the Disk Create a VM from that Disk Don´t install the Extensions Manuel, just enable the Features u need like Diagnostic Settings The Extensions will me installed automaticly Best Regards, Kim

Azure Vm Extension Stuck?

Goofoff 91

Can someone give me some guidance on how to get my monitoring extension working?
We did a rename and this new VM is from the previous disk, we are going to have a lot of these in our migration.
Any help is greatly appreciated.

yes I have tried to uninstall from the dashboard- it fails
I have tried force removing it with PowerShell and it throws some no content error
I have one that shows installed and 1 vm that doesn't, they both show the same error.
the one that showed installed, I tried uninstalling it, installing manually with workspace id and keys. still nothing.
I need this because I can't turn on, disk encryption, update management, inventory, etc..
If I get the status in PowerShell all I see is
Extensions[0] :
Name : MicrosoftMonitoringAgent
VMAgent :
VmAgentVersion : Unknown
Statuses[0] :
Code : ProvisioningState/Unavailable
Level : Warning
DisplayStatus : Not Ready
Message : VM status blob is found but not yet populated.
Time : 11/12/19 8:01:54 PM

ANY help would be greatly appreciated. Please. I am out of ideas

jakaruna-MSFT 596 Reputation points Microsoft Employee

2019-11-13T08:26:44.22+00:00

Whats the base OS of your VM? windows or linux
Micah McKittrick 946 Reputation points Microsoft Employee

2019-11-13T18:48:51.177+00:00

In addition to what @jakaruna-MSFT asked, can you provide some specific errors you get from removing it via the portal and PowerShell? That might help narrow it down. Also, based on the last error regarding the VM agent, that might be the issue. You cannot use extensions if the Agent is not working. You can reinstall the agent though which might resolve everything all up. Here is the doc on the VM agent: https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/agent-windows it is for windows but if you are running Linux on the left hand menu there is another option for linux.
Goofoff 91 Reputation points

2019-11-14T18:10:07.807+00:00

They are a mix of Server 2012/2016.
Goofoff 91 Reputation points

2019-11-14T18:15:44.007+00:00

If I goto update management/inventory/change tracking, etc..
I receive
"The xxxxxxx solution cannot be enabled"
"The solution cannot be enabled on this virtual machine because VM agent is missing or not responding"

When I try to remove it from the portal through the uninstall option.
"Failed to delete the virtual machine extension
Failed to delete the virtual machine extension 'MicrosoftMonitoringAgent'. Error: error"
PowerShell just says No content and doesn't go anything even if I try the -force switch.
Micah McKittrick 11 Reputation points

2019-11-14T22:28:06.117+00:00

Try logging into the VM then manually installing the Agent. This should replace it with a working version then at which point you could manage the extensions again from the portal:https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/agent-windows#manual-installation
Goofoff 91 Reputation points

2019-11-18T18:52:42.933+00:00

still comes up with unknown on the extension. =/
Goofoff 91 Reputation points

2019-11-22T02:09:01.56+00:00

I have tried every suggestion people have made and nothing has worked. I am going to resort to rebuilding the VM
Micah McKittrick 11 Reputation points

2019-11-22T02:10:30.563+00:00

If you like, I can get you in touch with Technical Support to see what they can do. I just would need you to email me at AzCommunity@microsoft.com and provide your SubscriptionID and link to this issue.

1 answer

WeilKi 81 Reputation points

2019-11-14T11:04:54.95+00:00
Hi Goofoff,

i have the same Problem. A Call with the MS Azure Support give me the workaround:

Create a Snapshot from the Disk

Create a VM from that Disk

Don´t install the Extensions Manuel, just enable the Features u need like Diagnostic Settings

The Extensions will me installed automaticly

Best Regards,

Kim
Please sign in to rate this answer.
Goofoff 91 Reputation points

2019-11-14T20:01:44.23+00:00

Failed during deployment. both agents show unavailable.
"provisioningOperation": "Create", "provisioningState": "Failed", "statusCode": "Conflict", "statusMessage": { "status": "Failed", "error": { "code": "ResourceDeploymentFailure", "message": "The resource operation completed with terminal provisioning state 'Failed'.", "details": [ { "code": "VMAgentStatusCommunicationError", "message": "VM 'X' has not reported status for VM agent or
extensions. verify VM has a running VM agent and can establish outbound connections to Azure storage.", id": "/Microsoft.Insights.VMDiagnosticsSettings"

Goofoff 91 Reputation points

2019-11-14T20:06:33.067+00:00

and by both I mean. the Diagnostics agent failed during deployment. I tried to install the Microsoft monitoring agent. It went to unavailable when I enabled it from the dashboard.
Sign in to comment