ReSearch This KB – VMM Agent Not Reachable

Alert: VMM Agent Not Reachable

Management Pack Name: System Center 2012 Virtual Machine Manager Monitoring

Management Pack Version: 3.1.6011.0

Rule or Monitor: Monitor

Rule or Monitor Name: System Center 2012 Virtual Machine Manager VMM Agent Reachable

Rule or Monitor Notes: None

Issue: The VMM agent status is NeedsAttention on vmmserver.domain.loc


All Hyper-V hosts are in OK status in VMM console. No hosts are in NeedsAttention status.

Note: The ‘System Center 2012 Virtual Machine Manager VMM Agent Reachable’ monitor uses a $Target/Property[Type=”VMM2012Discovery Microsoft.SystemCenter.VirtualMachineManager.2012.AgentWatcher”]/AgentStatus$ property. It just compares the OpsMgr object’s property value to a string. In our case this is the Agent Status property.

So, we have an object with a wrong property. All properties are populated when a discovery rule runs and returns them. Obviously, we have an issue with a discovery process.

How to investigate this?

First, you need to know that almost all discoveries used in VMM-OpsMgr integration are made via a connector. There is no discovery rules for most of objects in the VMM management pack(s). So the first place you need to check is the Settings tab in VMM Console (Settings – System Center Settings – Operations Manager Server – Properties).

In this case Connection Status were ‘Error’ and we can find this in the error details:

‘VMM Management group object cannot be found.

Operations Manager discovery failed with error: “Exception of type ‘Microsoft.VirtualManager.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipSourceExceptionOM10′ was thrown.”.’

Looks pretty cryptic, isn’t it?

Note the server name from the ‘Operations Manager root management server’ field.

Open Operations Manager eventlog on the server you noted above and find the event with ID 26319.

In our case it contained this description (it’s pretty big so here is the most important part):

“An exception was thrown while processing ProcessDiscoveryDataWithBinarySupport for session ID

Exception message: The relationship source specified in the discovery data item is not valid.

Relationship source ID: 2342c8d1-af40-510c-3d05-3335be6143a0

Rule ID: b24cf64c-bace-4854-bfb4-55aed6dafbd3



Hmm. ‘The relationship source specified in the discovery data item is not valid’ means ‘the object specified as a source doesn’t exist’. Let’s find what this object is.

Now we have two important pieces of data:

RelationshipInstance TypeId=”{cca19de7-7feb-ee85-ba5c-edb46e918ccb}”

and the target (discovered object) name:


So what is discovered object type? Run the following query on the OpsMgr Database:

SELECT [RelationshipTypeId]
FROM [OpsMgrDB].[dbo].[RelationshipType]

WHERE RelationshipTypeId = ‘cca19de7-7feb-ee85-ba5c-edb46e918ccb’

In our case the result is:

CCA19DE7-7FEB-EE85-BA5C-EDB46E918CCB  Microsoft.SystemCenter.VirtualMachineManager.Network.2012.VirtualMachineHostsVNic

Our object is the virtual network card.

Let’s find the Virtual Machine this vNIC is attached to (using the vNIC’s name):

Open Virtual Machine Manager Shell (powershell) and run the following pipe:

Get-SCVirtualNetworkAdapter -All | Where-object {$_.DeviceId -eq ‘Microsoft:C096E71D-461F-4598-B1B8-AA30B6B998FF\205FF091-30B7-4C73-AB40-9E957C2939B9’}

Check the Name property, it’s the name of the VM we’re looking for. Now we can check the VM status in VMM console.

In our case this VM is stored in VMM Library AND it is in Missing state. I do not need this VM anymore so I just deleted it from VMM Console. After VM deletion I am opened the Settings tab in VMM Console (Settings – System Center Settings – Operations Manager Server – Properties) and clicked the Refresh
button. When refresh job were finished connection status returned back to OK, all discoveries are went fine and alerts were closed.

2 thoughts on “ReSearch This KB – VMM Agent Not Reachable

  1. josefehse

    Hi Alexey, thank you for the post. It was very clarifying. I was able to run some scripts to get the objects that were causing the “issues”. However, I have some VSwitchHostsVPort objects that are supposedly fine and working. I wonder what is exactly wrong with them. Have any ideas on how to figure out WHY SCOM doesn’t like them?


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.