Article ID: 2584907 - View products that this article applies to.
This article covers how to troubleshoot issues when adding a Hyper-V host in System Center Virtual Machine 2008 or System Center Virtual Machine 2008 R2.
Common errors that are logged in the VMM Administrator Console when an “Add virtual machine host” job fails include the following:
Agent installation failed on server.domain.com because of a WS-Management configuration error.
An internal error has occurred trying to contact an agent on the server.domain.com server.
VMM is unable to complete the request. The connection to the agent server.domain.com was lost.
A Hardware Management error has occurred trying to contact server server.domain.com.
Step 1: Review the VMM Agent installation log file
On the Hyper-V host, review the “vmmAgent.msi_%date%_%time%.log” file that’s located in the %systemdrive%\ProgramData\VMMLogs directory.
Note: This log file may not exist if the failure occurs early in the installation process.
Step 2: Use the System Center Virtual Machine Configuration Analyzer (VMMCA)
The Virtual Machine Manager Configuration Analyzer is a diagnostic tool that administrators 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:
· Scans the hardware and software configurations of the computers that you specify
· Evaluates these configurations against a set of predefined rules
· Displays error messages and warnings for any configurations that are not optimal for the VMM role or for other VMM functions that you specified for the computer
To download the Virtual Machine Manager Configuration Analyzer, visit the following Microsoft website:
Step 3: Verify the recommended hotfixes are installed on the VMM and Hyper-V servers
On the VMM and Hyper-V servers, verify the recommended hotfixes are installed:
(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 4: Verify the ports used by VMM are not blocked by a firewall
Verify the ports used by VMM to communicate with the Hyper-V host are not blocked by a firewall. By default, VMM uses the following ports to communicate with the Hyper-V host:
TCP port 80
TCP port 443
TCP port 2179
The following knowledge base article covers some tests to verify communication between the VMM and Hyper-V hosts:
(http://support.microsoft.com/kb/2465160)Add Host or other action fails with (2916) 0x80338126 in System Center Virtual Machine Manager 2008
For more information on the ports used by VMM, please reference the following TechNet article: http://technet.microsoft.com/en-us/library/cc764268.aspx
Step 5: Check for duplicate SPNs
Perform the steps documented in the following article to check for duplicate SPNs:
(http://support.microsoft.com/kb/970923)Unable to add a managed host in SCVMM 2008 and SCVMM 2008 R2, Error 2927 (0x8033809d)
Step 6: Check for corrupted performance counters on the Hyper-V host
Review the following knowledge base article to determine if the Hyper-V host has corrupted performance counters:
(http://support.microsoft.com/kb/2001247)SCVMM: Adding a host to System Center Virtual Machine Manager 2008 may fail with error 2912 / 0xc0000BBF
Step 7: Manually install the VMM Agent on the Hyper-V host
If the Add-VMHost job continues to fail, manually install the agent on the Hyper-V host by performing the steps documented in the following TechNet article: http://technet.microsoft.com/en-us/library/cc764218.aspx
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2584907 - Last Review: July 20, 2011 - Revision: 1.0