Reporting HTML 5 Viewer timeout

[Hesham Desouky]

I am using the Telerik Reporting with HTML 5 Viewer Q2 2015. With specific report it needs high processing i increased the timeout of the sql data source command to 600 seconds (10 minutes).

 When rendering the report in the HTML 5 Viewer i receive the following error :

 Internal Server Error
Timeout expired. The timeout period elapsed
prior to completion of the operation or the server is not responding.
This failure occurred while attempting to connect to the routing
destination. The duration spent while attempting to connect to the
original server was - [Pre-Login] initialization=112; handshake=27;
[Login] initialization=0; authentication=0; [Post-Login] complete=1;
The wait operation timed out

This error occurs just 40 seconds after pressing the preview button

On the FREB log i see that the timeout occurs on the ReportController GetDocumentInfo method.

 Any thoughts?

[Katia]

Hello Hesham,

Please try the following:

• try to use a larger value for the CommandTimeout property


• try to use a larger value in the connection string as well


• extend the execution timeout in the web.config file, for example  <httpRuntime executionTimeout="7200" />

If this does not resolve the issue, you might consider filtering the data on the retrieval. We suggest information in Filtering Data and Performance Considerations help articles and see what can be applied to your project.

Regards,
Katia
Telerik

[Hesham Desouky]

Hi Katia,

 Thanks for your reply.

I tried the CommandTimeout property but it seems it has no effect.

The connection stirng timeout i believe it is for conneciton establishment and has nothing to do with command execution.

 I will try the httpruntime setting (https://msdn.microsoft.com/en-us/library/e1f13641%28v=vs.100%29.aspx) it looks like to be the root cause.

 Regarding the data filtration, it is intended for this report to retrieve long amount of data for printing and auditing purpose. Several situations we face customer requirements to generate such large reports.

 

Thanks

[Hesham Desouky]

Hi Katia,

 I tried the httpruntime executionTimeout with 600 seconds (10 minutes) and the same problem occurst.

Any idea?

[Katia]

Hello Hesham,

You are right, that ConnectionTimeout is used for establishing the initial connection. However, by design, it is also used for committing and rolling back transactions. Therefore, the recommended troubleshooting in such cases is to control both CommandTimeout and ConnectionTimeout properties.

If testing extending the timeouts does not solve the problem, please open a support ticket and send us a backup of the database and a demo project with the report. This way we can reproduce the problem locally and advise you further.

Regards,
Katia
Telerik