Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

1 Answer 10 Views
.NET Core DataSource SQL Report Designer (standalone)
Ron
Top achievements
Rank 1
Iron
Iron
Iron
Ron asked on 05 May 2025, 07:05 PM
Good afternoon.

I'm hitting a new roadblock that I've never hit before with the standalone report viewer.

The crux of the problem - I have many reports with lengthy WITH () statements, none of them have caused issues to date. That said I have a particular data source with this as the second term of the query:

), L01 AS (
    -- L0 without writeoffs
    SELECT * FROM L0 WHERE [WriteoffTF] = 0

That works fine, if I run it alone in SSMS it runs in 7515 ms

I need to make a change based on an output mismatch the client noticed, it's a very simple change - only removing the WHERE clause:

), L01 AS (
    -- L0 without writeoffs
    SELECT * FROM L0 

This query runs alone in SSMS in 8219 ms


In Telerik Standalone Report Viewer the first version works fine but the moment I remove the WITH statement I get this:

Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.


Where I'm stuck:

1) The connection string is in a .Net Core / Angular project (pulling from the .Net Core side) so there's no web.config until the app is published. The connection string being used is from my appsettings.json file.
2) Adding time to my connection string, like 'Connect Timeout=600', this unfortunately has no impact.

I also tried opening up the .trdp as a .zip and looking at the definition.xml but I couldn't find any reference to time and if I need to add something there I don't have any examples as to what the syntax should be.

I just went to File > Help to see which version of the standalone report viewer I'm using, it's
14.0.20.115.

Please let me know if you have any ideas on how I can resolve this as well as whether you need any additional information.


1 Answer, 1 is accepted

Sort by
0
Accepted
Ron
Top achievements
Rank 1
Iron
Iron
Iron
answered on 06 May 2025, 04:52 PM
It looks like in this case there's some kind of SQL glitch where slightly different WHERE conditions on the same query (or even the same result set requested differently) also have the same effect on a stored procedure containing it. 

I'll cancel this question since it can be recreated elsewhere without Telerik Reporting being involved.
Tags
.NET Core DataSource SQL Report Designer (standalone)
Asked by
Ron
Top achievements
Rank 1
Iron
Iron
Iron
Answers by
Ron
Top achievements
Rank 1
Iron
Iron
Iron
Share this question
or