大网数据广告活动
启动与系统组件

Can't add a managed host with error 2927

· 52CE 我爱测

Fixes an issue in which error 2927 occurs when you add a managed host in Virtual Machine Manager.

This article helps you fix an issue in which error 2927 occurs when you add a managed host in System Center 2012 Virtual Machine Manager.

Original product version:   System Center 2012 Virtual Machine Manager
Original KB number:   970923

Symptom

When you add a managed host in System Center 2012 Virtual Machine Manager, it may fail with the following error messages:

From the VMM console:

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

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

The following event may also be logged in the System event log:

Log Name: System
Source: Microsoft-Windows-Security-Kerberos
Date: 23/04/2009 2:08:30 PM
Event ID: 4
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <server>
Description: The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server <server>. The target name used was HTTP/<server>. It indicates that the target server failed to decrypt the ticket provided by the client. Which can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain (DOMAIN.COM) is different from the client domain (DOMAIN.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

Cause

This problem occurs because two or more computer accounts have the same service principal name (SPN) registered. Event ID 11 is logged when the Key Distribution Center (KDC) receives a ticket request, and the related SPN exists more than one time when it's checked on the global catalog (GC) for forest-wide verification.

Resolution

To resolve this problem, locate the computer or user accounts that have the duplicate SPNs. When you've located the computers that have the duplicate SPNs, you can delete the computer account from the domain, disjoin, and rejoin the computer to the domain, or you can use ADSI Edit (Active Directory Service Interface Editor) to correct the SPN on the computer that has the incorrect SPN.

On Windows Server 2008 and later versions, to locate the computer accounts that have the duplicate SPNs, use setspn -x to automatically detect duplicate SPNs.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 04/09/2024
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。