Announcements
No record found.
Hi,
My update failed from version 17 to 18 on step 53.
Any idea what that means? The log error doesn't say much
thanks!!
Hi Astrid,
Have you downloaded the log files and searched for the error details? If you need help in understanding please provide some more details from the downloaded log.
Hello AstridMalanka,
Please refer below article to download deployment/runbook and get detailed exception on step 53, then we can advise next action plan. Or you can raise a ticket with MS so that we can help.
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/deployable-package-troubleshooting
If package application fails, and you want to use the logs, follow these steps.
Download and then unzip the log files.
Select the role that a step failed for, such as AOS or BI.
Select the virtual machine (VM) where the step failed. You can find this information in the Machine name column in the Environment updates section.
In the VM logs, select the folder that corresponds to the step where the issue occurred. The folder name identifies the step that each folder corresponds to.
For example, if the issue occurred during the execution of a step, select the ExecuteRunbook folder. The step number is highlighted and is the number after the globally unique identifier (GUID).
I know what step it failed, it is step 53
On the DownloadSlipstreamPackagesWorkItem the error notepad is empty.
On the preservicing on the error it says: "The specified module 'C:\Program Files\Microsoft Security Client\MpProvider' was not loaded because no valid module file was found in any module directory."
On the RunbookExecution folder when I look at step 53 is the update retail channel, i had a error before there, i will try to do what i did then with the retail server
it was the same issue as before with the retailed server, i dropped it and then i was able to continue the install.
thanks to everyone.
Hey Astrid, were you able to solved this issue? do you mind to share what did you do? I'm having the same problem now
Hi Astrid, how did you solve this issue? I'm having the same error now trying to update to version 18
Yes, I was able to resolve it, by using the sql to drop the retail server. Here is the steps on how to do it. community.dynamics.com/.../1127950
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.
Congratulations to our 2026 Super Stars!
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
André Arnaud de Cal... 521 Super User 2026 Season 1
Giorgio Bonacorsi 438
Adis 261 Super User 2026 Season 1
