Azure Win VM: Guest Agent Status - Not Ready/Unknown (GuestAgent is running within the VM)

Article
2019-06-27

Question

_{Thursday, June 27, 2019 8:32 AM}

Hi,

So, we've a Windows Azure VM on which all of a sudden Agent Status went to 'not ready' únknown' & unable to enable the replication as the Agent is not responding.

We tried, (1.) restarting the AzureGuestAgent service - didn't work (2.) Stopped the GuestAgent service & re-installed the latest GuestAgent (.msi file) again manually using elevated command - services started but @ portal level (& via powershell) agent status is still not ready. (3.) within taskmanager all the 3 required .exe are running (waapagent, guestagent, telemetry)

Enabling Replication Fails as the agent though running within the VM @ portal level is not ready/unknown.

Please, share your findings or work around in order to get the agent responding & captured @ portal level.

All replies (12)

_{Thursday, July 11, 2019 5:50 AM ✅Answered | 1 vote}

Hi,

The issue was resolved after we removed the NPcap loopback Adapter. The Azure agent was somehow trying to communicate via this adapter (had an APIPA IP) instead of Hyper-V adapter. Thus, resulting into unable to communicate with the fabric.

WaAPPAgent Logs

[00000006] [06/27/2019 16:44:40.83] [ERROR] Failed to obtain fabric URI. ControlSystem not initialized.
[00000006] [06/27/2019 16:44:45.83] [INFO] Initializing ControlSystem.
[00000006] [06/27/2019 16:44:45.88] [INFO] Attempting to discover fabric address on interface Npcap Loopback Adapter.
[00000079] [06/27/2019 16:44:45.88] [WARN] Empty DHCP option data returned
[00000006] [06/27/2019 16:44:45.88] [ERROR] Did not discover fabric address on interface Npcap Loopback Adapter.
[00000006] [06/27/2019 16:44:45.88] [ERROR] Did not discover fabric address on any interface. Dumping networking information

Regards,
Gaurav N.

_{Thursday, June 27, 2019 11:46 AM}

HI,

Is there any change happened on the network security group side?

Whats your OS version

Do you have internet connectivity for your VM?

_{Thursday, June 27, 2019 6:32 PM}

Hi Jakaruna,

VM NSG - No changes
OS - WIN 2012 R2
Internet connectivity - VM's internet connectivity is proper

is there a workaround to resolve this issue or anything that needs to be checked @ the O.S. level or Portal level.

_{Thursday, June 27, 2019 6:38 PM}

Hi,

You can look at uninstalling and reinstalling the agent

Thanks,

Matt

_{Thursday, June 27, 2019 6:45 PM}

check the log here for azure vm agent C:\WindowsAzure\Logs\WaAppAgent.log

also confirm the Agent version that should be latest

simplest way is to re-create VM either from disk or backup if you dont find anything in the logs.

_{Thursday, June 27, 2019 6:49 PM}

Hi,

Following are the certain errors from the WaAPPAgent logs..

_{Thursday, June 27, 2019 7:04 PM}

check .NET version as 4.5 is required for the VM agent to communicate with the service.

_{Thursday, June 27, 2019 7:19 PM}

.NET 4.5 is installed on the VM

_{Thursday, June 27, 2019 7:20 PM}

Hi,

Following are the certain errors from the WaAPPAgent logs..

_{Thursday, June 27, 2019 7:23 PM}

Hi,

We have already re-installed .msi file via elevated command prompt. Theough have't performed the powershell part, is that necessary for VMs in ARM & that the VM was already having agent since its deployment.

However, what shall I replace servicename with? or what should be the value. Please help out with command.
$vm = Get-AzureVM –ServiceName <cloud service name> –Name <VM name>

$vm.VM.ProvisionGuestAgent = $true
Update-AzureVM –Name <VM name> –VM $vm.VM –ServiceName <cloud service name>

_{Tuesday, July 9, 2019 5:54 PM}

Just to confirm, are you running your app in an Azure Cloud Service or an Azure Virtual Machine?

_{Tuesday, July 16, 2019 7:41 PM}

Good find! Can I ask out of curiosity where that log location was?

Share via

Azure Win VM: Guest Agent Status - Not Ready/Unknown (GuestAgent is running within the VM)

Question

All replies (12)

Additional resources