Post reply

The underlying connection was closed:

  • May 26, 2010 at 3:08 pm

    #219372

    I am running a report that sends SQL to Oracle. The report appears to be running (the SQL is long running). After a 20 seconds or so the report stops and displays the following:

    The underlying connection was closed: An unexpected error occurred on a receive.

    Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.

  • May 27, 2010 at 7:26 am

    #1173307

    Seems as though you might be hitting a timeout somewhere. Can you better describe the connection for us? Are you querying a MS SQL Server that has a linked server to the ORacle DB or are your querying the oracle DB directly? There are a number of places that timeouts on the data connection could be defined. On the DataSource (in SSRS), on the SQL box, on the linked server to ORacle (if there is one) and on the oracle server itself.

    Check those settings.

    IF you run the same query from SSMS how long does it take to return your data, or does it time out there as well?

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • May 27, 2010 at 8:14 am

    #1173339

    I think I have figured it out. There are some servers between the development server and Oracle that monitor how long the response takes. I believe they are cancelling the query to Oracle because we don't want business partners running reports that take to long. I wish there was a better message so it is clear what it happening but I have other options and may attempt to run the SQL from a different source to see how it runs there.

    Thanks!

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply