SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 Logon SSPI handshake failed
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Peter99
Constraint Violating Yak Guru

494 Posts

Posted - 05/07/2013 :  18:18:14  Show Profile  Reply with Quote
Hi,

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

Any help.
Thanks

russell
Pyro-ma-ni-yak

USA
5072 Posts

Posted - 05/07/2013 :  21:25:45  Show Profile  Visit russell's Homepage  Reply with Quote
Where are you seeing this?
Go to Top of Page

Peter99
Constraint Violating Yak Guru

494 Posts

Posted - 05/08/2013 :  15:29:45  Show Profile  Reply with Quote
We are receiving these alerts through SCOM.
Go to Top of Page

russell
Pyro-ma-ni-yak

USA
5072 Posts

Posted - 05/08/2013 :  15:38:51  Show Profile  Visit russell's Homepage  Reply with Quote
check how the client is trying to connect. you're not giving us a lot to go on here...

Edited by - russell on 05/08/2013 15:40:55
Go to Top of Page

Peter99
Constraint Violating Yak Guru

494 Posts

Posted - 05/08/2013 :  15:58:40  Show Profile  Reply with Quote
Here is setup:

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.
Go to Top of Page

chadmat
The Chadinator

USA
1974 Posts

Posted - 05/08/2013 :  20:45:32  Show Profile  Visit chadmat's Homepage  Reply with Quote
I don't believe these 2 errors are related. The first indicates a problem getting a connection to SQL Server, the 2nd indicates a problem with a transaction once you already have a connection.

-Chad
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.06 seconds. Powered By: Snitz Forums 2000