locked
SQL 2008 R2 - A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) RRS feed

  • Question

  • Hi,

     

    We are using SQL Server 2008 R2 - on Windows Server 2008 - Enterprise (SP2), with 16-GB of RAM. The SQL server is restricted to use 12-GB of RAM on the DB server.

    The client is a web-server running Windows 2008 Enterprise (SP2), with IIS 7 and latest service packs.

     

    Problem: Every once in a while, when trying to retrieve data (usually binary data since we store documents in the SQL server database) we get the error message:

    Msg 233, Level 20, State 0, Line 0

    A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

    The Event Log has the following error logged in:

    Log Name:      Application
    Source:        MSSQLSERVER
    Date:          4/25/2011 11:10:57 AM
    Event ID:      7886
    Task Category: Server
    Level:         Error
    Keywords:      Classic
    User:          xxxxxxxx
    Computer:      xxxxxxxx

    Description:

    A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSSQLSERVER" />
        <EventID Qualifiers="49152">7886</EventID>
        <Level>2</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-04-25T15:10:57.000Z" />
        <EventRecordID>164628</EventRecordID>
        <Channel>Application</Channel>
        <Computer>XXXXXXX</Computer>
        <Security UserID="S-1-5-21-1815965802-3523341392-552917294-1009" />
      </System>
      <EventData>
      <Binary>CE1E00001400000008000000500054004B0044004200300033000000150000004D00440049006E0073007500720061006E006300650041007500740068005F00500052004F0044000000</Binary>
      </EventData>

    </Event>

    We have disabled the Shared-Memory protocol on the Client machine, however the error keeps coming, and the only way to fix this is to re-boot the server. After which everything starts working fine.

    I have checked all related articles on this forum and none of them point to a way forward. This is a production machine and we need to get this fixed ASAP as this problem is getting more and more frequent. The DB size is crossing the 30-GB mark but not sure if that could be a cause of the problem.

    Is this a known issue?? Are there any hotfixes available?

    A quick response would be highly appreciated.

    Thanks in Advance.

    Ritz. 

    Monday, April 25, 2011 3:28 PM

Answers

  • Hi Ritzzz,

    I'm guessing that my solution to this will not be terribly helpful in your situation. Basically, do not run production SQL Boxes on VMs. There are all sorts of issues. This is only one. You will also find things like Service Broker loosing data with no apparent trace, DB Mirroring endpoints disapearing for no reason, and general poor performance.

    If you must use a VM, use Hypre-V, because atleast it is supported by MS (If you have Win Srv 08R2 and SQL 08 or higher) and then, atleast you can raise support calls.

    In your precise situation, I really hope somebody else has a more useful workaround, but I have spent a fair amount of time playing with it, and I have never found one.

    Sorry... :(


    Peter Carter-Greenan http://sqlserverdownanddirty.blogspot.com/
    • Proposed as answer by Peja Tao Wednesday, April 27, 2011 7:57 AM
    • Marked as answer by Alex Feng (SQL) Tuesday, May 3, 2011 4:10 AM
    Tuesday, April 26, 2011 1:48 PM

All replies

  • Is the server a VM?

    I have encountered similar issues several times and it has always been on Virtual Servers...


    Peter Carter-Greenan http://sqlserverdownanddirty.blogspot.com/
    Monday, April 25, 2011 4:23 PM
  • Hi Pete,

     

    Thanks for the response. And you are right.  The server is a VM running in a cloud. 

    Have you been able to find a resolution to this? Or are there any workarounds? Any information would greatly help, because this rebooting of the server is not a good option as it sometimes results in database inconsistency errors, which are not even resolved by the DBCC fix data option.

     

    Please let me know.

    Thanks in advance.

     

    Ritz.

    Tuesday, April 26, 2011 6:56 AM
  • Hi Ritzzz,

    I'm guessing that my solution to this will not be terribly helpful in your situation. Basically, do not run production SQL Boxes on VMs. There are all sorts of issues. This is only one. You will also find things like Service Broker loosing data with no apparent trace, DB Mirroring endpoints disapearing for no reason, and general poor performance.

    If you must use a VM, use Hypre-V, because atleast it is supported by MS (If you have Win Srv 08R2 and SQL 08 or higher) and then, atleast you can raise support calls.

    In your precise situation, I really hope somebody else has a more useful workaround, but I have spent a fair amount of time playing with it, and I have never found one.

    Sorry... :(


    Peter Carter-Greenan http://sqlserverdownanddirty.blogspot.com/
    • Proposed as answer by Peja Tao Wednesday, April 27, 2011 7:57 AM
    • Marked as answer by Alex Feng (SQL) Tuesday, May 3, 2011 4:10 AM
    Tuesday, April 26, 2011 1:48 PM