client was unable to reuse a session?

Question

client was unable to reuse a session?

SQL Galaxy

One Orange Chip

Points: 29472
More actions
August 20, 2013 at 11:33 pm

#281368

Hi
I am received email alert frequently as below error messages.
DESCRIPTION:The client was unable to reuse a session with SPID 119, 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 Fix that issues http://support.microsoft.com/kb/2543687 by updating latest service pack3 & CU1 of SP3.
Currently - SQL Server 2008 standard edition with SP1
Can we update SP3 and CU1 for resolve that issues? please suggesion me..
Thanks
ananda

Viewing 8 posts - 1 through 7 (of 7 total)

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

HanShi SSC-Dedicated Points: 33507 More actions · Answer 1

I don't know if the SP and CU will solve your problem. But it's always a good thing (for both security and stability) to apply the latest SP to your software. So I recommend to install SP3 on your instance.

Are you able to reproduce the problem on a test-instance? If so, you can install the CU and test if it solves your problem.

** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 2

Ok..

That error was fixed with CU6 of SP3.. SQL SERVER 2008 32 bit

Pl. confirm as below steps for updating SP3 and CU6

1. Install SP3

2. Install CU1, CU2....CU6 ( i need to apply all the CU of SP3)

Thanks

HanShi SSC-Dedicated Points: 33507 More actions · Answer 3

ananda.murugesan (8/21/2013)
Ok..
That error was fixed with CU6 of SP3.. SQL SERVER 2008 32 bit
Pl. confirm as below steps for updating SP3 and CU6
1. Install SP3
2. Install CU1, CU2....CU6 ( i need to apply all the CU of SP3)
Thanks

No, that's incorrect. You only need to apply the latest CU. From the Technet document "SQL SP & CU recommendations":

Cumulative update package for SQL Server contains hotfixes for the Microsoft SQL Server issues that have been fixed since the release of SQL Server SP. We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.

** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 4

ok.. Thanks for replay

First update SP3 and then apply latest Cumulative update package 12 for SQL Server 2008 SP3, is it correct ?

HanShi SSC-Dedicated Points: 33507 More actions · Answer 5

ananda.murugesan (8/21/2013)
...then apply latest Cumulative update package 12 for SQL Server 2008 SP3, is it correct ?

It's not required to apply the -latest CU-. It required to apply the -latest CU containing the needed hotfix-. But if you install the most recent CU, the needed hotfix is included.

** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 6

I got it....

In my case current service pack is (sp1) already updated on Instance.

I could install SP3 only and not required latest CU12..

In SP3 included that hot fix as below errors

The client was unable to reuse a session with SPID 119,

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.

HanShi SSC-Dedicated Points: 33507 More actions · Answer 7

ananda.murugesan (8/20/2013)
Microsoft Fix that issues http://support.microsoft.com/kb/2543687 by updating latest service pack3 & CU1 of SP3.

According to your original post, you also need to apply both SP3 and CU1 of SP3.

** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **