Exchange was unable to register the service principal name.

 

Applies to: Operations Manager Management Pack for Exchange 2010

Topic Last Modified: 2011-08-02

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, do one or more of the following:

  • From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.

  • From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.

Details

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Event ID

12011

Event Source

MSExchangeTransport

Alert Type

Error

Rule Path

Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport

Rule Name

Exchange was unable to register the service principal name.

Explanation

This Error event indicates the Microsoft Exchange Transport service couldn't register the specified service principal name (SPN).

SPNs are used to support mutual authentication between a client application and a service. The SPN is the same for any method of authentication. When it uses Kerberos to authenticate itself to a server, the client requests a session ticket for the service principal name. When the client uses certificate-based authentication, the SPN is validated against the contents of the SubjectName field of the certificate of the server.

This Error event may be caused by an error in the operating system during the DsServerRegisterSpn function.

User Action

To resolve this error, do the following:

  1. Determine the description of the Win32 error code that is provided in the event description. To look up system error codes, see System Error Codes at the MSDN Web site for more information.

  2. Use the explanation of the Win32 error code as a guideline to resolve the Win32 error.

If this error frequently occurs, contact Microsoft Customer Support. For information about how to contact support, visit the Microsoft Help and Support Web site.

For More Information

If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.