Hello everyone,
I'm facing an issue with a custom SSRS report in D365 Finance & Operations.
When I run the report interactively (not in batch) with a small data set, it works fine and returns results within seconds.
When I run the same report in batch, it fails with the error: An error occurred when running report Design in batch. Contact your system administrator for more information. Additionally, I attempted to debug the batch job using batch.exe, but was unable to load symbols for the process. Despite several efforts, Visual Studio does not hit any breakpoints, making it difficult to trace the root cause inside the batch job.
An error occurred when running report Design in batch. Contact your system administrator for more information.
Hii Jonas, I discussed the issue with the admin — the debugging problem is happening because the environment is running on an older version. Due to this, batch jobs cannot be debugged, and there's also a mismatch between the Sandbox and DEV environments.
I’ve suggested either upgrading the version or redeploying the server, especially since the batch job for the report isn’t working in Production either.
Yes, that makes sense.
I also started leaning toward the idea that the environment itself might be broken, especially since even standard reports fail in batch and symbols don’t load at all in batch.exe. The same code and setup work perfectly on another project server, so it really does point to an environment-specific issue.
batch.exe
Redeploying the environment does sound like a clean and efficient solution at this point. I agree—spending time debugging a broken dev environment often ends up costing more than just setting up a fresh one.
Also, I’ve noticed that when the report runs in interactive mode, it completes within seconds, but in with more records, it often throws this error:
Exceeded 10 minutes timeout during report processing. Consider updating the report to pre-processing or reducing data using report filters. Error in UAT: For more information about this error navigate to the report server on the local server machine, or enable remote errors
Do you know if there’s a recommended way to fix or work around this? Would implementing pre-processing help avoid the timeout.
Thanks again!
Hi Jonas
Yes, I'm using a custom controller, contract, and DP class. The contract class is clean and only used to pass parameters—no dialogs or UI interactions involved.
Regarding the debugging issue: I’ve tried multiple times to debug the batch execution using breakpoints and attaching the debugger to w3wp.exe and batch.exe, but the symbols never get loaded. I even tried very simple batch classes with info() statements just to see if the debugger hits, but it doesn’t. This behavior only occurs on my current project server. I tried the same report (even a standard one) on a different project server, and it worked fine—batch ran successfully and symbols were loaded correctly.
w3wp.exe
info()
So, to clarify:
Only SSRS reports fail in batch on my current environment. Custom and standard batch jobs run successfully (NOT SSRS Report).
The standard and custom report works on a different project server. I got sames issue in standard as well as custom reports while running in batch job.
For small case the report work fine without batch job and more records it throw error: Exceeded 10 minutes timeout during report processing. Consider updating the report to pre-processing or reducing data using report filters. (Usually client run this Report using interactive mode)
Debugger never attaches to batch.exe on the problematic server—symbols don’t load even for a test batch job.
Let me know if you think this could be an environment/configuration issue or anything else I can try.
Thanks!
Hi Raj, Thank you for your response and suggestions.
Just to clarify a few points based on your feedback:
There are no dialog() methods or UI elements used in the report. We use a proper contract class to handle input parameters.
dialog()
Previously, the report used a Regular table, but I’ve updated it to use a TempDB table. Unfortunately, the issue persists even after this change. I tested the one standard report on a different project server, and it worked fine there. I also tried running a standard SSRS report in batch on my current server, and it fails similarly — but other batch jobs (non-SSRS) run without issues. So it seems the problem is isolated to SSRS reports when executed via batch on this specific environment.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Andrés Arias as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Sohaib Cheema 789 User Group Leader
André Arnaud de Cal... 607 Super User 2025 Season 2
Martin Dráb 497 Most Valuable Professional
