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 |
|
pphillips001
Starting Member
23 Posts |
 Posted - 2010-10-07 : 04:26:00
|
| Hi,We have a replicated SQL 2005 database which worked (almost) flawlessly for twelve months. Now, with no apparent change, it has started throwing these errors frequently.Severity 20 ErrorsDESCRIPTION: The client was unable to reuse a session with SPID 63, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.Severity 18 ErrorsDESCRIPTION: Replication-Replication Transaction-Log Reader Subsystem: agent ###-###-5 failed. The process could not execute 'sp_MSpub_adjust_identity' on '#######'.In the logs on the receiving server (which is who generated the error message) it says that "Login failed for user 'sa'".Has anybody come across this before? Could it be a network related issue? If so, how could we find out?Many thanks.===========================There is no reality - only perspective. |
|
|
jeffw8713
Aged Yak Warrior
819 Posts |
Posted - 2010-10-07 : 16:50:59
|
| Check to see if the 'sa' login has been disabled. The login can become disabled when someone tries to login with that account and fails multiple times. |
 |
|
|
pphillips001
Starting Member
23 Posts |
Posted - 2010-10-13 : 04:48:04
|
| Thanks jeffw8713,We connect to both servers in question on a regular basis using the 'sa' account. We've not changed the account's permissions or anything like that. Sometimes it goes days without any errors, then get thirty in one hour. There seems to be no pattern to it.===========================There is no reality - only perspective. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2010-10-13 : 07:06:04
|
| Connection pooling erroneously reusing a pool? I remember reading of bugs that allowed this to happen in the old days - and part of the previous pool's query, or results, or somesuch got carried forwards, or reused, but the pool's new owner.I expect that was all fixed long ago, but might be worth checking that version numbers on DB / ADO / OLE-DB . ODBC, or whatever it is called now!, drivers etc are all recent. |
|
|
|
|
|
|
|
|
Dozens of daily Severity 20 and 18 Errors!