Setspn fails if domain name differs from NetBIOS name where SQL Server SPN is registered
This article was previously published under Q277658
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 236041 (SHILOH)
When you try to register the Service Principal Name (SPN) by using the Setspn utility, and the NetBIOS name of the computer that is running Microsoft SQL Server 2000 differs from the domain name, the following syntax is incorrect.
This syntax will return the following error:
setspn -A MSSQLSvc/<Host>:<port> <serviceaccount>
Note The following information applies to the examples in this article:
C:\>setspn -A MSSQLSvc/lphBar2.hemlock.com:1433 delegationRegistering ServicePrincipalNames for (null) MSSQLSvc/LPHBar2.hemlock.com:1433Failed to assign SPN to account '(null)', 0x57
- "Lphbar2" is the host name of the computer that is running SQL Server.
- "Hemlock" is the Microsoft Windows 2000 domain name.
- "Delegation" is the SQL Server domain account under which the SQL Server service is running.
- "Hemlock0" is the NetBIOS name of the computer that is running SQL Server. This is the computer where the SPN is being registered.
To work around this problem, you can register the SPN by using the following syntax.
For example, use the following syntax.
setspn -A MSSQLSvc/<Host>:<port> <domainname>\<serviceaccount>
Notice that the NetBIOS name of the computer that is running SQL Server (hemlock0) and the Windows 2000 domain name (hemlock) are different.
C:\>setspn -A MSSQLSvc/lphbar2.hemlock.com:1433 hemlock0/delegation
For information about delegation, see the "Security Account Delegation" topic in SQL Server 2000 Books Online.
Article ID: 277658 - Last Review: 12/05/2015 22:27:09 - Revision: 5.4
Microsoft SQL Server 2000 Standard Edition
- kbnosurvey kbarchive kbprb KB277658