SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Connection Pooling Error - SQL 2008R2


Connection Pooling Error - SQL 2008R2

Author
Message
curious_sqldba
curious_sqldba
SSCertifiable
SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)

Group: General Forum Members
Points: 7598 Visits: 3696
We just migrated our from sql 2005 to sql 2008R2. Occasionally we do see the following error message and timeouts in our application

"Date 4/13/2012 3:30:37 PM
Log SQL Server (Current - 4/13/2012 8:00:00 PM)

Source spid172

Message
The client was unable to reuse a session with SPID 172, 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.
"


I did little research and this article "http://blogs.msdn.com/b/psssql/archive/2010/08/03/how-it-works-error-18056-the-client-was-unable-to-reuse-a-session-with-spid-which-had-been-reset-for-connection-pooling.aspx?wa=wsignin1.0&CommentPosted=true#commentmessage" seems to have something, but i couldn't find a solution. Has anyone faced this issue before? We are currently on sql2008R2 standard edition with SP1 +CU3.

P.S: I couldn't find a place for SQL 2008R2 questions , so i just posted here.
heymiky
heymiky
UDP Broadcaster
UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)

Group: General Forum Members
Points: 1487 Visits: 845
see if this helps
http://connect.microsoft.com/SQLServer/feedback/details/468478/sql-server-2008-periodically-does-not-accept-connections#

please post if you find the answer it seems like a problem for lots of people out there!

good luck
curious_sqldba
curious_sqldba
SSCertifiable
SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)

Group: General Forum Members
Points: 7598 Visits: 3696
SQLDBA360 (4/16/2012)
see if this helps
http://connect.microsoft.com/SQLServer/feedback/details/468478/sql-server-2008-periodically-does-not-accept-connections#

please post if you find the answer it seems like a problem for lots of people out there!

good luck


Issue seems to be the same but there isnt really a hotfix for this. We were able to resolve this issue by making few changes in the .net code. I will have to monitor for few days.
atchimule
atchimule
SSC Rookie
SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)

Group: General Forum Members
Points: 41 Visits: 424
Looks like it's memory issue..May be high pressure on CPU

1)Check max memory set .If not better to maximum memory
2)Threads unable to create for connections...check sp_configure
max worker threads

It should be dynamic value..It should not the fixed Value


Please refer below link you may get solution :

http://blogs.msdn.com/b/sqlsakthi/archive/2011/07/06/error-18056-state-29-the-client-was-unable-to-reuse-a-session-the-failure-id-is-29-after-upgrading-sql-2000-to-sql-2008-sp2.aspx

Thanks
Asr
Jayanth_Kurup
Jayanth_Kurup
SSCertifiable
SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)

Group: General Forum Members
Points: 5757 Visits: 1351
Most likely this issue is caused by the applcaition not opening and closing connections to the DB , you can also check you conenction pool setting in IIS. Rarely this issue occurs when the ram is out of space too. Check the number of connections to SQL Server and the Ram utlization just to be sure.

Max number of connection should be 0 and if your sure this is a minor issue you can timeout session after x minutes

Jayanth Kurup
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search