Error 2927 when you add a Hyper-V server or a Hyper-V cluster node in System Center VMM

Applies to: System Center 2012 Virtual Machine ManagerMicrosoft System Center Virtual Machine Manager 2008 R2Microsoft System Center Virtual Machine Manager 2008 R2 Service Pack 1

Symptoms


Consider the following scenario. You add a Hyper-V server or a Hyper-V cluster node on a server that is running one of the following versions of Microsoft System Center Virtual Machine Manager (VMM):
  • System Center 2012 R2 Virtual Machine Manager
  • System Center 2012 Virtual Machine Manager
  • System Center Virtual Machine Manager 2008 R2
  • System Center Virtual Machine Manager 2008 R2 Service Pack 1
In this scenario, you receive the following error message:

Error (2927)
A Hardware Management error has occurred trying to contact server
<servername>.
(Unknown error (0x80338029))

Recommended Action
Check that WinRM is installed and running on server <servername>. For more information use the command "winrm helpmsg hresult".

Cause


This issue may occur in one of the following situations:
  • Antivirus software is installed but configured incorrectly on the VMM server.
  • The Hyper-V host is a node of a high availability (HA) cluster, and the cluster has issues.
  • Windows Remote Management (WinRM) is configured incorrectly.

Resolution


Step 1: Run a cluster validation report if the Hyper-V host is a node of an HA cluster

If the Hyper-V host is a node of an HA cluster, run a cluster validation report, and fix errors if there are errors in the report.

Step 2: Configure exclusions of the antivirus software

To configure exclusions of the antivirus software, follow these steps:
  1. Test whether the Hyper-V host can be added after you disable the antivirus software on the VMM server.
  2. If the test succeeds, make sure that the following directories and files are added to the exclusion list of the antivirus software:

Step 3: Check whether WinRM is configured correctly

To check whether WinRM is configured correctly, follow these steps:
  1. Open an elevated command prompt on the Hyper-V host, run winrm qc, and then restart the host. For more information, see WinRM (Windows Remote Management) Troubleshooting.
  2. Increase the default value for the WinRM time-out. To do this, open an elevated command prompt on the Hyper-V host, and then execute the following commands:
    1. winrm set winrm/config @{MaxTimeoutms = "1800000"}
    2. winrm set winrm/config/Service @{MaxConcurrentOperations="200"} 
       in WinRM 1.1 and earlier versions. Or 
      winrm set winrm/config/Service @{MaxConcurrentOperationsPerUser="400"} 
       in WinRM 2.0 and later versions. 
    3. net stop winrm
    4. net start winrm
    5. net start vmmagent
  3. Check the Svchost.exe process of the WinRM service. If the shared Svchost.exe process that hosts the WinRM service is experiencing issues, run the following command to configure the WinRM service to run in a separate Svchost.exe process:
    sc config winrm type= own
    For more information, see step 5 in How to troubleshoot the "Needs Attention" and "Not Responding" host status in System Center 2012 Virtual Machine Manager
  4. If you experience the issue that is described in WinRM operations to Hyper-V fail on a Windows 7 SP1-based or Windows Server 2008 R2 SP1-based computer that has Windows Management Framework 3.0 installed, install the hotfix on the Hyper-V host.