I am using pipelines to deploy solution for dataverse model driven app.
Dev solution is version 42
Test solution is/was version 41
Prod solution is version 41
I am deploying from Dev to Test and it failed with the following error:
“ImportAsHolding failed with exception :Cannot start the requested operation [Import] because there is another [Uninstall] running at this moment. Use Solution History for more details. -- The solution installation or removal failed due to the installation or removal of another solution at the same time. Please try again later. “
If I try re-running the deployment it does not pass validation and I get the following error:
“Validation results
This solution has a pending upgrade. Please complete the upgrade before proceeding”
In the TEST environment there are now two solutions (Version 41 and version 42).
Solution version 41 – for which the “apply upgrade” tick is available. If I select “apply upgrade” I get the following error:
“Failed to upgrade solution. Cannot start another [Uninstall] because there is a previous [Uninstall] running at this moment. Use Solution History for more details. -- The solution installation or removal failed due to the installation or removal of another solution at the same time. Please try again later.”
Solution version 42 – If I try to delete I get the following error:
“Cannot start another [Uninstall] because there is a previous [Uninstall] running at this moment. Use Solution History for more details. -- The solution installation or removal failed due to the installation or removal of another solution at the same time. Please try again later.”
The pipeline to deploy from dev to test to prod has been working well up until now.
I am really stuck – any suggestions ?
@sharonsammy123 Glad you have managed to to resolve this now.
For future reference, and for anyone else reading, this usually happens when there is another solution import/export/delete/upgrade operation in progress in the environment at the same time. The platform blocks multiple instances of this operation from running in parallel (for very valid reasons). Such operations can also be triggered by Microsoft updates or by updates from third party solutions you might have installed in your environment, not just your own solutions.
You can verify any such in progress operations in the environment by opening it in the maker portal and navigating to Solutions and then Solution History
UPDATE - I managed to fix this by republishing the solution in dev and redoing the deployment from DEV to TEST. Solution has now deployed successfully in test (as version 43). ie it never successfully deployed version 42. I think the problem may have been on Microsoft end. Anyway all appears ok so i am happy 🙂
WarrenBelz
791
Most Valuable Professional
MS.Ragavendar
410
Super User 2025 Season 2
mmbr1606
275
Super User 2025 Season 2