Could not find RDL file C:\AOSService\PackagesLocalDirectory\xxx

(3) Share

Report

Posted on by Shooowtek

845

Hello everyone,

I'm encountering a frustrating issue with a custom SSRS report in D365 F&O and would appreciate any insights.

The Scenario:
We have a custom SSRS report that works perfectly on our local DEV environment. However, after deploying it to our UAT (Tier-2) environment via a Deployable Package in LCS, running the report results in the following error:

Could not find RDL file C:\AOSService\PackagesLocalDirectory\XXX\Reports\XXX.Report.rdl

What I've Already Checked:

Package Integrity: I have unpacked the deployable package (.zip file) and I can confirm that the RDL file is present in the correct path: AOSService\Packages\XXX\Reports\. This seems to rule out a build issue on the DEV environment.
Build Process: The package was created after a full model rebuild. The build completed with 0 errors,
DEV Environment: As mentioned, the report runs flawlessly on the DEV machine after right-clicking and selecting "Deploy" in Visual Studio.

My Question:

Given that the RDL file is definitely included in the package that was successfully deployed, what could be preventing the UAT environment from finding it?
Is this likely an issue with the SSRS cache on the UAT environment that requires a service restart?
Has anyone experienced a scenario where the LCS deployment process completes successfully but fails to correctly deploy or register specific SSRS reports?
What would be the recommended next steps? Is raising a support ticket with Microsoft to restart the SSRS service the only way forward in this situation?

Thanks in advance for any suggestions

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (1)

Aditya Pal 198 on at

Like (0)

Report
Copy link

Link copied!

ChatGPT said:

This issue usually occurs because, while the RDL file is present in the package, it may not have been properly deployed to the SSRS server in your UAT environment. On DEV, the report works since you deploy it directly from Visual Studio, but in UAT the deployment via LCS sometimes doesn’t push the RDL correctly, leaving the system unable to locate it. The most common fix is to manually redeploy reports on the UAT server using the axupdateinstall.exe deployreports command from the PackagesLocalDirectory\Bin folder, and then restart the SSRS and batch services to refresh the cache. It’s also important to verify that the report is registered in the SRSReportServerItems table in AXDB to ensure the system knows about it. In most cases, a manual redeployment followed by a service restart resolves the “Could not find RDL file” error, and you won’t need to raise a Microsoft support ticket unless the problem persists even after these steps.

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,538 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi Shooowtek,

A few questions:

1. Are the reports deployed to the Tier-2 environment through a deployable package created through ADO Build pipeline or release pipeline?

2. Is the reporting file present under Metadata\<modelname>\<modelname>\AxReport\<reportname>.xml in Azure DevOps, if the deployments are managed through Azure DevOps?

A few suggestions:

1. In the Tier-2 environment, you also have a mechanism to check for DP classes through table SRSReportPreProcessedDetails.

2. In your Tier-2 environment, check the table called dbo.SRSReportQuery. This table should have the .Report file entry in the database. If the entry isn't present then the report isn't present nor deployed in the Tier-2 environment.

3. In the Tier-2 environment, run the class called https://<Tier-2environmenturl>/?cmp=<cmpName>&mi=SysClassRunner&cls=SysFlushReportServer and https://<Tier-2environmenturl>/?cmp=<cmpName>&mi=SysClassRunner&cls=SysFlushAOD.

Hope this helps. Happy to answer questions, if any.

Was this reply helpful? Yes No
Verified answer

Sagar121 1,160 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi,

Please try to re-deploy the package.

This happens with many customers where report don't get deployed properly at first go while redeploying same package helped.

1 people found this reply helpful.

Was this reply helpful? Yes No