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:
Error (421) Agent installation failed on server.domain.com because of a WS-Management configuration error. Error (2912) An internal error has occurred trying to contact an agent on the server.domain.com server. Error (2916) VMM is unable to complete the request. The connection to the agent server.domain.com was lost. Error (2927) 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