ADO Connection Pooling Error: "The client was unable to reuse a session with ..."

Hello,

We are running SQL2K5 and have a Web server with a family of sites all sharing an identical connection string to enable ADO connection pooling between them. Today for about 20 minutes we had several (all ) connections from one site that uses a specific DB get a connection reuse error which showed in out SQL logs:

DESCRIPTION: The client was unable to reuse a session with SPID #, which had been reset for conection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

We also have SQL Server slowdown and log in problems from other applications that seemed a symptom of this, or some third unknown cause. Note, the # means the run-time spid number was inserted. The misspelling "conection" comes right out of sys.messages (it is not our custom error):

select top 10 * from sys.messages where message_id = 18056

The immediately preceeding error in the SQL Log was always:

Message
Error: 18056, Severity: 20, State: 29.

Where Severity and State vary, but "Error: 18056" is consistent, although I can find no documentation on "Error: 18056" through Google or MSDN.

Also, the "The client was unable to reuse a session ..." error seems not to be referred to anywhere.

In our IIS logs, the matching entries are of the form:

[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.

and

Invalid connection string attribute

My questions: Does anyone have experience with this error We have real good history with ADO connection pooling, but can a "bad" connection be pooled, and if so can it be "flushed" or the pool "drained"

Thank you for anything you have to offer!

Answer this question

ADO Connection Pooling Error: "The client was unable to reuse a session with ..."

Ella H
We have a similar issue. Seems that when users change passwords things go wrong intermittently and we end up at this error message. Can anyone give me a reference to the existing case raised with Microsoft so we can follow up. Thanks
Manivannan.D.Sekaran

We have opened a case with MS on this. I am no longer directly involved in it, but MS has admitted they can duplicate the problem on the their end and it is due to locking in the security cache introduced by creating logins. We can reproduce the problem on our end by the CREATE LOGIN process, but the problem while detectable at any level only causes real problems (such as this error message) when many logins (say 50 or more) are created in rapid succession, near simultaneously.

The process of resolution with MS seems to be moving very slow. I suspect it will be a hotfix if not a future SP if it is every resolved.
Duelund
Currently, our resolution is to no longer use the native SQL Login tables as we have been. We are creating customer tables to hold UIDs, passwords, etc. and doing our own authentication which may be integrated with AD.
rrmadhav

We are using the SQL OLEDB provider. Specifically in our connection string is the name value pair: "Provider=SQLOLEDB.1"
WBI
I don't believe there is currently a way to flush the pool since the OLE DB resource pooling is done in an implicit manner.

However you may want to check the following link to control the maximum life time of the pooled connection:

http://support.microsoft.com/default.aspx scid=kb;en-us;301384

Thanks
Suroor
Tanweer Ahmed
I'm getting the same error. I not sure what is causing it at this time. Please make sure you post your resolution on this forum.

Thanks in advance.
Len Weaver

What provider are you using in your ADO code
msebald
Hi guys

I'm just experienced the same problem too. But, my connection is using ODBC

Anyone the solution please email me at:

sorgavana@yahoo.com
ADO Connection Pooling Error: "The client was unable to reuse a session with ..."

Answer this question