SSPI handshake failed with error code 0x80090311


  • Hi,

    Yesterday, all of a sudden, I received 15 alerts from my sql2k8 R2 64bit with the same content as follows:

    DATE/TIME:       9/27/2010 8:54:01 PM


    DESCRIPTION:   SSPI handshake failed with error code 0x80090311, 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>].

    How can this be troubleshooted. I can access my sql withoiut any problem through sharepoint or SSMS.

    Thqnlks in advance

    Monday, September 27, 2010 11:07 PM

All replies

  • I just checked eventviewer, security log and found 7 scurity failure for a user running a service for almost more than 1 year withoiut no issues which is a user to run Biztalk services and has full domain rights to access sql, otherwise my Biztalk would have never worked. How can this be tracked if it happens again.

    Uereunder the log :


    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          9/27/2010 8:54:05 PM
    Event ID:      4625
    Task Category: Logon
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    An account failed to log on.

     Security ID:  NULL SID
     Account Name:  -
     Account Domain:  -
     Logon ID:  0x0

    Logon Type:   3

    Account For Which Logon Failed:
     Security ID:  NULL SID
     Account Name:  btsuserrun
     Account Domain:  SALAM

    Failure Information:
     Failure Reason:  An Error occured during Logon.
     Status:   0xc000018d
     Sub Status:  0x0

    Process Information:
     Caller Process ID: 0x0
     Caller Process Name: -

    Network Information:
     Workstation Name: BTS2K9
     Source Network Address: -
     Source Port:  -

    Detailed Authentication Information:
     Logon Process:  NtLmSsp
     Authentication Package: NTLM
     Transited Services: -
     Package Name (NTLM only): -
     Key Length:  0

    This event is generated when a logon request fails. It is generated on the computer where access was attempted.

    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

    The Process Information fields indicate which account and process on the system requested the logon.

    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

    The authentication information fields provide detailed information about this specific logon request.
     - Transited services indicate which intermediate services have participated in this logon request.
     - Package name indicates which sub-protocol was used among the NTLM protocols.
     - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
    Event Xml:
    <Event xmlns="">
        <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
        <TimeCreated SystemTime="2010-09-27T18:54:05.817607700Z" />
        <Correlation />
        <Execution ProcessID="532" ThreadID="2764" />
        <Security />
        <Data Name="SubjectUserSid">S-1-0-0</Data>
        <Data Name="SubjectUserName">-</Data>
        <Data Name="SubjectDomainName">-</Data>
        <Data Name="SubjectLogonId">0x0</Data>
        <Data Name="TargetUserSid">S-1-0-0</Data>
        <Data Name="TargetUserName">btsuserrun</Data>
        <Data Name="TargetDomainName">SALAM</Data>
        <Data Name="Status">0xc000018d</Data>
        <Data Name="FailureReason">%%2304</Data>
        <Data Name="SubStatus">0x0</Data>
        <Data Name="LogonType">3</Data>
        <Data Name="LogonProcessName">NtLmSsp </Data>
        <Data Name="AuthenticationPackageName">NTLM</Data>
        <Data Name="WorkstationName">BTS2K9</Data>
        <Data Name="TransmittedServices">-</Data>
        <Data Name="LmPackageName">-</Data>
        <Data Name="KeyLength">0</Data>
        <Data Name="ProcessId">0x0</Data>
        <Data Name="ProcessName">-</Data>
        <Data Name="IpAddress">-</Data>
        <Data Name="IpPort">-</Data>

    Monday, September 27, 2010 11:19 PM
  • Did you reboot a Domain Controller or have issues with Active Directory at any point in the last 24 hours? 
    Jonathan Kehayias
    Please click the Mark as Answer button if a post solves your problem!
    Tuesday, September 28, 2010 12:01 AM

    0x80090311 error means "No authority could be contacted for authentication" which means the user cannot contact Active Directory Domain Controller to get a ticket.

    Sivaprasad S Please click the Mark as Answer button if a post solves your problem!
    Tuesday, September 28, 2010 12:39 AM
  • I rebooted Domain controller 2 days back as there were critical updates. In fact I reebooted SQL and Biztalk server also because of critical microsoft updates.

    As I said, this happened last night, which means 48 hours after reboot.

    Tuesday, September 28, 2010 7:26 AM