Microsoft KB Archive/277658

= Setspn fails if domain name differs from NetBIOS name where SQL Server SPN is registered =

Article ID: 277658

Article Last Modified on 1/29/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q277658



BUG #: 236041 (SHILOH)



SYMPTOMS
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. setspn -A MSSQLSvc/: This syntax will return the following error: C:\>setspn -A MSSQLSvc/lphBar2.hemlock.com:1433 delegation

Registering ServicePrincipalNames for (null)

MSSQLSvc/LPHBar2.hemlock.com:1433

Failed to assign SPN to account '(null)', 0x57 Note The following information applies to the examples in this article:
 * &quot;Lphbar2&quot; is the host name of the computer that is running SQL Server.
 * &quot;Hemlock&quot; is the Microsoft Windows 2000 domain name.
 * &quot;Delegation&quot; is the SQL Server domain account under which the SQL Server service is running.
 * &quot;Hemlock0&quot; is the NetBIOS name of the computer that is running SQL Server. This is the computer where the SPN is being registered.



WORKAROUND
To work around this problem, you can register the SPN by using the following syntax. setspn -A MSSQLSvc/: \ For example, use the following syntax. C:\>setspn -A MSSQLSvc/lphbar2.hemlock.com:1433 hemlock0/delegation Notice that the NetBIOS name of the computer that is running SQL Server (hemlock0) and the Windows 2000 domain name (hemlock) are different.



MORE INFORMATION
For information about delegation, see the &quot;Security Account Delegation&quot; topic in SQL Server 2000 Books Online.

Keywords: kbprb KB277658

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.