Finance | Project Operations, Human Resources, ...

SSRS Report Execution timeout issue (The wait operation timed out)

(1) Share

Report

Posted on by TH-10100715-0

Hi there,

I have a SSRS report and i have followed all best practices like

I have Extended My DP class with SrsReportDataProviderPreProcessTempDB.
My Report table Type is TempDB
I have created Controller Class and call my report through this class
I have Updated the properties of menu item , Object Type Class , Object controller class name
Set the User Connection on the temp table . For this write this code on the start of your processReport method

I am not getting any error on OneBox machine but i am getting timeout and different server errors on UAT and Production environments. We are using on prem Microsoft dynamics 365 Finance and Operation version 10.0.38 (10.0.1777.94).

I am getting following different errors.

1. The wait operation timed out

2. An existing connection was forcibly closed by the remote host

Image (1).jpeg

All responses (2)

Answers (0)

Jonas "Jones" Melgaard 1,920 on at

Like (0)

Report
SSRS Report Execution timeout issue (The wait operation timed out)

Hmm... If it’s using the pre-processing pattern, I have a hard time seeing how it can time out unless there are some really funky things going on in the RDL or if an SQL execution plan in TEST/PROD got screwed up.

My old AX checklist includes manually deleting the report from the SSRS manager and deploying it again. That’s what I’d try first.

I wonder if there’s an issue with the SSRS server itself.

Can you see any high CPU or memory loads on the server when the report is being generated?

Do you have issues with other reports?

Can you see anything in the SSRS logs? SSRS Logs Documentation

Is this the only report with issues?

You should be able to see how long it spends in the data provider in the logs.
Suggested answer

Waed Ayyad 6,360 Super User 2024 Season 2 on at

Like (0)

Report

SSRS Report Execution timeout issue (The wait operation timed out)

Hi,

Did you try to enhance the query of the code?

Suggestion: Instead of using insert try to use RecordInsertList and insertDatabase.

Thanks,
Waed Ayyad

If this helped, please mark it as "Verified" for others facing the same issue