none
Physical connection is not usable

    Question

  • One of our stores is often getting the following error: "A transport-level error has occurred when sending the request to the server. (provider: Session Provider, error: 19 - Physical connection is not usable"

    The connection type is IDSL and may be intermittent but, I have not seen this error before.  Any idea how to trace it and how to fix it?  I am using connection pooling - FYI.

    Wednesday, June 30, 2010 6:12 PM

Answers

  • I found this article http://msdn.microsoft.com/en-us/library/8xx3tyca.aspx, which talks about SQL Server Connection Pooling (ADO.NET) in .Net 4.0. It mentions that "The pooler maintains ownership of the physical connection. ...". So it looks like physical connection = active connections maintained by the pooler.
    • Marked as answer by Steve Frase Friday, September 30, 2011 5:12 PM
    Thursday, July 01, 2010 3:56 AM

All replies

  • try to ping your server and checker whether you are able to connect, if not please check your n/w connection
    Everything about SQL Server | Experience inside SQL Server -Mohammad Nizamuddin
    Wednesday, June 30, 2010 7:49 PM
  • Are you using .Net Framework in you app, if so, what version is it? Just wondering if that could be the version of the connection driver.
    Thursday, July 01, 2010 12:26 AM
  • Yes.  I'm using .Net 4.0 currently.  I have seen other types of connection issues but, this one is different and, someone added that return code under a particular set of curcumstances.  I just want to know what those circumstances are.  In other words, why mention the "physical connection" rather than "timeout", "login error", "connection dropped", etc...

    Thursday, July 01, 2010 2:12 AM
  • I found this article http://msdn.microsoft.com/en-us/library/8xx3tyca.aspx, which talks about SQL Server Connection Pooling (ADO.NET) in .Net 4.0. It mentions that "The pooler maintains ownership of the physical connection. ...". So it looks like physical connection = active connections maintained by the pooler.
    • Marked as answer by Steve Frase Friday, September 30, 2011 5:12 PM
    Thursday, July 01, 2010 3:56 AM
  • I found interesting bug about this error. My database version is 2008 R2. When inserting datetime field like '0001.01.01 00:00', database give this error :S

    Detail information: http://gunce.mustafakerim.com/?p=439

    Thursday, September 19, 2013 7:12 AM