How to fix broken Development VM after failed Update?

(0) Share

Report

Posted on by Community Member

Hello,

my D365-FO development VM has version 10.0.12 (10.0.507.20028)

and I tried to apply it Service Update 10.0.13 (10.0.569.20009) via LCS but it failed and I had to Abort.

Now the system seems not fully operational.

So, I can still login using RDP, but the application website is broken,

the browser (not application) prompts me to login then displays error 404 at the main page.

Is there any Dev environment update failure rollback strategy available to apply?

And what I should do to try manually fix the environment?

I have the same question (0)

All responses (7)

Answers (2)

Sort by

Gunjan Bhattachayya 35,423 on at

Like (0)

Report
Copy link

Link copied!

Hi Yiannis,

Please check this thread. It lists a few steps you could try for restoring your environment.

Did you check what was the error during service update?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Gunjan,

Unfortunately not, but I think it was similar error as in the thread you proposed.

However, I do not see a DynamicsBackup folder in my Development VM I: drive.

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 304,116 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Yiannis,

If you update to 10.0.13, there is a pre-requisite to install .NET 4.7.2 before starting the service update. If you haven't done this, you can install it and try to update to 10.0.13 again.

See also: community.dynamics.com/.../action-required---net-version-and-visual-studio-2017

If you want to use VS2017, it would be recommended to redeploy a development environment with 10.0.13 pre-installed.

Was this reply helpful? Yes No
Gunjan Bhattachayya 35,423 on at

Like (0)

Report
Copy link

Link copied!

I think easiest option will be to deploy a new Dev environment.

But, if you really need this environment, can check the other drives as well for a backup folder?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks you Andre,

I am now installing .NET 4.7.2 then trying the update to 10.0.13 again.

I hope this will work, but I also doubt if updating the broken environment will do.

Gunjan,

not in other drives either.

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,166 Moderator on at

Like (0)

Report
Copy link

Link copied!

In general, when the update fails, you must read the logs to see what went wrong.

For this particular scenario (10.0.12 -10.0.13) it's most likely caused by wrong .NET framework version, as mentioned by others.

I recommend you to deploy a new box, this way you will also get VS2017.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report
Copy link

Link copied!

I have very good news from my broken environment front.

Installing .NET Framework 4.7.2 Runtime led the 10.0.13 update to success. My environment seems not broken anymore.

Thank you all,

esp. Andre & Nikolaos for correctly explaining the problem.

Was this reply helpful? Yes No