Application unable to connect Sql Server 2005

Hi,

We recently installed Sql 2005 server and it was working fine. But today one of our user reported that they could not able to connect the sql server 2005 from the application. When I checked the error log, I found the following error for every one minute. We restarted the sql service on this sql 2005 instance but still we are getting the same error.

SSPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed.

Could any one help us on that?

Regards,

Sankar

Hello Sankar. There appears to be several possibilities as to what is going on so i will provide the links that I think are the most relevant.

http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx

http://support.microsoft.com/kb/247931/en-us

OJ has suggested this as a possible means for tracing it - I am not sure of your setup so it may or may not be useful.

0x80090311 error refers to "No authority could be contacted for authentication" which means the user cannot contact AD to get a ticket. I suggest turning on Kerberos logging and using Netmon to trace the authentication routes. You can find detailed info on how to troubleshoot Kerberos here.

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerberr.mspx

Let us know if you have any further questions or if this helps. If you do have further questions/problems please try specifying more details about your setup, e.g. are db and web server on same server? what os? what update revisions, etc.

|||

Hi, SanKar

Is your computer in a Domain? If so, it seems the problem that no KDC can be contacted. Suggest:

1) Disjoin the domain and rejoin your computer to the domain.

2) nslookup

type " <FQDN> of your client computer " see which DC returned.

3) ping <KDCname> if you know the hostname of your DC.

ping -a <ipaddress of your DC>, see whether FQDN returned.

4) Try use "SetSpn.exe" to manually register SPN, see whether it succeeds.

5) Or restart your client computer, try to use a domain account to log on, see what happens.

Good Luck!

Ming.

|||

Thanks all for your reply.

We rebooted the sql server. The error is not getting displayed after the server reboot.