InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 16:30:46 GMT20http://www.sqlservercentral.com/Forums/Topic1283574-391-1.aspxMost 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 minutesTue, 15 Jan 2013 04:44:07 GMTJayanth_Kuruphttp://www.sqlservercentral.com/Forums/Topic1283574-391-1.aspxLooks like it's memory issue..May be high pressure on CPU1)Check max memory set .If not better to maximum memory2)Threads unable to create for connections...check sp_configuremax worker threadsIt should be dynamic value..It should not the fixed ValuePlease 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.aspxThanksAsrTue, 15 Jan 2013 04:40:21 GMTatchimulehttp://www.sqlservercentral.com/Forums/Topic1283574-391-1.aspx[quote][b]SQLDBA360 (4/16/2012)[/b][hr]see if this helpshttp://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[/quote]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.Mon, 16 Apr 2012 08:54:10 GMTcurious_sqldbahttp://www.sqlservercentral.com/Forums/Topic1283574-391-1.aspxsee if this helpshttp://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 luckMon, 16 Apr 2012 06:28:07 GMTSQLDBA360http://www.sqlservercentral.com/Forums/Topic1283574-391-1.aspxWe just migrated our from sql 2005 to sql 2008R2. Occasionally we do see the following error message and timeouts in our application[b]"Date 4/13/2012 3:30:37 PMLog SQL Server (Current - 4/13/2012 8:00:00 PM)Source spid172MessageThe 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."[/b]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.Fri, 13 Apr 2012 22:23:20 GMTcurious_sqldba