Logon SSPI handshake failed RRS feed

  • Question

  • Hi,

    We are receiving following alerts (SQL Server 2005):

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

    Any help.

    Tuesday, May 7, 2013 10:21 PM

All replies

  • occasionally or occuring all the time?

    If you haven't all the things you want,be grateful for the things you don't have that you didn't want.

    Wednesday, May 8, 2013 12:45 AM
  • Check this article http://blogs.msdn.com/b/dipanb/archive/2010/12/08/sspi-handshake-failed-could-result-when-the-security-event-log-has-reached-the-maximum-log-size.aspx

    Thanks & Regards RAJUKIRAN L Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers.

    Wednesday, May 8, 2013 1:31 AM
  • Can you post some more details are you getting this error when using IIS.?

    Your SQL Server service account has the priviledge to register SPN, SQL Server will automatically register the SPN when you restart SQL Server.Local System and Network System have the priviledge

    I think you are using domain account and that does not have privilage to create SPN so you are getting this alert message.

    Also is communication is happeing between two domain check trust relationship between them.

    Below link might help


    Soldier..Sir we are surrounded from all sides by enemy.. Major: Good, we can attack in any direction Thats attitude..

    Wednesday, May 8, 2013 5:51 AM
  • there are two ways you can solve this

    1) change your service account to localsystem

    2) get your AD administrator to register the domain id and the spn using setspn.exe (refer: http://technet.microsoft.com/en-us/library/bb735885.aspx)

    Wednesday, May 8, 2013 10:42 AM
  • Here is more detail:

    Application retrives data from one database server (through select statement), process it and then update records into another database server. Both are SQL Server 2005.

    We are receiving these alerts on target server.

    On the application side we receive following error:

    The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
    Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 0, current count = 1.
    Uncommittable transaction is detected at the end of the batch. The transaction is rolled back.

    Wednesday, May 8, 2013 8:00 PM
  • That's a different error, and basically means what it says.  There should have been a previous error indicating that something failed to put your transaction into an uncommittable state.


    David http://blogs.msdn.com/b/dbrowne/

    • Proposed as answer by Fanny Liu Monday, May 13, 2013 10:17 AM
    Wednesday, May 8, 2013 8:06 PM