SSPI handshake failed with error code 0x8009030c

  • Hello,

    New here and trying to figure out the root cause of these error messages.  I have read a lot of posts about this same message but none seem to fit my scenario.  I have 2 messages back to back about every 30 seconds.  The first is :

    Event Type: Error

    Event Source: MSSQL$WCS2008

    Event Category: Logon

    Event ID: 17806

    Date: 7/29/2019

    Time: 6:45:42 AM

    User: N/A

    Computer: WCS_CEO

    Description:

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

    Where the client ip is the address of my sql server itself. The second error is:

    Event Type: Failure Audit

    Event Source: MSSQL$WCS2008

    Event Category: Logon

    Event ID: 18452

    Date: 7/29/2019

    Time: 6:45:42 AM

    User: N/A

    Computer: WCS_CEO

    Description:

    Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: xx.xx.xx.xx]

    Where again the client ip address is the sql server address itself. These messages show up in the application error log.  The sql server is not domain joined and my sql is set to allow mixed authentication.

    Any help is appreciated.

    Thanks!

  • jmarberg wrote:

    Any help is appreciated. Thanks!

    in case if default trace is enabled, get ClientProcessID and check process trying to connect :

    DECLARE @trcpath nvarchar(256)
    SELECT
    @trcpath=left(CAST(value as nvarchar(256)),len(CAST(value as nvarchar(256)))-charindex('_',reverse(CAST(value as nvarchar(256)))))+'.trc'
    FROM fn_trace_getinfo(default)
    WHERE property = 2

    SELECT * FROM fn_trace_gettable (@trcpath,default )
    WHERE EventClass= 20
    ORDER BY starttime DESC

     

    Description of the event:

    https://docs.microsoft.com/en-us/sql/relational-databases/event-classes/audit-login-failed-event-class

     

     

  • Thank you. Im new to SQL and that helped me right away.  I was able to determine it was the reporting service causing the issue.  Now to figure why it cant connect to SQL.

  • jmarberg wrote:

    Now to figure why it cant connect to SQL.

    it can be due to the misconfiguration of SSRS

    first ideas:

    1. it tries connects to the wrong SQL instance
    2. it's not configured properly (login & password)
    3. it worked before but something was changed on OS or AD level
    4. password was changed for SSRS account (see p.2 above)

    Are there any ReportServer databases on the instance at all?

     

Viewing 4 posts - 1 through 3 (of 3 total)

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