Article ID: 303411 - View products that this article applies to.
This article was previously published under Q303411
BUG #: 232774 (SHILOH_BUGS)
When SQL Server starts on a computer that is running Microsoft SQL Server 2000 or Microsoft SQL Server 2005, the SQL Server program always attempts to register the virtual server in the Active Directory. The following event may be logged in the event log:
SuperSocket info: (SpnRegister): Error 8344 SuperSocket Info: (SPNRegister) : Error 1355 SuperSocket info: SpnUnRegister() : Error 8344.NoteError 1355 is equal to ERROR_NO_SUCH_DOMAIN. Error 8344 is equal to insufficient permissions to perform the registration operation. This is shown as a warning for the SPNRegister function and as an error for the SpnUnRegister function.
This message is not an error message. This text is only a warning that SQL Server cannot register a service principal name (SPN). This indicates that the security mechanism that will be used is Microsoft Windows NT Challenge\Response (NTLM) authentication instead of Kerberos authentication.
These messages should only be considered a problem if your SQL Server installation requires Kerberos authentication or the network security settings prevent fallback to NTLM negotiation. Otherwise, these messages can be ignored safely.
The message usually appears because the SQL Server service account is running as a domain user who does not have requisite permissions to register SPNs. With Microsoft Windows 2000 Service Pack 3 (SP3), you can enable Kerberos authentication on server clusters. For instructions on how to do this, see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/319723/ )Information about SQL Server 2000 Kerberos support, including SQL Server virtual servers on server clusters
You can also edit the account's Access Control Settings permissions in the Active Directory directory service to enable the Read servicePrincipalName permission and the Write servicePrincipalName permission for the SQL Service account.
Warning If you use the Active Directory Service Interfaces (ADSI) Edit snap-in, the LDP utility, or any other LDAP version 3 clients, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require that you reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems caused by incorrectly modifying Active Directory object attributes can be solved. Modify these attributes at your own risk.
To resolve these type messages and enable the SQL Server service to create SPNs dynamically for your SQL Server instances, ask your domain administrator to add the appropriate permissions and user rights to the SQL Server startup accounts.
To enable the SQL Server service account to establish SPNs correctly on startup, follow these steps:
When you perform this workaround, you eliminate SPN issues for new installations or installations that have had the TCP/IP port or domain name modified.
Important We recommend that you do not grant WriteServicePrincipalName right to the SQL service account when the following conditions are true:
Assume that you have the following:
The following may occur:
Note This issue is fixed in SQL Server 2012.
Microsoft has confirmed that this is a problem in SQL Server 2000 and SQL Server 2005.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/235529/ )Kerberos support on Windows 2000-based server clusters
(http://support.microsoft.com/kb/269229/ )How to manually re-create the Cluster service account
Article ID: 303411 - Last Review: April 7, 2013 - Revision: 6.0