Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Peter99
Constraint Violating Yak Guru
498 Posts |
 Posted - 2013-05-07 : 18:18:14
|
| 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
5072 Posts |
Posted - 2013-05-07 : 21:25:45
|
| Where are you seeing this? |
 |
|
|
Peter99
Constraint Violating Yak Guru
498 Posts |
Posted - 2013-05-08 : 15:29:45
|
| We are receiving these alerts through SCOM. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2013-05-08 : 15:38:51
|
| check how the client is trying to connect. you're not giving us a lot to go on here... |
|
|
|
Peter99
Constraint Violating Yak Guru
498 Posts |
Posted - 2013-05-08 : 15:58:40
|
| 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. |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2013-05-08 : 20:45:32
|
| 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 |
|
|
|
|
|
|
Logon SSPI handshake failed