[ACCEPTED]-Reporting Services Report Timeout-reportingservices-2005
You can fiddle with any of the following:
1) Modify SessionTimeout and SessionAccessTimeout system properties.
Here 11 is a sample script for rs.exe which will 10 set these values for you:
Public Sub Main()
Dim props() as [Property]
props = new [Property] () { new [Property](), new [Property]() }
props(0).Name = "SessionTimeout"
props(0).Value = timeout
props(1).Name = "SessionAccessTimeout"
props(1).Value = timeout
rs.SetSystemProperties(props)
End Sub
You can run this 9 script with the following command:
rs -i sessionTimeout.rss -s http://yourserver.com/reportserver -v timeout="6000"
The timeout 8 is expressed in seconds, so this example 7 sets the SessionTimeout and SessionAccessTimeouts 6 to about an hour and a half.
(via http://blogs.msdn.com/b/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx)
2) Change Report Execution Timeout via Report Manager Open 5 Report Manager At the top of the page, click 4 Site Settings. This opens the General Properties 3 page of the site.
Report Execution Timeout Specify 2 whether report processing times out after 1 a certain number of seconds. (via http://msdn.microsoft.com/en-us/library/ms181194.aspx)
3) Set the HttpRuntime ExecutionTimeout
- Open the ReportServer’s Web.config file by going to Start -> Administrative Tools -> Internet Information Services.
- From there, expand Web Sites -> Default Web Site, and click on ReportServer. On the right-hand pane, right-click ‘Web.Config’ and select ‘Open’.
- Locate the HttpRuntime parameter. If it doesn’t exist, you will have to create it within the section.
- Set the executionTimeout value to ‘10800’ (3 hours) as shown below:
<system.web>
<httpRuntime executionTimeout = "10800" />
</system.web>
4) Increase the script timeout on the report server
- Go onto your Reporting Server and open up Internet Information Services; right-click on the ReportServer and select Properties.
- Go to the Options tab, and set the ASP Script timeout to 300 seconds (this didn't really work for me).
5) Set the report to never time out on the server
- Open your web browser on the server and go to http://yourserver.com/Reports
- Navigate to the Report location and click on the problem report(s).
- On the left-hand pane, click on Properties.
- In the ‘Report Execution Timeout’ click the ‘Do not timeout report execution’. (via http://geekswithblogs.net/ssrs/archive/2009/10/30/steps-to-resolve-ssrs-timeout-issues.aspx)
There is a report execution timeout setting 11 for each report in SSRS. By default, they 10 are set to use the default system setting, but 9 they can be customized through the report 8 manager or SSMS.
Are you sure it isn't a 7 database command timeout? That could be 6 adjusted in the connection string. Is it 5 the report that is inefficient or the query? 250 4 pages for a SSRS report really isn't that 3 bad. We run reports that large often. SSRS 2 actually outperforms most of the other reporting 1 engines we use.
More Related questions
We use cookies to improve the performance of the site. By staying on our site, you agree to the terms of use of cookies.