locked
SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security RRS feed

  • Question

  • Hi,

    Starting yesterday, I started getting the following error:

    2016-07-12 05:42:04.91 Logon       Error: 18452, Severity: 14, State: 1.
    2016-07-12 05:42:04.91 Logon       Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.11.6.221]
    2016-07-12 05:51:32.61 Logon       Error: 17806, Severity: 20, State: 14.
    2016-07-12 05:51:32.61 Logon       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. The logon attempt failed   [CLIENT: 10.11.6.221]

    I'm trying to identify which account could be the cause of the failed logon attempts. But while I know the source and the application, I'm unable to obtain the account name causing the failed logon attempt.

    I need some help troubleshooting this.

    Thank you,

    Nico

    Tuesday, July 12, 2016 4:56 PM

Answers

  • Hello Nico,

    1. Check in SQL Server ErrorLog if the SPN registration worked. If not you will find an entry at the start sequence like this:
    The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/XXX] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos.
    The you have to fix it: Register a Service Principal Name for Kerberos Connections

    2. Check on machine 10.11.6.221 if there was an issue connecting the domain controller at the time.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Tuesday, July 12, 2016 5:16 PM