📎 AI Summary:
The thread is about troubleshooting a Hyper‑V Replica setup where enabling replication fails with “Enabling Replication Failed” for a specific VM (error code 0x80048016) even though a Hyper‑V Replica Broker has been configured on both sites and replication has been allowed. The key guidance is that this error is often caused by a mismatch in the VM configuration version—typically when the primary is on a newer Windows/Hyper‑V level than the replica host/cluster—along with checks for required permissions (notably the “Log on as a service” right) and verification via Hyper‑V event logs to confirm the actual root cause. Overall, the sentiment is constructive and troubleshooting-focused, with the responder asking for environment details to pinpoint the fix.
The thread is about troubleshooting a Hyper‑V Replica setup where enabling replication fails with “Enabling Replication Failed” for a specific VM (error code 0x80048016) even though a Hyper‑V Replica Broker has been configured on both sites and replication has been allowed. The key guidance is that this error is often caused by a mismatch in the VM configuration version—typically when the primary is on a newer Windows/Hyper‑V level than the replica host/cluster—along with checks for required permissions (notably the “Log on as a service” right) and verification via Hyper‑V event logs to confirm the actual root cause. Overall, the sentiment is constructive and troubleshooting-focused, with the responder asking for environment details to pinpoint the fix.
Solution
Hi ejdgr8,
That specific failure code in your screenshot (%%2147778582 / 0x80048016) most commonly shows up when the VM “configuration version” on the Primary is newer than what the Replica host/cluster supports—e.g., replicating Server 2022 → Server 2019/2016, or 2019 → 2016. In that case, Hyper‑V Replica can fail at the final “Finish” step with this generic error. (learn.microsoft.com)
Then confirm the Replica hosts support that version (rule of thumb: Replica must be same or newer than Primary for VM config versions).
Typical fixes:
That specific failure code in your screenshot (%%2147778582 / 0x80048016) most commonly shows up when the VM “configuration version” on the Primary is newer than what the Replica host/cluster supports—e.g., replicating Server 2022 → Server 2019/2016, or 2019 → 2016. In that case, Hyper‑V Replica can fail at the final “Finish” step with this generic error. (learn.microsoft.com)
1) Check VM configuration version (most likely cause)
On the Primary Hyper‑V host, run:Get-VM "test-replication-vm" | Select-Object Name, VersionThen confirm the Replica hosts support that version (rule of thumb: Replica must be same or newer than Primary for VM config versions).
If versions are mismatched
You generally cannot downgrade a VM configuration version.Typical fixes:
- Upgrade the DR/Replica hosts/cluster to the same (or newer) Windows Server/Hyper‑V level as Prod.
- Or recreate the VM in a version the Replica supports (often: create it on the older host/cluster first, then move it to the newer one without upgrading the VM version), then enable replication. (learn.microsoft.com)
2) Also verify this “Log on as a service” right (quick win)
Make sure the following principal has the user right Log on as a service on the Hyper‑V hosts (via Local Security Policy or GPO):NT VIRTUAL MACHINE\Virtual Machines
3) Grab the real reason from Event Viewer (to confirm)
On both Primary and Replica nodes check:- Event Viewer → Applications and Services Logs → Microsoft → Windows → Hyper‑V‑VMMS → Admin
- (Also check Hyper‑V‑Worker)
A few details that will let me pinpoint it fast
- What Windows Server versions are Prod hosts and DR hosts/cluster? (2016/2019/2022?)
- Are you using Kerberos (HTTP/80) or Certificate (HTTPS/443) replication?
- When enabling replication, are you entering the Hyper‑V Replica Broker FQDN (not an individual node)?
Reply with those + the VM “Version” fromGet-VM, and I’ll tell you exactly what to change.
