This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(92.8, 44%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
Unable to start replication of vms. It Stucks at installing mobiliy service and enabling replication with Error ID327185, Error ID 327173 and ID 539
![](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(16, 97%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Hello Equal
Thank you for posting your query on Microsoft Q&A platform.
Enable replication fails and Mobility Service push install gets stuck with:
Error ID 327185 – Site Recovery configuration failed
Error ID 327173 – Mobility Service installation failed
Error ID 539 – Replication Provider action failed
The source VM doesn’t have the required trusted root certificates for ASR authentication, so configuration fails.
Fix (Windows & Linux):
Cause: ASR push install can’t copy/install the agent because File & Printer Sharing, WMI, or admin credentials are not correctly configured.
Fix: Enable File & Printer Sharing, Enable WMI for Domain/Private/Public profiles and allow through firewall, Use Local Administrator credentials for push install
If push install continues to fail, perform manual Mobility Service installation and retry enable‑replication.
3)Error 539 : This is a generic Replication Provider failure that occurs because the configuration/push‑install steps above did not complete successfully.
First fix Errors 327185/327173 and retry.
If still failing, on the replication appliance:
Upgrade/Restart Microsoft Azure RCM Proxy Agent and RCM Proxy Management Service, then wait ~1 hour and retry enable‑replication.
Thanks,
Suchitra.
Hello Equal
Could you please let us know if the solution shared in the comment addressed your query. If you have any other questions or need further support, please feel free to contact us.
Thanks,
Suchitra.
Suchitra,
Thank you for your help.
We are using admin domain credentials for this process. Regarding the root certificates, the systems are updated through Windows Update, and I understand that during that process the certificates are also updated. As for the other error, with the ASR push installation, I see that it installs on the source machines, but something fails and the process does not complete.
At this point I need to reach the logs that could tell us what is really going on. This is very frustrating, and at this point we´re considering AWS as our DSR solution.
![](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(249.60000000000002, 44%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
You need to check below first;
How will I check replication if it doen´t even start? No replication progress, nothing.
can you take screenshot and share
Salamat Shah can you help me?
An update. Tried to manual install, this is what I get: