Which had been reset for connection pooling

You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. My SQL Server error log shows Share this: Twitter Facebook. Like this: Like Loading Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:.

If different groups of web servers have the same connection string syntax but with slightly different whitespace, would this cause the server to use another connection pool? I don't think memory is the issue as the box seems to have a decent page lfe expectancy. Auto close is not enabled. The way my network is set up I suspect it's the network's automatic closing of tcp sessions after being 5 minutes idle that's the issue - neither the db nor the client is closing the session so the connection pool still thinks the connection is open and tries to use it only to find it's not really open anymore.

You don't mention how the network between your web servers and db is configured, maybe your case is similar.

If I'm wrong on that, please let me know. Over the last few days it has spat out the following messages about the resetting connection pools: The client was unable to reuse a session with SPID , which had been reset for connection pooling. Error log reads: Error: , Severity: 20, State: I've been trying to help as much as I can by finding links that seems useful, but if you are interesting in reading these, or you do not find them applicable, there is not more than I can do.

Message The client was unable to reuse a session with SPID , which had been reset for connection pooling. The failure ID is This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. Message Error: , Severity: 20, State: The same symptoms may not necessarily require the same resolution.

Rather than add to an answered thread that is years old, I suggest you ask a new question. And here in the forums, you need to start a new thread describing your problem from start to end. Piggybacking on old threads as you have been doing in several forums, is not going to help you. Learn More. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. SQL Server Security. Sign in to vote. Tuesday, December 11, AM.

Tuesday, December 11, PM. The service pack only relieves you from the noise of state 29 for message Login failed for user 'XXX'.

Reason: Failed to open the database 'XXX' configured in the login object while revalidating the login on the connection. Error: , Severity: 14, State: You must be logged in to reply to this topic. Login to reply. Post reply. October 25, at am Finally i have restarted sql server and suddenly all these messages disappear The client was unable to reuse a session with SPID , which had been reset for connection pooling.

Seems no other go except raising MS case.