Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm having problems with my SQL Server 2008 installation (10.0.2531.0 - SP1 installed). It works as a database server for small hosting environment (about 500 sites).

I'm getting errors like this:

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

in Windows event log and when I run this:

SELECT  *  FROM sys.dm_os_performance_counters WHERE object_name = 'SQLServer:General Statistics'

I see that one of counters looks a little odd:

Logins/sec                   429
Connection Reset/sec         163459
Logouts/sec                  399
User Connections             30
Logical Connections          33

any ideas how to check what is causing this problem?

share|improve this question

closed as unclear what you're asking by Falcon Momot, Ward, Iain, mdpc, jscott Jul 15 '13 at 0:44

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question.If this question can be reworded to fit the rules in the help center, please edit the question.

Did you get anywhere with this? – Stewart Robinson Feb 25 '10 at 14:26
Our whole team is getting this error on one section of our code, were you able to find out any more info? Cheers – campo Aug 27 '10 at 1:22
This ended up being a malformed date value of a parameter we were passing in. Hope this helps someone :) – campo Aug 31 '10 at 22:42
Possibly related: – Michael Haren Nov 18 '13 at 19:08

There is an MSDN blog post about how to work with this error. It's not very good, but it does give some pointers as to how you can interpret the error code (failure ID).

Typically what happens is there is some expensive work to do while reinitializing the connection (such as access control and validation). This creates a potential race condition. While the server is doing this work, the client may time out and close the connection or do something else, creating an exception. Corrupt input, as campo mentioned in his comment, could well exacerbate that.

This isn't the only possible cause of the error; anything that causes an exception during the session reinitialization might cause this. The name of the error code is RedoLoginException.

share|improve this answer

protected by Zypher Mar 19 '11 at 1:51

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.