Reporting Services 2005 Timeout When Exporting Through a Web Service
We faced the same issue as here: Huge PDF export report
We are exporting a report from SSRS using .asmx web services. Exporting via Report Manager works great calling at times from code. We get:
Exception Message: The underlying connection was closed:
An unexpected error occurred on a receive.
We tried the same solutions that Dustin Brooks tried to use in his post.
- set the HttpRuntime ExecutionTimeout to 3 hours on the report server
- disabled http keep alives on report server
- increased script timeout on report server
- set the report to never go to the server
- set the report timeout to a few hours when calling the client
I hope someone might come across a solution in the year that has passed since their request.
source to share
I also ran into this issue during my experience with SSRS 2005 and found this post using MSDN MVP in the msdn forum:
The good news for this thread is SQL 2008 Reporting Services, which is available and has superior scalability for larger reports than the previous ones.
I can also say that we (the Reporting Services team) heard a message about really large reports and the reasons for doing them. To be honest, it came as a surprise to us that people would want to run such a large report interactively on a web page and wait for it to return. We also captured our perception of the script in SQL 2008 Reporting Services, which we laid out to access reports of any size (millions of data rows). You will (hopefully) be pleasantly surprised at how well we can come across this script with the latest version. That being said, you still need the right hardware to run them efficiently (lots of CPU and memory), and you will need to adjust the query execution time, query, etc. accordingly.
Providing really large reports for a browser session is not necessarily desirable. We would recommend using PDF sharing so that your user does not expect a web page response.
Hope it helps, -Lukasz
Not sure if this helps, but I have since switched to SSRS 2008 (I know this is not always an option).
source to share