No VM names for Hyper-V in SCOM

KB ID: 1930
Product: Veeam Management Pack for Microsoft System Center | Veeam Management Pack 7.0 | Veeam Management Pack 8.0 | Veeam Management Pack 9.0
Published: 2014-09-30
Last Modified: 2020-11-19
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

The Hyper-V topology is discovered correctly except for the Display Names of Virtual Machines, instead you can see only VM ID like in the screenshot below:

User-added image

Additionally, error events 3603 are logged in the OperationsManager event log on the Hyper-V server:

"VMDiscovery.js : 'vmid' is null or not an object error number: -2146823281"

Cause

The issue is caused by "ghost" roles for the affected VMs on the Failover Cluster Manager server or the VMM server. When our script discovers the VM names, it checks the VM list in the registry of the Cluster Manager or the VMM server at HKEY_LOCAL_MACHINE\Cluster\Resources

The behavior may manifest itself if a VM has been manually removed from inventory. By design, Hyper-V should be updating the registry appropriately. If this does not happen, the "ghost" VM has no VmID under "Parameters". Here are two examples of invalid configuration:

[HKEY_LOCAL_MACHINE\Cluster\Resources\8ad1692b-3d65-4716-8517-e8092c469af4]
"Name"="Name of VM Configuration"
"Type"="Virtual Machine Configuration"
"SeparateMonitor"=dword:00000000
 
[HKEY_LOCAL_MACHINE\Cluster\Resources\8ad1692b-3d65-4716-8517-e8092c469af4\Parameters]
"DependsOnSharedVolumes"=hex(7):61,00,62,00,63,00,33,00,36,00,33,00,32,00,63,\
  00,2d,00,37,00,36,00,36,00,66,00,2d,00,34,00,38,00,61,00,62,00,2d,00,39,00,\
  36,00,61,00,36,00,2d,00,37,00,35,00,62,00,61,00,63,00,65,00,63,00,65,00,34,\
  00,63,00,32,00,38,00,00,00,00,00


or 

[HKEY_LOCAL_MACHINE\Cluster\Resources\e27f0edb-66c2-4be0-a1c9-3a8545e6e15f]
"Name"="Name of VM"
"Type"="Virtual Machine"
"SeparateMonitor"=dword:00000000
 
[HKEY_LOCAL_MACHINE\Cluster\Resources\e27f0edb-66c2-4be0-a1c9-3a8545e6e15f\Parameters]



 

Solution

The workaround is to remove the Virtual Machines with missing VmID from the registry of the Failover Cluster Manager or the VMM server.

More information

There is a side effect to the suggested workaround: the failover will no longer work for the VMs that have been removed from registry.

If you have any questions, please, contact Veeam Support.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.