Software

Ask something
Question Locked

SSRS reports Time out

0 helpful
3 replies

by anqara05 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi, recently we had an issue with SSRS 2005 with one of our applications and had to remove and reinstall and reconfigure it. everything is working fine, except for certain large reports. when we run them i let it run and after approximately 35 minutes it ceases running with a message on the screen " Report processing has been canceled by the user". using subscriptions to drop the report file to a share failed with the same errors. tried running the report at off hours still same issue.
This report used to run before we reconfigured SSRS and all the config files have exactly the same settings.
any help is greatly appreciated.

3 replies

by robo_dev

How large are these reports?

Can you run the query behind the report manually?

From MSDN SQL Server Dev center:
"Setting Time-out Values

You can specify time-out values to set limits on how system resources are used. Report server supports two time-out values:

* A query time-out value is the number of seconds that the report server waits for a response from the database. This value is defined in a report.
* A report execution time-out value is the maximum number of seconds that report processing can continue before it is stopped. This value is defined at the system level. You can vary this setting for individual reports.

Most time-out errors occur during query processing. If you are encountering time-out errors, try increasing the query time-out value. If necessary, adjust the report execution time-out value so that it is larger than the query time-out. The time period should be sufficient to complete both query and report processing."

Some info on setting report processing timeouts:

http://msdn.microsoft.com/en-us/library/aa274413(SQL.80).aspx/ms155782.aspx

by anqara05

Changed few time out values, and still didn't make a difference.
A hotfix was released for the application we were using and there was some changes to their reporting portion of the application that seems to do the trick, and reports have been running good since then.

This discussion is closed to new replies.