Article ID: 976640 - View products that this article applies to.
This article discusses how to troubleshoot the "Not Responding" host status that appears in the Microsoft System Center Virtual Machine Manager (VMM) Administrator Console. The "Not Responding" host status indicates that the VMM server cannot communicate with the host. If this communication is interrupted, even intermittently, you can expect the host status to change in the VMM Administrator Console.
Common errors that are logged in the VMM Administrator Console in the Jobs view when a Host status is "Not Responding" include the following:
Insufficient resources are available to complete this operation on the servername.domainname server.
(Not enough storage is available to complete this operation (0x8007000E))
An internal error has occurred trying to contact an agent on the servername.domainname server.
(No more threads can be created in the system (0x800700A4))
VMM is unable to complete the request. The connection to the agent servername.domainname was lost.
(Unknown error (0x80338012))
The WS-Management Service cannot process the request. Object not found on the servername.domainname server.
(Unknown error (0x80041002))
Host cluster servername.domainname 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.
Step 1: Use Virtual Machine Manager Configuration AnalyzerThe Virtual Machine Manager Configuration Analyzer is a diagnostic tool that you can use to evaluate important configuration settings for computers that either are serving or might serve VMM roles or other VMM functions. The Virtual Machine Manager Configuration Analyzer does the following:
Before you install the Virtual Machine Manager Configuration Analyzer, you must download and install the 64-bit version of Microsoft Baseline Configuration Analyzer. To download the MBCASetup64.msi file, visit the following Microsoft website:
http://go.microsoft.com/fwlink/?LinkID=97952Note The system requirements for Microsoft Baseline Configuration Analyzer indicate that only Windows Server 2003 is supported. However, the Virtual Machine Manager Configuration Analyzer and the Microsoft Baseline Configuration Analyzer were tested and are supported on 64-bit versions of Windows Server 2008 and of Windows Server 2008 R2.
You must install and run the Virtual Machine Manager Configuration Analyzer on the computer that either currently is or will become your VMM server. To review the system requirements for the VMM server, visit the following Microsoft website:
http://go.microsoft.com/fwlink/?LinkId=133516To download the Virtual Machine Manager Configuration Analyzer, visit the following Microsoft website:
Step 2: Check recommended hotfixesOn all servers that host a VMM or Hyper-V role, verify that the recommended hotfixes are installed. For more information about these hotfixes, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2397711)Recommended hotfixes for System Center Virtual Machine Manager 2008 R2
(http://support.microsoft.com/kb/962941)Recommended hotfixes for System Center Virtual Machine Manager 2008
Step 3: Check for corrupted performance countersCheck the Application event log on the host to see if the following event is logged:
Log Name: Application
Event ID: 3012
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
If the Event ID 3012 is logged on the host machine, perform the steps documented in the following knowledge base article to rebuild the performance counters:
(http://support.microsoft.com/kb/2554336)- How to manually rebuild Performance Counters for Windows Server 2008 64bit or Windows Server 2008 R2 systems
Step 4: Check the Svchost.exe process of the Windows Remote Management serviceVirtual Machine Manager depends very much on the Windows Remote Management service for underlying communication. Therefore, the "Not Responding" status is very likely to occur because of an error in the underlying Windows Remote Management communication between the VMM server and the host computer. In this case, the status is "OK" shortly after you restart the host computer. However, the status changes to "Not Responding" after three to four hours, and jobs on the VMM server fail and return an error that resembles the following:
A Hardware Management error has occurred trying to contact server server.contoso.com.
(Unknown error (0x803381a6))
Check that WinRM is installed and running on server server.contoso.com. For more information use the command "winrm helpmsg hresult".
Additionally, if you stop the Windows Remote Management service at a command prompt, this process takes much longer than usual to be completed. Sometimes, it can take up to five minutes to stop.
This problem can occur if the shared Svchost.exe process that hosts the Windows Remote Management service is backed up.
To resolve this problem, configure the Windows Remote Management service to run in a separate Svchost.exe process. To do this, open an elevated command prompt, type the following command, and then press ENTER.
c:\>sc config winrm type= ownIf the command is completed successfully, you see the following output:
Note Make sure that you type the command exactly as it appears here. Notice the space after the equal sign (=) symbol.
[SC] ChangeServiceConfig SUCCESS
Step 5: Increase the default value for the WinRM time-outOn each server, open an elevated command prompt, and then follow these steps:
Step 6: Check the VMM server computer accountThis problem also occurs because the VMM server computer account is removed from the local Administrators group on the host computer. This setting may be caused by the "Restrictive Groups" Group Policy setting.
For more information about this cause, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/969164/ )Virtual Server or Hyper-V host may have a status of "Not Responding" or "Needs Attention" due to Restricted Groups group policy setting
To resolve this problem, move the VMM server and host computers to a new organizational unit (OU) that blocks inheritance of all Group Policy objects.
Step 7: Disable TCP OffloadingYou must disable TCP Offloading in Windows in the registry and in any network adapter teaming management software that is being used. You must check all these locations to make sure that TCP Offloading is completely disabled. This operation must be performed on both the VMM server and on the host computer.
Locate all network adapters in the registry under the following subkey:
There are additional subkeys under this subkey that are named with four digits, starting with "0000." Locate the subkeys that show the physical network adapter names on the details pane. Find the "DriverDesc" value on the details pane. This value should contain the name of a network adapter, such as "HP NC360T PCIe Gigabit Server Adapter." For each of these subkeys, make the following changes:
Disable all vendor-specific offloading. Set values for any entries that include the word "Offload" to zero (0). This value disables vendor-specific offloading. For example, these entries include the following.
Collapse this tableExpand this table
To disable TCP Offloading in Windows, use the following registry entry for task offloading for the TCP/IP protocol:
You can set this registry entry to 1 to disable all task-offloading from the TCP/IP transport.
Many vendors have some form of offloading capabilities built into their teaming management software. Such offloading can appear in many forms and is usually vendor-specific.
For more information about task offload, visit the following Microsoft Developer Network website:
Step 8: Check for other causesSome other potential causes of this problem include the following:
VMM accounts membershipYou can put the VMM accounts into the appropriate groups according to the following:
VMM server machine account:
Article ID: 976640 - Last Review: January 12, 2012 - Revision: 4.0