Edit this page

Configure the Report Rendering Engine

Configuration File

The reports rendering engine can be fine-tuned using a dedicated configuration file, called TelerikReporting.config. This file gets automatically created on the server when it is started for the first time. The default location of this file is C:\Program Files (x86)\Progress\Telerik Report Server\Telerik.ReportServer.Web\TelerikReporting.config and affects the live report preview generation and the WebApi 'documents' endpoint. The Report Server instance needs to be restarted manually in order to apply the changes.

Telerik.Reporting configuration section

To become effective, open the TelerikReporting.config file and uncomment the TelerikReporting configuration section registration:

<?xml version="1.0" encoding="utf-8" ?>
    <section name="Telerik.Reporting" type="{0}" allowLocation="true" allowDefinition="Everywhere" />
    <restReportService workerCount="3" clientSessionTimeout="15" reportSharingTimeout="0" />

restReportService element settings

The following are the attribute settings applicable to the Report Server:


Optional integer attribute. Specifies the combined count of report rendering worker threads that render report documents for the live report preview and export and for the 'documents' WebApi endpoint. The default value is equal to the logical processors available on the server machine.


Optional integer attribute. Specifies the value in minutes indicating how long a client report preview session will be preserved in the service storage after the last interaction with the report content from this client. The value must be greater than zero. The default value is 15 minutes.


Optional integer attribute. Specifies the value in minutes indicating how long a rendered report document from a client will be eligible for reuse for another clients' request. The value must be greater than or equal to zero. A zero value will prevent rendered report document reuse. The default value is zero. Changing this is highly recommended for a user-intensive Report Server deployment.

Is this article helpful? Yes / No
Thank you for your feedback!

Give article feedback

Tell us how we can improve this article