A host refresh in the System Center Virtual Machine Manager 2008 Administrators console fails with error 2912

A host refresh in the System Center Virtual Machine Manager 2008 Administrators console fails with error 2912

  • Comments 1
  • Likes

KBHere's another KB we published this morning.  This one talks about an issue where doing a host refresh in the SCVMM 2008 admin console generates error 2912 with 0x800700A4:

=====

Symptoms

In the System Center Virtual Machine Manager 2008 (SCVMM) Administrators console, a host refresh may fail with the following error:

Error (2912)
An internal error has occurred trying to contact an agent on the agent %servername%.contoso.com server.    (No more threads can be created in the system (0x800700A4))

Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.

The hex code 0x800700A4 equates to ERROR_MAX_THRDS_REACHED

In addition, the following error message may be displayed in the System event log on the managed host:

Error 1605
“The processing of Group Policy failed. Windows could not evaluate the Windows Management Instrumentation (WMI) filter for the Group Policy object”

When this occurs the host status will also change from "Ok" to "Needs Attention".  Further inspection of the host properties will reveal that the agent status is "Not Responding".

Cause

Typically, the "Needs Attention" host status is displayed if the SCVMM server is unable to communicate with the agent on the managed host.  However, in this specific example the communication to the host is working normally (RDP and PING works) but the host is unable to perform any actions required to update the VMM server. 

Note : This issue is very rare and has only been reported in scenarios with large VM deployments on a managed host.

Resolution

This problem has been known to occur if the WMI service is non-responsive or backed up on the problem host.
1. Open the Services.msc snap in.
2. Click on Start followed by Run.
3. Type "services.msc" without the quotes and press Enter. This will open the Services snap-in
4. Right click on "Windows Management Instrumentation" and select "Restart"

Note : The following system components depend upon WMI:

·         Hyper-V Image Management Service
·         Hyper-V Networking Management Service
·         Hyper-V Virtual Machine Management
·         Internet Connection Sharing
·         IP Helper
·         Microsoft iSCSI Software Target
·         SMS Agent Host
·         SMS Task Sequence Agent
·         Virtual Machine Manager Agent

5. Right click on the "Virtual Machine Manager Agent" and select "Restart"

Note: If VMM is in the process of refreshing this host while the WMI service is restarting, it may result in the following error:

Error (2916)
VMM is unable to complete the request. The connection to the agent %server_name%.contoso.com was lost.
(Unknown error (0x80338126))

Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTP traffic. If the error persists, reboot %server_name%.contoso.com and then try the operation again.

6. In the VMM administrators console, select the Hosts tab in the lower left hand corner and right click on the problem host and select "Refresh"

More Information

This error is not indicative of a problem with SCVMM, but more likely a Windows performance related issue on the managed host.  While the managed host is in this state, connectivity via PING or RDP should still function normally although expect delayed logon times and the Hyper-V snap-in may not load either local or remote.

Please refer to the following article for the recommended hotfixes for VMM: KB2397711 - Recommended hotfixes for System Center Virtual Machine Manager 2008 R2

=====

For the latest version of this article see the link below:

KB2472146 - A host refresh in the System Center Virtual Machine Manager 2008 Administrators console fails with error 2912

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

clip_image001 clip_image002

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • <p>Hello, we have one machine with this error &nbsp;(Unknown error (0x800007d0)) </p> <p>No way to refresh the host...</p>