3

DESCRIPTION: SSPI handshake failed with error code 0x8009030c, 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.XXX.XX.XX} ***The client address is different on different occasion

Can i refer this problem to my network admin? is this a network issue or a sql server issue. Is there any other way other then changing the registry ? Can i safely ignore this error ?

  • 5
    This blog post might help. – Dan Guzman Nov 19 '17 at 23:58
  • 1
    I've seen this happen before when a domain controller is rebooted. Don't have a solution though. – Andrew Lackenby Nov 21 '17 at 16:04
  • 1
    can i ignore this error safely because if a user needed access and couldnot log he would definitely have opened a ticket by now. – SqlNovice Nov 21 '17 at 16:29
2

WORKAROUND/SOLUTION Loopback check can be removed by adding a registry entry as follows:

Edit the registry using regedit. (Start –> Run > Regedit ) Navigate to: HKLM\System\CurrentControlSet\Control\LSA Add a DWORD value called “DisableLoopbackCheck” Set this value to 1

1

To address the issue:

We added the account “contoso\sqlaccount” to “Access this computer from the network” local security policy (secpol.msc) on the SQL Server box and post which we were successfully able to connect to the instance from the application.

To address the SSPI Handshake failed errors, always review the security logs post enabling Audit Logon events. Security logs would give a good amount of information needed to address this issues.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.