Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 950599 - Last Review: March 28, 2008 - Revision: 1.1
An SPN for the SQL Server Browser service is required when you establish a connection to a named instance of SQL Server 2005 Analysis Services or of SQL Server 2005
SYMPTOMS
Consider the following scenario. You establish a connection to a named instance of Microsoft SQL Server 2005 Analysis Services or of Microsoft SQL Server 2005. Then, the SQL Server Browser service determines the port on which the named instance is available. The connection uses Kerberos authentication. In this scenario, a service principle name (SPN) for the SQL Server Browser service is required in addition to the SPN for the named instance of Analysis Services or of SQL Server 2005. If the SPN for the SQL Server Browser service does not exist, Kerberos authentication fails.
CAUSE
This behavior occurs only when the connection string contains the
SSPI=Kerberos parameter. In this case, the connection is forced to use Kerberos authentication, and the SPN for the SQL Server Browser service must be configured.
If the connection string does not contain the
SSPI=Kerberos parameter, Kerberos authentication is typically used. The connection to the SQL Server Browser service uses NTLM and the NT_ANONYMOUS account instead. In this case, the connection to the SQL Server Browser service is successful. The SQL Server Browser service determines the correct port. Then, the actual database connection uses Kerberos authentication to provide the true authentication.
RESOLUTION
You must create an SPN for the SQL Server Browser service by using the account under which the SQL Server Browser service is running. The account must be a domain account.
Note The account cannot be the LocalSystem account or another local computer account.
The format of a NetBIOS SPN is as follows:
MSOLAPDisco.3/serverHostName
The format of a fully qualified domain name SPN is as follows:
MSOLAPDisco.3/serverHostName.Fully_Qualified_domainName
STATUS
This behavior is by design.
APPLIES TO
- Microsoft SQL Server 2005 Analysis Services
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Standard Edition
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please