RE: Msg 15404: Could not obtain information about user



Hi Jason,
Thank you for mailing me the SQL error logs.

From the error logs, I found the following error message:
"2008-05-19 09:13:34.29 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098, state: 15. Failure to register an SPN may cause integrated
authentication to fall back to NTLM instead of Kerberos. This is an
informational message. Further action is only required if Kerberos
authentication is required by authentication policies."

This indicates that the Kerberos authentication was not established for
your SQL Server instance. In this case, any domain user account will not be
accepted as a valid login account. I recommend that you try manually
registering SPN according to this article:
How to make sure that you are using Kerberos authentication when you create
a remote connection to an instance of SQL Server 2005
http://support.microsoft.com/kb/909801/en-us

Hope this helps. If you have any other questions or concerns, please feel
free to let me know. Have a nice day!


Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
=========================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================

.



Relevant Pages

  • Re: connect the SQL Server in different domains
    ... Generally SPN should be registered in the following format ... But to enable Kerberos protocol in this inter domain scenario, ... need to register an SPN using the NETBIOS name ... connect the SQL Server B in the other domain and vise versa. ...
    (microsoft.public.sqlserver.connect)
  • RE: 0x80004005 - you need permission to view its data
    ... SPN without the port number and another SPN with the port number. ... typical, non-clustered computer that is running SQL Server, you only have ... to register the SPN with the port number. ...
    (microsoft.public.sqlserver.security)
  • Re: cannot generate sspi context when server in mixed authenticati
    ... A domain admin will need to create an SPN for the SQL Server service ... Local system or domain admin starting sql does this automatically...domain ... Real-world stuff I run across with SQL Server: ... after we switched it to mixed authentication mode. ...
    (microsoft.public.sqlserver.connect)
  • Re: Publish SQL 2000 to Inet
    ... testing purposes I've registered the SQL Server instance from a workstation ... > What kind of authentication are you using with your SQL server? ... Do you wish to Register anyway? ...
    (microsoft.public.isaserver)
  • Re: Not able to register server name using windows authentication - Ur
    ... SQL Server machine. ... authentication and try connecting/registering. ... have configured mixed mode authentication also. ... But i am able to register server with sql authentication. ...
    (microsoft.public.sqlserver.connect)