web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Deployment Issues with Unified Package to New Power Platform Finance and Operation Environment

(6) ShareShare
ReportReport
Posted on by 272

Hi everyone,

We are encountering two separate issues while deploying unified packages to the a new Power Platform environment, and I would appreciate your insights on resolving them.

As you kwno this will be the new mode to deploy packages when LCS is deprecating.

Current Problems:

  1. WaitingForResources Issue:
    The deployment process initiated from Azure DevOps gets stuck in the WaitingForResources state with the log showing:

    • "Starting apply package"
  2. Unexpected Environment State Failure:
    In previous attempts, the deployment failed entirely, indicating an unexpected environment state.


Technical Details:

Context:

  • Tooling: Managing environments via Power Platform Admin Center (not LCS).
  • Setup: Followed Microsoft documentation to configure pipelines, releases, Azure application, and connections. Successfully enabled the app on the Sandbox environment.

Problem 1: WaitingForResources State

  • The deployment process remains in the WaitingForResources state indefinitely.
  • Log message excerpt

Problem 2: Unexpected Environment State Failure

In previous deployments, the process go on, but failed with the following error logs:

2024-11-18T20:49:31.8733214Z [
2024-11-18T20:49:31.8734843Z   'Upload Finance and Operations Module RUB_1_0_0_1_managed.zip - Applying Application Module - Failed; Error Message: "Microsoft.Dynamics.CAP.Iris.NanoServices.EnvironmentStatusCheckerException: Environment has reached an unexpected state Failed\\r\\n\\r\\n\\r\\n   at Microsoft.Dynamics.CAP.Iris.NanoServices.EnvironmentInstanceStatusChecker.HasTargetStatusReached(String pollingLocation, HashSet`1 expectedStates, HashSet`1 unExpectedStates, CancellationToken cancellationToken) in C:\\\\__w\\\\1\\\\s\\\\src\\\\Iris.Infrastructure\\\\Services\\\\StatusPoller\\\\EnvironmentInstanceStatusChecker.cs:line 81\\r\\n   at Microsoft.Dynamics.CAP.Iris.Jobs.LifecycleJobs.DeployFinOpsCustomPackageJob.RunPollAsync(DeployFinOpsCustomPackageMetadata deployFinOpsPackageMetadata) in C:\\\\__w\\\\1\\\\s\\\\src\\\\Iris.Infrastructure\\\\Jobs\\\\Lifecycle\\\\JobCallbacks\\\\DeployFinOpsPackage\\\\DeployFinOpsCustomPackageJob.cs:line 113\\r\\n   at Microsoft.Dynamics.CAP.Iris.Jobs.Platform.LongRunningWithPollingJob`1.RunAsync() in C:\\\\__w\\\\1\\\\s\\\\src\\\\Iris.Infrastructure\\\\Jobs\\\\Platform\\\\LongRunningWithPollingJob.cs:line 60\\r\\n   at Microsoft.Dynamics.CAP.Iris.Jobs.Platform.WhatIfModeSupportedJob`1.ExecuteAsync() in C:\\\\__w\\\\1\\\\s\\\\src\\\\Iris.Infrastructure\\\\Jobs\\\\Platform\\\\WhatIfModeSupportedJob.cs:line 68"'
2024-11-18T20:49:31.8737197Z ]
2024-11-18T20:49:36.8739793Z [
2024-11-18T20:49:36.8740504Z   'Upload Finance and Operations Module RUB_1_0_0_1_managed.zip - Failed - Complete'
2024-11-18T20:49:36.8740867Z ]
2024-11-18T20:49:36.9008444Z [ 'Installation failed for Finance and Operations application' ]
2024-11-18T20:49:36.9032988Z [ 'Beginning queueing up UpdateRibbonClientMetadata job.' ]
2024-11-18T20:49:37.0586906Z [
2024-11-18T20:49:37.0587564Z   'Successfully queued up UpdateRibbonClientMetadata request. - Complete'
2024-11-18T20:49:37.0588105Z ]
2024-11-18T20:49:37.5005640Z [ 'Microsoft PowerPlatform CLI' ]
2024-11-18T20:49:37.5034843Z [ 'Version: 1.35.1+g0c2637a' ]
2024-11-18T20:49:37.5035480Z [ 'Online documentation: https://aka.ms/PowerPlatformCLI' ]
2024-11-18T20:49:37.5035956Z [
2024-11-18T20:49:37.5036415Z   'Feedback, Suggestions, Issues: https://github.com/microsoft/powerplatform-build-tools/discussions'
2024-11-18T20:49:37.5036848Z ]
2024-11-18T20:49:37.5037185Z [ '' ]
2024-11-18T20:49:37.5037658Z [ 'Error: Installation failed for Finance and Operations application' ]
2024-11-18T20:49:37.5038105Z [ '' ]
2024-11-18T20:49:37.7925433Z ##[error]error: 1
2024-11-18T20:49:37.8187451Z ##[error]failed: Connected as ***
Reading the import configuration. Please wait.
Import configuration loaded. - Complete
Reading the solutions. Please wait.
Reading the solutions. Please wait.


Any one has the same error?

We already open a Microsoft Ticket for supporting us and a yammer post on the PAAP program group https://www.yammer.com/dynamicsaxfeedbackprograms/threads/2918619781013504

Thank you in advance for your support!

Best regards,
Diego

I have the same question (13)
  • Umar Usman Profile Picture
    19 on at
    @Diego Mancassola Were you able to resolve it?

    My Context:
    1. Build pipeline on ADO -> Creates a unified deployable package
    2. Release pipeline on ADO -> Uses the artifact from build pipeline and try to deploy it on UDE Developer sandbox environment.
    3. Release pipeline fails with the following Error message:
    "Upload Finance and Operations Module tcllabel_1_0_0_1_managed.zip - Applying Application Module - InProgress; Failure happened while running DBSync on environment mli-d365-ax1."


     @Martin Dráb @André Arnaud de Calavon Guys, I need help your help on this issue?!
  • Martin Dráb Profile Picture
    237,965 Most Valuable Professional on at
    You keep talking about pipelines. Does it mean that others ways of deployment works for you, or that you didn't try a direct deployment at all and now you don't know whether your problem is about deployment in general or specific to your pipeline? 
  • Umar Usman Profile Picture
    19 on at
    @Martin Dráb I recently moved from LCS to UDE envs. So, I was following MS recommended CICD practice which is to create unified deployable package from build pipeline (done) and deploy that package using release pipeline (not working). Now, I'm not sure if this issue is specifically related to my release pipeline or not, gut says it isn't.
  • Umar Usman Profile Picture
    19 on at

    @Martin Dráb 

    My pipeline setup:


    Pipeline Failure:

    The pipeline fails specifically at the Power Platform Deploy Package step with the following error:

     

    Microsoft.Dynamics.CAP.Iris.Connectors.Exceptions.DSSidecarOperationException: DS/Sidecar operation: dbsync failed with the error code FailedDependency; error message: Failure happened while running DBSync on environment [environment name]…

    However, when I manually deploy the same model package and run a full database synchronization directly from Visual Studio (Extensions → Dynamics 365 → Deploy → Synchronize Database) on the same UDE environment, everything works successfully without any errors.

     

    I’ve attached screenshots showing:

    • The manual deployment of models to the online environment

    • Successful database synchronization (Completed DB Sync with syncKind: Full)


     

    Despite that, the automated release pipeline fails on the DBSync step within the Power Platform Deploy Package task.

    Is there any specific configuration or permission required for the pipeline service connection to perform DBSync on UDE environments?

    Or is there an additional step needed before executing the “Power Platform Deploy Package” task?
  • Martin Dráb Profile Picture
    237,965 Most Valuable Professional on at
  • Suggested answer
    Umar Usman Profile Picture
    19 on at
    @Martin Dráb I figured it out.
     
    In order to view detailed db sync logs of the failed deployment from release pipeline, you have to follow these steps mentioned in the MS UDE FnO FAQs:

    https://learn.microsoft.com/en-us/power-platform/developer/unified-experience/finance-operations-faq#how-can-i-find-the-history-of-packages-applied-db-sync-and-other-updates-to-my-environment

    In my case, the actual error in the db sync log was:
     
    Serialization version mismatch detect, make sure the runtime dlls are in sync with the deployed metadata. Version of file '210'. Version of dll '209'.

    So, now I knew the actual problem I have to solve instead of a generic db sync error. I hope this helps!
  • BM-05111959-0 Profile Picture
    7 on at
    @Diego Mancassola I am experiencing the same issue you posted. I am not having the DBSync issue that everyone else is incorrectly trying to solve. I have a ticket open with MS since Sep. 17th with no resolution. 
     
    I was able to pinpoint that this issue only occurs on PPAC environments AFTER I copied a LCS Tier 2 to replace the data. Other PPAC environments that have not been copied from the LCS Tier 2 do not have this deployment issue.
     
    Have you found a resolution?
  • Suggested answer
    BM-05111959-0 Profile Picture
    7 on at
    @Diego Mancassola I have found a workaround. By opening the Power App "Finance and Operations Package Manager" and then removing all Modules and all history from the Package area, I am able to deploy successfully. I provided this information to MS on my open support case. Hopefully, this will help them find a permanent fix.
  • Suggested answer
    MS-23111319-0 Profile Picture
    3 on at
    @BM-05111959-0, this workaround also worked for me. I had the same issue described in the original post and deleting all Modules and all Packages solved did the trick.
     
     

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.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 503 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 434 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 278 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans