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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

Upgrade to version 18 failed on step 53

(0) ShareShare
ReportReport
Posted on by 8

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!!

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    303,397 Super User 2026 Season 1 on at

    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.

  • zhifeng Profile Picture
    Microsoft Employee on at

    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

    Use the logs

    If package application fails, and you want to use the logs, follow these steps.

    1. Download and then unzip the log files.

    2. Select the role that a step failed for, such as AOS or BI.

    3. Select the virtual machine (VM) where the step failed. You can find this information in the Machine name column in the Environment updates section.

    4. 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).

  • AstridMalanka Profile Picture
    8 on at

    I know what step it failed, it is step 53

  • AstridMalanka Profile Picture
    8 on at

    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

  • AstridMalanka Profile Picture
    8 on at

    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.

  • Community Member Profile Picture
    on at

    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

  • Community Member Profile Picture
    on at

    Hi Astrid, how did you solve this issue? I'm having the same error now trying to update to version 18

  • AstridMalanka Profile Picture
    8 on at

    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.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

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

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 521 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 438

#3
Adis Profile Picture

Adis 261 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans