Hello,
We had some challenges with updating our cloud hosted DEV environment via LCS and as we were on tight schedule, we updated environment with Power shell script. So, now environment is updated to 10.0.10 version successfully but still LCS shows older version i.e.10.0.8. When trying to update via LCS, we receive the same error.
This is a known issue with the Azure subscription. The best way forward is to delete the environment and redeploy. That should be easy as this is a cloud hosted environment. The version mismatch issue is separate and fixing that will not fix this issue. The best and simplest way forward is to redeploy the VM.
Regards,
Dip
Thanks Dip for your response. That's what even MS is suggesting.
Hi ShamikaK,
What version do you see from D365 FO application from. if it shows you 10.0.10 then no need to update it again from LCS.
About the Remote Management error - please try to rotate secrets (Dynamics Deployment Certificate) from LCS.
About the mismatch in the version that's shown in LCS vs your actual version: I recommend deploying a new system. But it might also be fixed by installing the update again from LCS.
It's a known limitation. The data in LCS does not get updated when anything is installed manually from command line. Whether you install an ISV package or install a monthly update. Only when you deploy from LCS will it gather and update all the data.
So next time you install an update or package from LCS, the correct will be reflected.
Yes, I can understand that suggestion coming from Microsoft support because the VM is currently in a bad state. To resolve the version mismatch (LCS showing wrong application version) issue, you need to deploy the next package through LCS and that will update the information in the LCS to match the actual application version of the environment. But to resolve the error: 95112, you can try to rotate secret of your SSL certificate though I highly doubt that can resolve it (you can let me know if you try). Redeployment is my suggestion, specially because this is a customer owned cloud hosted environment and should be rather simple to set up a new one.
If this answers your question fully, please mark it for the same so that anyone facing the same issue after you and referring to this forum is helped.
Best Regards,
Thank you all for your response. Rotate certificate option is also tried but no luck. As version is wrong on LCS page, I wanted to make sure we can peform future updates correctly, directly via LCS. I believe, only option is to uninstall and install again.
In general it's good to treat the dev systems as disposable. If you encounter issues, just deploy a new one since it's much faster (and therefore cheaper) than using hours or even days investigating problems.
I had the 95112 error today, when trying to update one of our dev machines to QU 20.
This was caused by some misconfiguration on the azure load-balancer the dev-environment is related to.
To prevent the vm from being visible with it's public address, I removed the mapping from the "vm-winrm-vm-xx" inbound NAT rule.
I was still able to connect from company network and run the application itself, but it turned out that this port-mapping must be available for LCS deployment.
After I enabled the mapping again, the deployment from LCS was successful.
Regards
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
CA Neeraj Kumar 2,188
André Arnaud de Cal... 868 Super User 2025 Season 2
Sohaib Cheema 593 User Group Leader
