Here’s one more Knowledge Base article we published this morning. This one shows you how to easily fix an issue where the Microsoft System Center Operations Manager 2007 R2 (OpsMgr) Connector for HP OpenView fails to auto-forwarding alerts to an HP OVO server.
Consider the following scenario:
1. You are using System Center Virtual Machine Manager 2008 (VMM) to manage a cluster resource. 2. One node of the cluster displays a status of Needs Attention. 3. Viewing the properties of the node displays a connection status of Not Responding on the status tab. 4. Remove and attempting to re-add the cluster back again fails with the following error:
Error (2912) An internal error has occurred trying to contact an agent on the node1.xxx server. (Unknown error (0x800007d0)) Recommended Action Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
5. The other nodes can be added successfully, but when the cluster refreshes you receive the following message:
Warning (13926) Host cluster <name> was not fully refreshed because not all of the nodes could be contacted. Highly available storage and virtual network information reported for this cluster might be inaccurate. Recommended Action Ensure that all the nodes are online and do not have Not Responding status in Virtual Machine Manager. Then refresh the host cluster again.
This can occur if the Performance Counters on the node are corrupt.
To resolve this issue, complete the steps below:
1. Test using the following commands in an elevated command prompt (run a CMD prompt as Administrator):
winrm e wmi/root/cimv2/Win32_PerfRawData_Tcpi
Examine the result: p_NetworkInterface WSManFault Message ProviderFault WSManFault Message = HRESULT = 0x800007D0 Error number: -2147023537 0x8007054F An internal error occurred.
wmic path Win32_PerfRawData_Tcpip_NetworkInterface get *
Examine the result:
ERROR: Description =
2. Perform the steps documented in the following knowledge base article to rebuild the performance counters:
2554336 - How to manually rebuild Performance Counters for Windows Server 2008 64bit or Windows Server 2008 R2 systems (http://support.microsoft.com/kb/2554336)
3. Remove the partially added cluster and re-add the same cluster once again.
At this point all nodes should be added successfully.
For more information see the following Knowledge Base article:
976640 - How to troubleshoot the "Not Responding" host status in SCVMM 2008 and in SCVMM 2008 R2 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;976640)
For the most current version of this article please see the following:
2686573 : Adding a cluster to System Center Virtual Machine Manager fails with error 2912 (Unknown error (0x800007d0))
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/