SQL server 2008 R2 Cluster issue RRS feed

  • Question

  • Hi All,

    Today morning we face some in issue in cluster environment we are getting below error message in error log continuously with different SPID's. due to that application connectivity get lost for 18 min. After reboot application server its came back normal.

    RAM size is 264 GB

    we restricted SQL max & min memory

    Min memory : 0 & Max memory 130 GB

    Service pack: SQL server 2008 R2 SP1

    Error: The client was unable to reuse a session with SPID 1871, 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.

    Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)   Jun 17 2011 00:54:03   Copyright (c) Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) 

    Tuesday, December 1, 2015 11:57 AM


All replies

  • see if this helps:


    Thanks, Andrew
    My blog...

    Tuesday, December 1, 2015 11:59 AM
  • Hi,

    AFAIK such issue was fixed in SQL Server 2008 R2 Sp3. I strongly suggest you to apply SQl Server 2008 r2 Sp3. See this support article

    Client was unable to reuse session ID part 1

    how it works Client was unable to reuse session id part 2

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My Wiki Articles


    Tuesday, December 1, 2015 12:25 PM
  • Hi Karthik Sree,,

    Is there any update for this issue after applying the SQL Server 2008 R2 Sp3 to the instance? If the issue persists, please provide us the detailed error message in SQL Server error log, so that we can make further analysis.


    Ice fan

    Ice Fan
    TechNet Community Support

    Tuesday, January 12, 2016 12:03 PM
  • HI,

    Thanks for your support.

    Issue raised due to poor storage on cluster machine after storage migration issue was resolved.


    Friday, January 15, 2016 6:00 AM