Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSPI Handshake Error Expand / Collapse
Author
Message
Posted Wednesday, June 13, 2012 3:41 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, May 6, 2015 2:12 PM
Points: 37, Visits: 279
Hi All,

I am getting the below error regarding sspi error can you please someone advice on this.


SSPI handshake failed with error code 0x80090311, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. [CLIENT: 10.46.0.83].


Thanks,
Santosh
Post #1314959
Posted Wednesday, June 13, 2012 3:50 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, September 1, 2016 2:56 AM
Points: 5,969, Visits: 6,067
Service account changed for SQL? Does it have the ability to register / deregister SPN's in AD? SPN's configured and right? Rebooted domain controllers recently?

That error is usually related to SQL trying to contact AD for a kerberos ticket and failing.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
When a question, really isn't a question - Jeff Smith
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1314969
Posted Thursday, December 3, 2015 3:29 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, November 29, 2016 3:25 AM
Points: 112, Visits: 418
We had same issue with few users, where their network DNS entries were obsolete due to which those clients were unable to connect via SQL Server via windows authentication. After fixing local users DNS IP it started connecting SQL with windows authentication...

May be this will help someone ....

Shamshad Ali
Post #1742215
Posted Thursday, December 3, 2015 4:04 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 8:49 AM
Points: 7,030, Visits: 14,716
I've seen messages like this in connection with password expiration. I think it occurs when someone attempts to connect with a Windows login whose password has expired.

John
Post #1742221
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse