SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: <named pipe>]

Beantwortet SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: <named pipe>]

  • Friday, January 25, 2013 1:51 AM
     
     

    Hey everyone, while looking through the Application Logs today on the server trying to figure out some of our more recent issues with connectivity, I noticed my Application log had 45,668 new events, and they all seem to be this same exact error:

    Log Name:      Application
    Source:        MSSQLSERVER
    Date:          1/24/2013 5:20:15 PM
    Event ID:      17806
    Task Category: Logon
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SVRNAME
    Description:
    SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: <named pipe>]
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSSQLSERVER" />
        <EventID Qualifiers="49152">17806</EventID>
        <Level>2</Level>
        <Task>4</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-01-24T23:20:15.000Z" />
        <EventRecordID>46903</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SVRNAME</Computer>
        <Security />
      </System>
      <EventData>
        <Data>8009030c</Data>
        <Data> [CLIENT: &lt;named pipe&gt;]</Data>
        <Binary>8E45000014000000090000004300500043002D004500530051004C00000000000000</Binary>
      </EventData>
    </Event>

    I have searched and searched, and cant seem to make any headway... Can someone help point me in the right direction?

All Replies

  • Friday, January 25, 2013 7:53 AM
     
     Answered

    Hello,

    One reason for a SSPI handshake failure could be, that the local time of the client differs more the 5 minutes from SQL Server time; that SQL Server treats the client as "untrusted" and refuses connections.


    Olaf Helper

    Blog Xing

  • Tuesday, January 29, 2013 1:17 PM
     
     Answered

    It can be case that you are using NTLM. Check the enabled authentication is keybrose or NTLM.

    Also have a look on suggest solution at below links :-

    http://www.itmonotony.com/Lists/Posts/Post.aspx?ID=42

    http://stackoverflow.com/questions/1538027/sspi-handshake-failed-with-error-code-0x8009030c-while-establishing-a-connection

    To set DisableLoopBackCheck:

    1. Click Start

    2. Search for "regedit"

    3. Right click on regedit.exe and select Run as Administrator

    4. Expand the tree to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

    5. Right click on LSA and click New --> DWORD Value

    6. Enter the name DisableLoopbackCheck

    7. Right click on DisableLoopBackCheck and click Modify

    8. Enter 1 for the Value and click OK

    9. Restart the server


    Regards,
    Rohit Garg
    (My Blog)
    This posting is provided with no warranties and confers no rights.
    Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.