Finance | Project Operations, Human Resources, ...

LCS shows wrong version of Tier-1 VM after local update

(2) Share

Report

Posted on by Jan M.

3,317

Because of failed steps while updating Tier-1 v44 to v47 from LCS, the steps where locally finished. The app runs well on v47 now.

Now package v47 deployment is not possible from LCS, as there is still v44 displayed. Tried some steps according AI:

- set runbook steps to complete and run it

- restart lcs service

- restart vm

- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dynamics\Deployment should have a value for version but its not there...

How do LCS sync version info with VM?

Thanks for your help.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (8)

Answers (0)

Sort by

Suggested answer

Giorgio Bonacorsi 3,299 on at

Like (1)

Report
Copy link

Link copied!

Hello,

You can try to open from the VM environement in LCS to trigger manualy the update.

If you prefer you can even set an update cadance: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/configure-service-updates

Let's us know if it work, and we stay available for any question.

Thank you,

Giorgio

Was this reply helpful? Yes No
Jan M. 3,317 on at

Like (0)

Report
Copy link

Link copied!

Hello,

The quality update was saved this way and executed thru LCS, but it failed, so steps was executed locally with rerunstep on the same runbook.

LCS did not change the version, but the application is on the new version. My question remains, how the sync works between LCS and cloud hosted VM?

Was this reply helpful? Yes No
André Arnaud de Cal... 305,194 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Jan,

If you know that the version is on .47, then having the information reflected on LCS is not that important. It is not changing the behavior of the application. I had the update completed several times via local VM interactions. The version information will be updated in case a successful update was installed via LCS. You can try to rerun the .47 update, or wait until a next version update.

Was this reply helpful? Yes No
Jan M. 3,317 on at

Like (0)

Report
Copy link

Link copied!

Hi André

Agree, in general for a Dev VM it doesn't matter. In this case the VM is connected to a release pipeline where a v47 build now failed. The reason why former update failed was not clear, on Step 19 (copy files) there where blockings to .err files leaded in a timeout. And the reason why we are not just deploying a new VM is the huge db size, what always takes a lot of time.

May only a rerun of last step 61 would do the trick?

Thanks.

Was this reply helpful? Yes No
Sagar121 1,187 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Sure, it will not sync. But you can try to put same package again.

Was this reply helpful? Yes No
André Arnaud de Cal... 305,194 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Jan,

You mentioned that the steps were locally finished. I do assume it did complete step 61 already?

Was this reply helpful? Yes No
CU29051515-0 2 on at

Like (0)

Report
Copy link

Link copied!

Did you ever figure this out?

I have exactly the same problem.

I've found that LCS updates nearly always fail multiple times before succeeding.

Like you, I gave up on the 10.0.47 update.

I tried going direct to 10.0.48 too but that also failed.

Eventually I manually updated to 10.0.48 and now LCS is stuck on Failed status.

As far as I can tell this means I'm now doomed to manual-only updates from now on?

The update was fine, it's running, but next I have a Build VM to update and am truly dreading the experience.

How the heck can LCS be "fixed" or "synced" from the environment?

Was this reply helpful? Yes No
Jan M. 3,317 on at

Like (0)

Report
Copy link

Link copied!

Unfortunately not.

I tried to set all tasks in runbook to complete except 63, but it doesn't the trick.

Around step 17 when LCS stopped on error, setting the step complete and resumed LCS did work. But later on step where AOS update (20?) was involved, it restarted always on the same.

Was tired to test it from scratch as it needs such a long time. Had to deploy a new vm...

Was this reply helpful? Yes No