Connection Pooling Error - SQL 2008R2

Question

Connection Pooling Error - SQL 2008R2

curious_sqldba

SSC-Dedicated

Points: 36494
More actions
April 13, 2012 at 10:23 pm

#256403

We just migrated our from sql 2005 to sql 2008R2. Occasionally we do see the following error message and timeouts in our application
"Date4/13/2012 3:30:37 PM
LogSQL Server (Current - 4/13/2012 8:00:00 PM)
Sourcespid172
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.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

heymiky SSCarpal Tunnel Points: 4875 More actions · Answer 1

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 SSC-Dedicated Points: 36494 More actions · Answer 2

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 SSC Journeyman Points: 91 More actions · Answer 3

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 SSC-Insane Points: 22967 More actions · Answer 4

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[/url]