Hello Juan David Ruiz Lopez,
The error you're encountering typically indicates a discrepancy between the Azure portal's reported state and what the Azure Site Recovery (ASR) backend expects
To address this firstly navigate to your VM in the Azure portal and verify the replication health and agent status as shown below.
And go to the Extensions + applications blade of the VM and check the status of all extensions.
- If any extension is in a Failed state, ensure its Provisioning State is set to Succeeded before proceeding.
If all extensions are in a healthy state and replication health is good, you may need to perform a manual installation to try to revert this.
Please follow the below steps directly on the VM to manually update the Mobility Service:
- Log in to the VM**.**
- From the Azure portal, go to: Recovery Services Vault > Replicated Items > Your VM> Site Recovery Infrastructure and download the latest Mobility Service installer.
- Copy the installer to the VM and extract it with the following command:
MobilityServiceInstaller.exe /q /x:C:\MobilityTemp
- Navigate to the folder:
cd C:\MobilityTemp
- Execute a silent upgrade:
setup /i /q /x /v" /qn REBOOT=ReallySuppress /l*v C:\Temp\MobilityUpgrade.log"
- After installation, make sure the following services are running from the VM:
- InMage PushInstall
- InMage Scout Application Monitoring
- InMage Scout Service
No reboot is required for now, but you may optionally restart the services if needed. Once the upgrade is completed you can validate from the Azure portal that the Mobility Service version reflects the update.
Retry the "Update Mobility Service" job if it remains flagged in the portal.
Please proceed with these steps and let me know the outcome. I’ll be happy to assist further if needed.
Thanks.