July 5, 2012 at 5:48 am
I am seeing a lot of Connection Pool errors in our SQL Server logs on our cluster. Has anyone had this similar issue? This is an instance on an Active\Active farm cluster. We have 10GB of RAM allocated to this instance. There are 28 databases currently. Some are very large and active. Below are the actual error messages:
Message
Error: 18056, Severity: 20, State: 29.
Message
The client was unable to reuse a session with SPID 203, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
Any advice would be greatly appreciated. My next step was to create a new instance and migrate the "Vcenter" database and jobs off the instance... we have "SCOM" running on this instance also. I was thinking they may be battling each other.
Charlie
July 5, 2012 at 6:27 am
See if the data here helps: http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/f11537a5-8dc9-40a8-b2e4-17874685b074
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply