Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Error: 18056, Severity: 20, State: 29 Expand / Collapse
Author
Message
Posted Thursday, December 1, 2011 3:36 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 2:07 AM
Points: 359, Visits: 928
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
Post #1214453
Posted Thursday, December 1, 2011 3:49 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Monday, December 8, 2014 1:45 AM
Points: 5,221, Visits: 5,120
only other time i have seen this is when the server was rebooting due to automatic updates.

did your server reboot last night?




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1214463
Posted Thursday, December 1, 2011 3:54 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 2:07 AM
Points: 359, Visits: 928
Hi, no the server stayed up (and is still up) and is responding fine. We've not applied any updates.
Post #1214467
Posted Thursday, December 1, 2011 3:58 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Monday, December 8, 2014 1:45 AM
Points: 5,221, Visits: 5,120
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.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1214471
Posted Thursday, December 1, 2011 4:30 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 2:07 AM
Points: 359, Visits: 928
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.
Post #1214497
Posted Thursday, December 1, 2011 4:45 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Monday, December 8, 2014 1:45 AM
Points: 5,221, Visits: 5,120
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?




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1214510
Posted Thursday, December 1, 2011 7:51 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 6:53 PM
Points: 1,932, Visits: 1,589
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


Dev

Devendra Shirbad | BIG Data Architect / DBA | Ex-Microsoft CSS (SQL 3T)
*** Open Network for Database Professionals ***

LinkedIn: http://www.linkedin.com/in/devendrashirbad
Post #1214642
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse