"The operation has timed out" when rendering a report

Question

Hello,

I'm using ReportingServices 2008 and I've this message "The operation has timed out" when rendering a report with some parameters.

 I've set in the execution properties of this report : Do not apply the expiration time for the execution of the report.

When I look the ExecutionLogStorage table from ReportServer DataBase I see that I've no message for this report when timeRendering is 21109ms. When I change the report parameters to obtain more data, the timeRendering is 76866ms and I've the message "The operation has timed out".

Have you any tips for solving this problem?

Thanks in advance,

Ana Fróis

Answer 1

did you check your dataset TSQL queries/SP's in SSMS?

---

Regards, KarthikShanth. "Mark as Answer" if this helps you!

Answer 2

What is the source of data that populates your report??? Is it a direct SQL query or a Stored Procedure?? You can try decreasing the amount of data returned to the report gradually and find out at what point does the query stop responding and times out ultimately.

You might end up tuning your query/database for faster data access. You can also try increasing the Query Timeout setting for long running queries on your server and see if tha makes any difference.

Hope this helps.

 

Cheers!!

Muqadder.

Answer 3

Yes, I did and there are no problems for getting the data. It takes +/-2min.

 

Answer 4

I'm using a Stored Procedure and I've no problems when I execute it in the SQL Server Management Studio. It takes only about 2min.

I launch the report with an ASP page and I rend it in a PDF format. 

I get the report (in the PDF format) when the number of lines are about 5000 (about 400 pages) and I have the problem "the operation has timed up" when the number of lines are about 7600.

Thanks in advance,

Ana 

 

Answer 5

Hi, You might want to look into the web.config file.

If your running in SharePoint integrated mode

1. change  C:\Inetpub\wwwroot\wss\VirtualDirectories\80\web.config
2. From  <httpRuntime maxRequestLength="51200" />
3. To  <httpRuntime maxRequestLength="51200" executionTimeout = "9000" />

see http://msdn.microsoft.com/en-us/library/ms159704(SQL.90).aspx

A similar setting exists in rsreportserver.config, a quick google should find it.

 

Regards
Dan

Answer 6

Hello

Thanks for your ideas but, I still have the same problem

I also saw this page

http://blogs.msdn.com/mariae/archive/2009/09/24/troubleshooting-timeout-errors-in-reporting-services.aspx

I checked all the different timeouts that could be affecting the execution of my report and I changed all settings that were suggested.

1-The query execution timeout of the report

2-The report execution timeout property

3-The timeout  setting of the sessionState in the web.config file in the folder  “C:\Programme\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager”

On the server:

4-the timeout caused by the session

5-in RSReportServer.config file the key: <Add Key="DatabaseQueryTimeout" Value="7200"/>

 6 - the execution timeout settings in the web.config files.

And I RESTART IIS.

Thanks anyway for your help.

Ana

Answer 7

Ahh I see!! The problem is not with the execution of your Stored Procedure or the data volume. If I got it right, you get the data fine, but when writing it to PDF is where it times out??

If that is the case, you might try displaying the data in a SSRS report first (not PDF) and see if that works okaye. This will ensure the SQL engine and the STored Procedure are not among the real culprits.

Hope this helps.

 

Cheers!!

Muqadder.

Answer 8

Hi Ana,

Did you get any solution? I am facing same issue. My report is processing 460000 Records and converting them in PDF format.

Abhijeet

Answer 9

i am also getting the same error. 

Answer 10

Hi,

If you are using ReportExecutionService to render report, then increase the ReportExecutionService.timeout property value.

Hope this helps!

Thanks!

Siva

Answer 11

Thank you! This is so simple yet I had to look at a lot of pages to find this.