Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Please, try again later.
The Hyper-V topology is discovered correctly, however, the Display Names of Virtual Machines are listed as their VM IDs.
Example:
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
The issue is caused by "ghost" roles for the affected VMs on the Failover Cluster Manager server or the VMM server.
When the Veeam Management Pack for Microsoft System Center 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, however, if this does not happen, the "ghost" VM has no VmID under "Parameters". Here are two examples of invalid configuration:
The workaround is to remove the Virtual Machines with missing VmID from the registry of the Failover Cluster Manager or the VMM server.
Note: This workaround may cause failover to no longer work for the VMs removed from the registry.
Your feedback has been received and will be reviewed.
Please, try again later.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.
Please, try again later.