Finance | Project Operations, Human Resources, ...

update failed at step20 Update script for service model: AOSService on machine:

(1) Share

Report

Posted on by Community member

I upgraded the environment of a virtual machine on LCS from 10.0.34 to 10.0.38, but when I reached Update script for service model: AOSService on machine step 20, I failed. How can I solve this problem

I have the same question (0)

All responses (6)

Answers (0)

Martin Dráb 239,040 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

A good idea is checking why it failed, because how you can choose a solution if you don't know the problem? You can download the logs from LCS.

You can also try running it once more in the meantime, in case it was just a temporary problem.

(Moved from Dynamics 365 general forum.)

Was this reply helpful? Yes No
Hana Xue Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi,
The documentation mentions that you may have a database sync issue if you see the following steps failing: "GlobalUpdate script for service model: AOSService".
Troubleshoot package application issues - Finance & Operations | Dynamics 365 | Microsoft Learn
Best Regards,
Hana

Was this reply helpful? Yes No
Griet 31 on at

Like (0)

Report
Copy link

Link copied!

I also struggle with the update to version 10.0.38 on one virtual machine (we are upgrading from 10.0.37).

When I dig in the logs I can find something about a timeout value:

[13:34:33.5565] Exception[196609] found.
[13:34:33.5565] There are one or more failed step during the runbook execution, please check the runbook xml and log for more detail
[13:34:33.5565]
[13:34:33.5565] The step 20 failed with the following error:
[13:34:33.5565] The step execution time exceed the timeout value specified: 75min

I had the same issue on the same environment with the previous update. After several retries the update then succeeded. This time I have no luck (yet).

Is this issue familiar to anyone? Are there things I can try to fix this issue?

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Anthony Blake 3,092 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

If the environment is Cloud Hosted (Tier 1 in Azure) 10.0.34 to 10.0.38, it could well be the requirement for the new VC++ runtime requirement from 10.0.36 onwards:

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/get-started/whats-new-platform-updates-vcruntime#update-cloud-hosted-environments-to-the-latest-vc-runtime

Was this reply helpful? Yes No
RAGU Veelead 6 on at

Like (0)

Report
Copy link

Link copied!
please follow these steps:

Navigate to the Service Drive (for cloud deployments, this is typically K:\).

Open the Deployable Packages folder and locate the package that failed. You can identify it by sorting the files by date and time.

Within the package, locate the DevToolsService scripts folder. Look for the PowerShell script named AutoUpdateDevToolsService.

Run this script manually. After completion, resume the update process from LCS.

Was this reply helpful? Yes No
Anthony Blake 3,092 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @RAGU Veelead, this is from over a year ago, at this point, I would suggest just redeploy the environment, end of service for 10.0.38 was August 2024.

Anthony

Was this reply helpful? Yes No