SSPI handshake error

  • Got multiple (a lot) SQL alerts this morning on one of our cluster named instances (SQL Server 2008 R2, SP3 Enterprise Edition). this went on for about 45 minutes, then stopped. contacted users and with the exception of one (their application was slow), there were no issues. Here's the information we have:

    from the SQL Alerts:

    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: <named pipe>].

    Error log yields:

    2016-06-16 10:07:30.92 Logon Error: 17806, Severity: 20, State: 14.

    2016-06-16 10:07:30.92 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. [CLIENT: <named pipe>].

    Event Viewer also provides the SSPI handshake failed with error code 0x8009030c, state 14 message.

    BTW - for the SQL Service we use a domain account - it never expires.

    Googling this provides a lot of information - but it appears there multiple reasons why this can occur. Any ideas on how to tackle this? Thanks.

  • 1. Go to register start > run

    2. Type Regedit

    3. Go to: HKLM\System\CurrentControlSet\Control\LSA

    4. Add a DWORD value called “DisableLoopbackCheck

    5. Set this value to 1

    6. Reboot after making this change.

  • Thanks John,

    Checked with our server administrator, we implemented that a couple of months ago. Server is part of our domain. We have it user our clock service. And the sql server service uses a domain account.

    If you have any ideas or URLs, I'd like to see them. Thanks.

  • bobba (6/22/2016)


    If you have any ideas or URLs, I'd like to see them. Thanks.

    I found this SSPI-related post by Allen White[/url] while investigating SSPI issues at a previous place. Seemed to cover the situations we were having.

    Thomas Rushton
    blog: https://thelonedba.wordpress.com

  • This was removed by the editor as SPAM

  • This was removed by the editor as SPAM

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply