I checked my query from backend. It takes only 4 second the get the result.
I have tried to change the SQL select command's Command timeout = 1200.
What setting I can changed to extend the timeout so that report viewer can shows the result?
5 Answers, 1 is accepted
By default the connection timeout of the web server (IIS) is 120 secs. You can receive this error if the report generation time is more than this timeout. How to modify it is explained in the Setting Connection Timeout article. I have also attached a screenshot for IIS6.
Hope this helps.
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Would appreciate any feedback.
This forum thread is more than two years old and you are the first one to bring it up. It would be best if you open a support ticket where you provide detailed information about your setup or even better, provide us with a runnable sample project that exhibits the problem. You did not provide any information whether this is a problem only when hosting the application in IIS or it occurs on the built-in server as well.
the Telerik team
Hi Telerik Team,
We are facing a similar issue. There is a Telerik report with two datasources. Queries of the datasources when run in SQL server directly shows result withing 4secs. The same query when run by the report either times out or takes a long time to show up.
Connectionstring is dynamically updated. There are 6 tables in the report with one row each. When the row is clicked, another report opens.Parent report takes a long time to load for the first time. Child report opens quickly.
CommandTimeout is set with value 600. Connection Time-out in IIS is set to 601. Still there is no improvement. On running 'dbcc freeproccache' in SQL server, the report gets generated in a few seconds. But, the next time report is generated, the issue is back. We are working with ASP.Net Webforms Telerik Reporting 184.108.40.2067.
Please suggest what could be wrong and what could be done to see the report quickly. Running 'dbcc freeproccache' often is not feasible.
Each data item executes its data retrieval method on its own. Beside retrieving data the reporting engine needs time to create objects and resources related to the rendered document.
In case of retrieving large amounts of data records:
- Check Performance Considerations;
- Set the SqlDataSource.CommandTimeout to a greater value and provide a greater Connection_Timeout in the connection string.
- Verify that the machine can handle the report processing and rendering (CPU and memory). You can test hosting in a web farm and to enable the corresponding viewer's cache - Cache Management.
- Test data-binding approaches where a container's data is reused by nested data items - Use DataObject as a datasource for nested data items (Table, List, Crosstab, Graph).
Telerik by Progress