In the on-premises version of D365 Finance and Operations 10.0.45, deployment fails with an error.

(3) Share

Report

Posted on by RL-24021803-0

Hello,

We are doing a fresh installation (not an upgrade) of D365 Finance and Operations on-premises 10.0.45 and the deployment fails with the following errors during the Deployment.Setup.exe step on the AOS node.

Error 1: Infolog diagnostic message: 'Query extended range failure: Invalid class name 'WorkflowApprovalHistoryEntity'..' on category 'Error'.
Error 2: Infolog diagnostic message: 'Query extended range failure: Invalid class name 'VRMPersonEntity'..' on category 'Error'.

Both errors come from Microsoft.Dynamics.AX.Deployment.Setup.exe and are logged in Windows Application Event Log (Level: Error, EventID: 0).

This is a new installation from — not an upgrade from a previous version

We tried deploying version 10.0.44 — same error
There are no customizations — standard deployment with no custom models, extensions, or ISV solutions
The AXDB is restored from empty backup
Both entity views (WorkflowApprovalHistoryEntity, VRMPersonEntity) exist in AXDB and are valid SQL views with no broken references
Service Fabric shows no errors, but LCS reports Failed status
AxService reported Warning for DeploymentServicingOperationReport

Environment:

SQL Server: 2022 with CU12
SSRS: 2022 (16.0.1118.33)
Windows Server: 2022
SSMS: 18.12.1

If anyone has encountered and solved this problem, please share your solution — it would be very helpful. We have been stuck on this for several deployment attempts and any guidance is appreciated.

Categories:

Dynamics 365 Finance

Microsoft Dynamics AX

I have the same question (0)

All responses (8)

Answers (2)

Sort by

André Arnaud de Cal... 306,230 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

I don't have experience myself deploying on-premises environments. In case this is a fresh installation without customizations I suggest to contact Microsoft Support.

Was this reply helpful? Yes No
Verified answer

KM-16030905-0 Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Hello Everyone,

I'm the Technical Lead from Microsoft Support team who assisted Roman in this issue.

Please note that the F&O environment deployment was failing due to other reasons including an old version of Local Agent, an issue with SSRS redeployment, and star certificate.

Please note that (Query extended range failure: Invalid class name 'WorkflowApprovalHistoryEntity' | 'VRMPersonEntity') are misleading errors and you should check the logs properly for the actual reason of deployment failure.

If the environment is deployed already, please ignore those errors unless they are impacting other functionalities.

Thanks

Was this reply helpful? Yes No
Verified answer

RL-24021803-0 15 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi everyone,
I’d like to share a few details from my case in case they help others in a similar situation.

1. I was running the latest Local Agent version available in LCS at the time (3.4.0). I also saw that the entity errors (WorkflowApprovalHistoryEntity, VRMPersonEntity) had appeared in forum posts about a year ago.

2. The main issue was that SSRS was not coming up due to cryptography errors. I noticed a mismatch in the Microsoft.Identity.Client.dll version and used the TSG script described here: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/onprem-tsg-implementations#SSRSIdentityClient After that, SSRS deployed successfully, but the module installation step in LCS still did not complete.

3. Kareem suggested using the newest Local Agent, which wasn’t available to me at the time, and sent me the installer file. I installed it and continued to use the TSG script as well. From the outside the situation looked the same: SSRS was installed and running, but the installation step in the agent still did not complete.

4. Following Kareem’s advice, I checked the reports deployment log: Task Manager → Details → right‑click AXService.exe → Open file location → go up one folder and open the log folder → find the report deployment log: AXDeployReports-YYYY-MM-DD_HH_MM_SS. There I found that reports failed to deploy with: Publish-AXReport fails with ArgumentNullException: The value supplied for parameter 'serviceName' cannot be null or empty. Stack trace: Reporting.psm1 around line 446 (Publish-AXReport) and AXDeployReports.ps1 line 21

5. Resolution
Kareem then suggested running Complete-PreReqs.ps1 on the SSRS nodes again. After doing that, the reports deployed successfully, SSRS is working, and the entity errors have not reappeared.

Was this reply helpful? Yes No
André Arnaud de Cal... 306,230 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for providing the resolution, Kareem and Roman. This will be helpful in case others have a similar question.

Was this reply helpful? Yes No
MG-18032239-0 6 on at

Like
a
(0)

Report
Copy link

Link copied!

tengo este error, pero en entornos BUILD al instalr la versión 10.0.47, alguna sugerencia? de dónde saco el script Complete-PreReqs.ps1?

Was this reply helpful? Yes No
MG-18032239-0 6 on at

Like
a
(0)

Report
Copy link

Link copied!

También tengo este error en una máquina BUILD y regenerar las máquinas es muchísimo tiempo

Was this reply helpful? Yes No
André Arnaud de Cal... 306,230 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @MG-18032239-0

As this is an English lingual forum, please translate your replies into the English language.

Was this reply helpful? Yes No
MG-18032239-0 6 on at

Like
a
(0)

Report
Copy link

Link copied!

Ya lo corregí

1. Primero es entrar a la máquina y actualizar todas las versiones de VS con el visual installer

2. reiniciar

3. rotar certificados

Con eso queda listo y desaparece este error

Was this reply helpful? Yes No