Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
825 questions
Azure Site Recovery error - Attempt to install mobility service failed with MSI error 1603
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 21%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGA%3C/text%3E%3C/svg%3E)
Ghulam Abbas
211
Reputation points
Hi, we are trying to setup asr for one of our recently migrated (from on-prem HyperV) VM between 2 regions in Azure and getting an error:
- Error ID: 151242
- Error Message: Attempt to install mobility service failed with MSI error 1603.
- Possible causes: MSI failed with exit code 1603 and MSI error -- Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
We have looked into the url suggested and dozens of other online MS docs etc but cant seem to get it working. It looks like the Windows installer service gets stopped when the SiteRecovery extension gets started to install the mobility service. We have tried to start it manually a few times but every time when the site recovery setup begins, we have noticed it gets stopped again. Well, if we try to install some other extensions from Azure, like diagnostic etc, its gets completed with success. Also, we have a few other migrated VMs replication setup without any issue.
Can we please get any suggestion what to do to get to the bottom of this issue?
Many thanks
Azure Site Recovery
{count} votes
-
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator2023-06-16T17:05:52.44+00:00 @Ghulam Abbas Sorry for the inconvenience this must have caused you!
Did you try the suggestions posted in this link - https://social.msdn.microsoft.com/Forums/en-US/10cd0bd3-56a4-4575-aed3-ee2e910c17d9/installing-asrunifiedagent-on-configuration-server-failed-error-1603?forum=hypervrecovmgr
-
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator
2023-06-19T06:25:57.31+00:00 @Ghulam Abbas Have you had a chance to see the previous response? If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.
-
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator
2023-06-20T11:30:04.96+00:00 @Ghulam Abbas We haven't heard back from you. In case you already found a solution, would you please share it here with the community? Otherwise, let us know and we will continue to engage with you on the issue.
-
Ghulam Abbas 211 Reputation points
2023-09-28T14:12:37.55+00:00 Hi @SadiqhAhmed-MSFT , apologies for not being intouch previously. We have tried the steps mentioned in the link provided but no joy and still getting the same error:
MSI failed with exit code 1603 and MSI error -- Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
-
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator
2023-09-29T14:58:10.2533333+00:00 @Ghulam Abbas Here are some steps you can take to troubleshoot this issue:
Check the installation logs: The installation logs can be found in the following location: C:\ProgramData\ASRSetupLogs. Look for any errors or warnings in the logs that might indicate the cause of the problem.
- Check the prerequisites: Make sure that the source machine meets all the prerequisites for installing the Mobility service. You can find the prerequisites in the following article: https://docs.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview#prerequisites
- Check the firewall settings: Make sure that the required ports are open on the source machine's firewall. You can find the required ports in the following article: https://docs.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview#ports
- Check the antivirus software: Antivirus software can sometimes interfere with the installation of the Mobility service. Try disabling the antivirus software temporarily and then attempt the installation again.
- Try a manual installation: If the push installation is not working, you can try a manual installation of the Mobility service. You can find the instructions for a manual installation in the following article: https://docs.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-installation#install-the-mobility-agent-using-command-prompt-classic
If none of these steps resolve the issue, you may need to contact Microsoft Azure technical support team for further assistance.
-
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator
2023-10-03T14:27:14.9933333+00:00 @Ghulam Abbas Just checking in to see if you got a chance to see my response and if it helped, I would request you to "Accept Answer and Upvote" so that the relevancy of this post will improve when anyone in the community search for a similar query.
-
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator
2023-10-04T14:51:49.4433333+00:00 @Ghulam Abbas We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.
Sign in to comment
Sign in to answer