KBA45024: Timeout when restoring or uploading scheduled reports

Knowledge Base Article	45024
Applicable Versions	Report Manager 4.x and greater
Date Created/Updated	January 8, 2013

Issue

Restoring or creating scheduled reports fails and appears to timeout. You may get warnings such as: A scheduled task in the SQL Server Agent queue has been modified or deleted. This problem may occur only at some times of the day and not others.

Solution

SolarWinds MSP recommends that you review your system to ensure that enough resources have been allocated for optimal performance. Typically when this issue appears, the system could benefit from having additional RAM allocated.

In addition, this problem may also result when web server services are overloaded by requests. Therefore, we also recommend that you change some of the settings for the report server web services to allow the server to handle more connections. Changing the following three settings in the rsreportserver.config file will allow for restores and upgrades without timing out:

• MaxActiveReqForOneUser
• DatabaseQueryTimeout
• MaxScheduleWait

Refer to the following MSDN articles:

• http://msdn.microsoft.com/en-us/library/ms157273.aspx for more information about the rsreportserver.config file
• http://msdn.microsoft.com/en-us/library/958ef51f-2699-4cb2-a92e-3b4322e36a30 for details on file location if you are having trouble locating it

Instructions to change SQL Server Reporting Services web config file

Use caution when modifying configuration files. After modifying, check the trace log files to ensure there are no errors.

1. On your Report Manager server, locate the rsreportserver.config file.
2. The file path may vary. Here is a sample location:
   1. C:\Program Files\Microsoft SQL Server\MSSQL.n\Reporting Services\ReportServer folder
   2. It may also be in the bin folder. For more information on this file, refer to:http://msdn.microsoft.com/en-us/library/958ef51f-2699-4cb2-a92e-3b4322e36a30.
3. Open the file through a code editor, such as Notepad (do not use Textpad).
4. Save a copy of the file somewhere handy, in case you have to roll back the changes.
5. Change the default values for the following settings:
   • MaxActiveReqForOneUser
   • DatabaseQueryTimeout
   • MaxScheduleWait
6. Refer to the table below for the New Value for each of the settings.

   Setting	Description	Default Value	New Value
   MaxActiveReqForOneUser	Specifies the maximum number of reports that one user can process at the same time. Once the limit is reached, further report processing requests are denied. Valid values are 1 to a maximum integer. The default is 20. Note that most requests process very quickly so it is unlikely that a single user will have more than 20 open connections at any given time. If users are opening more than 15 process-intensive reports at the same time, you might need to increase this value. This setting is ignored for report servers that run in SharePoint integrated mode.	20	30
   DatabaseQueryTimeout	Specifies the number of seconds after which a connection to the report server database times out. This value is passed to the System.Data.SQLClient.SQLCommand.CommandTimeout property. Valid values range from 0 to 2147483647. The default is 120. A value of 0 specifies an unlimited wait time and therefore is not recommended.	120	240
   MaxScheduleWait	Specifies the number of seconds the Report Server Windows service waits for a schedule to be updated by SQL Server Agent service when Next Run Time is requested. Valid values range from 1 to 60. In the default configuration file, MaxScheduleWait is set to 5. If the report server cannot find or read the configuration file, the server defaults MaxScheduleWait to 1.	5	10

7. Save and close the file.
8. Check the trace log files to verify that you made the changes correctly.
9. Restore or upload scheduled reports.