Here’s a new Knowledge Base article we published that talks about how to troubleshoot the “Needs Attention” and “Not Responding” host status in System Center 2012 Virtual Machine Manager. This is one you’ll probably want to add to your Favorites.
This article discusses how to troubleshoot the “Needs Attention” and “Not Responding” host status in System Center 2012 Virtual Machine Manager. The “Needs Attention” and “Not Responding” host status in the VMM console occurs because the VMM Server is unable to communicate with the host machine or components (WMI, WinRM, etc.) on the host machine that are used to communicate with the VMM Server are not functioning correctly.
Common errors that are logged in the Jobs views in the VMM Console when the host status is “Needs Attention” or “Not Responding:”
The Windows Remote Management (WS-Management) service cannot process the request. The object was not found on the server ( servername.domain.com ).
Unknown error (0x80041002) or Unknown error (0x80338000)
VMM is unable to complete the request. The connection to the agent servername.domain.com was lost.
Unknown error (0x80338126) or Unknown error (0x80338012)
VMM does not have appropriate permissions to access the Windows Remote Management resources on the server ( servername.domain.com ).
Unknown error (0x80338104)
Host cluster servername.domain.com 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.
Virtual Machine Manager cannot complete the Windows Remote Management (WinRM) request on the computer servername.domain.com .
Perform the steps documented in the More Information section to identify the cause of the “Needs Attention” or “Not Responding” host status.More Information Step 1: Check the Health status of the Host To check the Health status of a host, perform the following steps:
1. Open the VMM Console.
2. Select the Fabric view, right-click the host that’s experiencing issues and chose properties.
3. Within the host properties, select Status.
4. Select the category that has the Red exclamation to view the error details.
For more information on the host health check feature, please reference the following blog: http://blogs.technet.com/b/scvmm/archive/2011/12/19/host-properties-new-in-vmm-2012-expanded-he...Step 2: Use the Virtual Machine Manager Configuration Analyzer (VMMCA) VMMCA is a diagnostic tool you can use to evaluate important configuration settings for computers that are either running VMM server roles or are acting as virtual machine hosts. The VMMCA scans the hardware and software configurations of the computers you specify, evaluates them against a set of predefined rules, and then provides you with error messages and warnings for any configurations that are not optimal.
• Add the VMM service account to the Administrators "restricted groups" group policy setting.
• Create a new organizational unit in the domain, move the host computer object to the new OU and then configure the new organizational unit to block policy inheritance.
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:
2554336 How to manually rebuild Performance Counters for Windows Server 2008 64bit or Windows Server 2008 R2 systemsStep 5: Check the Svchost.exe process of the Windows Remote Management service VMM depends on the Windows Remote Management service for host 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 scenario, the host 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 servername.domain.com .
Unknown error (0x803381a6)
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 experiencing issues.
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.
sc config winrm type= own
Note Make sure that you type the command exactly as it appears here. Notice the space after the equal sign (=) symbol.
If the command is completed successfully, you should see the following output:
[SC] ChangeServiceConfig SUCCESS
For the most current version of this article please see the following:
J.C. Hornbeck | Knowledge Engineer | Management and Security Division
App-V Team blog:
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:
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/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.