Error: 18056, Severity: 20, State: 29

Question

Post reply

Error: 18056, Severity: 20, State: 29

NickDBA

Hall of Fame

Points: 3792
More actions
December 1, 2011 at 3:36 am

#248755

Hi, we have a .net web application which experienced timeouts connecting to our SQL Server last night (for a period of about 10 mins).
The only thing in the SQL logs is:
-----------------------------------------------------------
Error: 18056, Severity: 20, State: 29.
The client was unable to reuse a session with SPID xx, 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.
*This is repeated for SPID xx (6 diferent SPIDs)
-----------------------------------------------------------
Reading a lot of conflicting information regarding this. Has anybody seen / diagnosed / remedied this issue in their own production environment.
We're running:
SQL Server 2008 Web Edition (SP1) x64
Windows Server 2008 Standard (SP1)
2 x 2.5 Ghz (quad core)
16 Gb RAM

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

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

Ant-Green SSC Guru Points: 113507 More actions · Answer 1

only other time i have seen this is when the server was rebooting due to automatic updates.

did your server reboot last night?

NickDBA Hall of Fame Points: 3792 More actions · Answer 2

Hi, no the server stayed up (and is still up) and is responding fine. We've not applied any updates.

Ant-Green SSC Guru Points: 113507 More actions · Answer 3

can you post your full error log

also MS say they have resolved the bug in this hot fix http://support.microsoft.com/kb/2543687 after a did a google search.

NickDBA Hall of Fame Points: 3792 More actions · Answer 4

I did see that post, but the msg we're getting out the application is:

System.InvalidOperationException:

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

Which is different to the error msg in the KB article.

Ant-Green SSC Guru Points: 113507 More actions · Answer 5

It would seem that your connection pool isn't clearing out dead/idle connections, or something spawned to many concurrent connections and the limit was reached.

Wasn't any changes to the app yesterday or something was disabled which used to clear out the connection pool or restart IIS, or something along them lines.

A new process which occurs in the app at around the time of the errors? which needs multiple connections?

Devendrakumar SSC-Forever Points: 42493 More actions · Answer 6

Hope you are not doing any load testing on the server with Multiple Logins.

Try this.

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