January 5, 2012 at 8:08 am
Just upgraded a vendor app from sql 2005 to sql 2008 r2 sp1 and are consistently getting Error: 18056, Severity: 20, State: 29. The client was unable to reuse a session with SPID 72, which had been reset for connection pooling. I have applied all patches and stil lcan't get rid of error. User's seeing timeouts (the box itself is doing little). ANyone found a way to overcome this error?
January 7, 2012 at 3:30 am
Is there any other error message that is shown in the error log just before this message.
Can you also enable profiler to trace any query executing sp_reset_connection / or another suspicious code that is running.
Refernce :
Regards,
Raj
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply