Error: 18452, Severity: 14, State: 1. Error: 17806, Severity: 20, State: 2

_{Thursday, May 31, 2012 4:33 AM}

Getting error:

Error: 17806, Severity: 20, State: 2.
SSPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed. [CLIENT: 1.2.3.4]

Error: 18452, Severity: 14, State: 1.
Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 1.2.3.4]
Error: 17806, Severity: 20, State: 2.

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

Error: 18452, Severity: 14, State: 1.
Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 1.2.3.4]

Error: 17806, Severity: 20, State: 2.
SSPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed. [[CLIENT: 1.2.3.4]

Windows log

This computer was not able to set up a secure session with a domain controller in domain XXX due to the following:

The remote procedure call was cancelled.

This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.

ADDITIONAL INFO

If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session

Please suggest is this N/W issue?

Manish

_{Thursday, May 31, 2012 7:38 AM ✅Answered}

Seems that something has been changed at AD level, may be the SPN entires has been modified for the Servi ce account which is running, so can you try to connect the

SQL server using SQL server service account , incase if you get the SSPI handshake error then you have to set SPN properly for the service accounts-

http://blogs.technet.com/b/activedirectoryua/archive/2010/04/16/registering-and-troubleshooting-service-principal-names-spns.aspx

http://technet.microsoft.com/en-us/library/bb735885.aspx

http://sqlserverdiaries.com/blog/index.php/2011/03/addressing-a-login-failed-error-18452-error-message-in-sql-server-2005/

http://sqlserverpedia.com/blog/sql-server-bloggers/sql-server-and-sspi-handshake-failed-error-hell/

Rama Udaya.K ramaudaya.blogspot.com Please remember to mark the replies as answers if they help and un-mark them if they provide no help.

_{Thursday, May 31, 2012 5:09 AM}

You are trying to connect to the server with sql login while SQL Server is set to Windows Authentication only 

http://msdn.microsoft.com/en-us/library/ms188670.aspx

Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/

_{Thursday, May 31, 2012 5:12 AM}

This job was executing for last 4 years and Authentication also was not changed.

Sql Job was configured to run at 1:00 Am today with 1 hour interval.

It run o 1:00 Am and then At 2 AM sql errorlog,agentlog and windows log filled with above err and now it is running properly 3:00 AM.

it skiped 2:00AM schdule.

now problem i want to know is it N/W issue or Db issue?

Manish