Hyper-V Troubleshooting: Event IDs 14050 and 32068: Reverse Replication failed

Event Details

Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin 

1. Failed to register the service principal name 'Hyper-V Replica Service'.

Event ID: 14050

 2.Hyper-V failed to enable reverse replication for '<VMName>': The server name or address could not be resolved (0x00002EE7). (Virtual Machine ID <VMId>)

Event ID: 32068

Issue:

Hyper-V Replica uses wrong FQDN during Reverse replication and Planned failover configuration. 

Possible Causes

The VMMS service is hardened to only connect to remote Domain Controllers/hosts on specific ports. In scenarios, Domain Controllers in this network have had either their netlogon/lsass port statically set OR the ephemeral port range changed, they will bind their dynamic RPC endpoints to ports outside these ranges.

During the Hyper-V reverse replication, we fail because we are expecting an FQDN. The issue is that DNS suffix is not populated correctly.

Resolution

You should configure Hyper-V server to add the Domain Controller's RPC port range so that Hyper-V is able to freely communicate with them.

The resolution for this issue is documented in this KB:http://support.microsoft.com/kb/2761899/EN-US

Related articles

• http://blogs.technet.com/b/virtualization/archive/2013/04/08/hyper-v-replica-name-resolution-of-internationalized-server-domain-names.aspx
• http://technet.microsoft.com/en-us/library/cc755191(v=WS.10).aspx