Troubleshooting
Applies To: Operations Manager 2007
The following table describes issues that can occur with the Hyper-V Management Pack and presents possible solutions.
| Issue | Solution |
|---|---|
Some monitors require manual reset of health state |
The following monitors require health state to be manually reset to Healthy once the prescribed resolution steps are taken:
|
Expected objects are not discovered. |
Ensure that the Hyper-V Networking Management service (Nvspwmi) is running. When the Nvspwmi service is not running and discovery runs, new Hyper-V roles and virtual networks will not be discovered and previously discovered Hyper-V roles and virtual networks will be removed. |
Virtual network adapters and guest computer containment relationships with the virtual machine are not discovered. |
Ensure that the virtual machine is running. On virtual machines that are not running, virtual network adapters and guest computer containment relationships with the virtual machine will not be discovered. |
Virtual hardware components are not discovered. |
Ensure that the Hyper-V Image Management service (vhdsvc) is running. |
Errors are generated by the script GetDiskPartitionSpace.vbs. |
Ensure that the Hyper-V Image Management service (vhdsvc) and Hyper-V Virtual Machine Management service (vmms) are running. |
Known Issues
The following are known issues with the Hyper-V Management Pack:
Hyper-V event 12680 is not generated correctly for NIC ID collisions, so the NIC ID Collision monitor will indicate a Healthy state even though a NIC ID collision may have occured.
The Media Already Present monitor does not detect event 12610 because this event has incorrect parameter information.
The Mounted Drive Read-Only monitor does not monitor some of the events that occur when a mounted drive is marked as read-only, and this monitor may not change state or alert in some situations when a mounted drive is set to be read-only.