Event 14050 after restoring VM Domain controller

JeffR 21 Reputation points
2021-11-19T15:11:21.913+00:00

Since restoring the VM, Event log on the Hyper-V host has Event 14050 Failed to register the service principal name 'Hyper-V Replica Service', Failed to register the service principal name 'Microsoft Virtual System Migration Service'. Failed to register the service principal name 'Hyper-V Replica Service' and similar messages – all Event ID 14050.
I checked the VM, AD Users and Computers, Advanced features, Selected the Hyper-V host, Attribute Editor tab, and checked servicePrincipalName had the value idap /<Host_Server_Name>.idap/#<numbers & text>.
On the Hyper-V host, I ran
setspn -S "Hyper-V Replica Service/HyperV" <VM_Server_Name>
setspn -S "Microsoft Virtual System Migration Service/HyperV" <VM_Server_Name>
setspn -S "Microsoft Virtual Console Service/HyperV" <VM_Server_Name>
setspn -S "Microsoft Virtual System Migration Service/HyperV.<FQDN>" <VM_Server_Name>

After running these I received the message Updated Object., but the host server is still generating the 14050 errors

I checked the AD ports and I believe they are the defaults:

netsh int ipv4 show dynamicportrange tcp

Start Port : 49152
Number of Ports : 16384
C:\Windows\system32>

Protocol udp Dynamic Port Range

Start Port : 49152
Number of Ports : 16384

As I believe the server is running on the default ports, I don’t think I need to run scripts for non default ports to overcome the 14050 errors. But the 14050 errors are still generating.
All suggestions welcome as I'm not sure what else I need to try. The objective is to eliminate the repetitive 14050 errors on the hyper-v host.

Thanks,

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,460 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Dave Patrick 426K Reputation points MVP
    2021-11-19T16:04:34.283+00:00

  2. JeffR 21 Reputation points
    2021-11-21T14:23:20.453+00:00

    Hi @Dave Patrick ,

    Removing and rejoining the domain didnt overcome this problem.

    0 comments No comments