Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.

Environment

Product Version	12.2.18.1017
Product	Progress® Telerik® Reporting

Description

The error message "Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding." is returned from the attempt to connect to the SQL server database.

Error Message

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.

Solution

The common troubleshooting approach for connectivity issues (timeout issue) is extending the connections timeouts in SqlDataSource component. You can try the following suggestions:

1. Test using a larger value for the CommandTimeout property;

2. Test using a larger value in the connection string as well;

3. Extend the execution timeout in the web.config file with even bigger value than you've set initially, for example:

<httpRuntime executionTimeout="7200" />

In case the report retrieves a large amount of data, you might consider filtering the data on the retrieval. We suggest to review the information in Filtering Data and Performance Considerations help articles and see what can be applied to the current project.

Notes

If this does not help, in order to proceed we would need the following information:

• Use Fiddler to follow the exact requests to/responses from the REST Service. The entire error Stack Trace should be available in the corresponding response when previewed with Fiddler. Save the generated traffic as SAZ file.
• Attach a Trace Listener to the REST Service project (add the corresponding section to the project web.config file) to obtain information on where and why the error occurs.

After you generate the log files from the above steps, archive them and attach them to a support ticket. Include the steps which have to be followed in order to reproduce the issue.