Hi folks, we have recently moved four SQL 2000 servers to three SQL 2008 servers. These are servers that connect to our web application which is load balanced on the back end to the three SQL Servers. Each server is Standard 64-bit on a Windows 2008 server standard. The new servers are 12GB ram, 8 core vs. 4GB ram, 4 core in the old servers.
We have been getting intermittant Sev. 20 errors of the following format:
DESCRIPTION: The client was unable to reuse a session with SPID XX, 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.
and the error in the log that occurs in conjunction with this error is: Error: 18056, Severity: 20, State: 29.
This seems to be a new thing in SQL 2008, as most references I've found online refer to SQL 2005, but also that it has been patched, which I assume is still fixed in SQL 2008.
I'm still waiting to get information from the online folks to see if they found any errors in their IIS logs to correlate with my errors, but has anyone received this type of error and made some headway in troubleshooting this?
Our web site still seems to be okay, considering we're retail and in a holiday season so orders are still flowing, but I'd rather not filter these warnings away from the pager if this is a symptom of something serious down the road, rather than an annoying feature I can safely ignore.
"In theory, theory and practice are the same. In practice, they are not."
- Albert Einstein