Home Dashboard Directory Help

SQL Server 2008 Express -- Connection pooling errors by Don Thompson


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


11
0
Sign in
to vote
Type: Bug
ID: 376574
Opened: 10/20/2008 8:03:08 AM
Access Restriction: Public
0
Workaround(s)
view
6
User(s) can reproduce this bug

Description

Hi,

I am using SQL Server 2008 Express (RTM) - 10.0.1600.22. I have some code in my application which opens a connection to the database in a thread asynchronously, then executes a query asynchronously. It's slightly odd code, but we had to implement it to get around another bug in previous versions of SQL server that still hasn't been hotfixed. The code has been released to our client base and is running on hundreds, if not thousands, of PCs connected to SQL 2000 and SQL 2005 databases, so I believe the code is doing things correctly.

Occasionally when that code executes, I get an error back from ADO's Recordset:Open which reports:
[DBNETLIB][ConnectionRead (WrapperRead()).]General network error. Check your network documentation. from Microsoft OLE DB Provider for SQL Server

When this happens, I also get an EventLog entry on the server hosting SQL 2008 that says:
The client was unable to reuse a session with SPID 58, 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 SQL Server ERRORLOG file (located in the install directory) says:
2008-10-16 11:08:12.39 spid58     Error: 18056, Severity: 20, State: 29.
2008-10-16 11:08:12.39 spid58     The client was unable to reuse a session with SPID 58, 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.

There are no previous error messages in the error log. I have reproduced this on 2 separate SQL Server installs, 1 on a Windows XP SP2 machine, the other on a Windows Vista SP1 machine.


This looks a lot like a known issue that was hotfixed in SQL 2005 -- http://support.microsoft.com/kb/937745
Although I have not been able to reproduce this problem when connected to a SQL 2005 instance.


Thanks for any help,

Don
Details
Sign in to post a comment.
Posted by volatiless on 6/1/2010 at 10:08 AM
The client was unable to reuse a session with SPID 53, 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.


Posted by csoloway on 2/4/2010 at 10:45 AM
We have this on SQL Server 2008 Standard edition on a cluster. (10.0.2710) which is SP1 plus CU1. We're working through a plethora of hardware inconsistencies first, but this has been happening with increasing frequency. Happens when CPU and memory are high . One node is worse than the other.
Posted by MikaelHenrixon on 4/15/2009 at 1:59 PM
Still having this issue. We have tweaked our stored procedures etc so now it happens randomly... It's extremely frustrating!
Posted by Mikes2nd on 4/14/2009 at 7:04 AM
I too am recieving this error with 2008, i also have the latest rollups installed. After a reboot it is fine for about a day. then they start up again. They will flurry with linked servers make remote calls.

Posted by Microsoft on 1/22/2009 at 10:08 AM
Hello,

Thank you one more time for reporting this issue.

Unfortunately, we were not be able to reproduce this issue in our environment and other investigation steps we took were incoclusive. Without a repro we are out of options. Therefore we are resolving this bug as No Repro. If you are ever able to provide a consistent repro we would be very happy to get it and reactivate the investigation.

Thanks,
Krzysztof Kozielczyk (Microsoft)

Posted by William Vaughn on 11/17/2008 at 9:36 AM
While this issue is rare, I have seen it caused by flaky Network Interface Cards (NICs) as well as improperly configured switches and other network infrastructure. Generally, it's trigged when the network load exceeds capacity and the Ethernet protocol has gone over the falls (times out due to the inability to insert a packet or receive a timely response).

hth
Posted by Microsoft on 10/23/2008 at 3:07 PM
Thank you for reporting this issue, we appreciate your time. Our developers will try to investigate the problem, but without a consistent repro it will be very hard to find the root cause.

Thanks,
Krzysztof Kozielczyk

Sign in to post a workaround.