Article ID: 2742275 - View products that this article applies to.
This article covers how to troubleshoot issues when adding a Hyper-V host in System Center 2012 Virtual Machine Manager.
Common errors that are logged in the VMM Console when an “Add virtual machine host” job fails:
Agent installation failed on servername.domain.com because of a WS-Management configuration error.
An internal error has occurred trying to contact an agent on the servername.domain.com server.
VMM is unable to complete the request. The connection to the agent servername.domain.com was lost.
A Hardware Management error has occurred trying to contact server servername.domain.com.
Perform the steps documented in the More Information section to identify the cause of the issue.
Step 1: Review the VMM Agent installation log fileOn 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 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.
To download the Virtual Machine Manager Configuration Analyzer, visit the following Microsoft website:
Step 3: Verify the ports used by VMM are not blocked by a firewallVerify 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 443
TCP port 5985
TCP port 5986
For more information on the ports used by VMM, please reference the following TechNet article: http://technet.microsoft.com/en-US/library/gg710871.aspx
Step 4: Check for duplicate SPNsPerform 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 2012, Error 2927 (0x8033809d)
Step 5: Check for corrupted performance counters on the Hyper-V hostCheck 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 6: Manually install the VMM Agent on the Hyper-V hostIf the Add-SCVMHost 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/bb740757.aspx
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.