Comments on: Advanced Troubleshooting of Hyper-V Replica – Part 1

By: Symon Perriman

Symon Perriman — Thu, 05 Mar 2020 06:57:00 +0000

In reply to Subhash.

Hi Subhash,
There are a few reasons why you could be seeing this… most likely your replication certificate has expired and needs to be renewed. Sometimes this could be due to a network change which causes the network to become misconfigured, so check your DNS routing. If you can afford some downtime, try rebooting the server, this has been reported to help some other with the same error.

Thanks,
Symon Perriman
Altaro Editor

By: Subhash

Subhash — Wed, 05 Feb 2020 14:27:00 +0000

Hi,

It would be helpful if you have explained about the workgroup configuration and configuring selfsigned certificates for it.

I’m currently stuck at Hyper-V failed to enable replication for virtual machine ‘test’: The connection with the server was terminated abnormally (0x00002EFE). (Virtual machine ID 16D3D782-92E2-4944-9E3E-B3237568B427)

By: Nirmal

Nirmal — Sat, 23 Nov 2013 13:22:00 +0000

Thanks for commenting Helmut!

Yes, time difference might cause authentication issue as well! I will have it added as a bullet point in the article!

Thanks!
Nirmal

By: Helmut Hauser

Helmut Hauser — Wed, 13 Nov 2013 18:02:00 +0000

Just brilliant Nirmal.

In addition I do recommend the “swiss army knive” WireShark, and if you are in troubleshooting mode, you might check all NTP settings.
Just a little clock screw can have a rather bad impact.

1 on pointing towards the certificates.
Have a quick look to Azure.
Some breakdowns have been caused by – guess what – Cert issues.

Cheers,

Helmut