Hyper-V "Failed to register service principal name."

[zag]

I've joined a server to the domain and then installed Hyper-V role.

I now get this error in the event log

"Failed to register service principal name."
EventID: 14050
Source: Hyper-V-VMMS

Has anyone else encountered this? Is it even a problem?

[zag]

Installing the windows updates seemed to fix the problem.

[tiru321]

It may be late for this Thread. Recently i faced same issue, tried all the Google search options.. no luck.
When final installation of Hyper-V Role, the Gateway IP has been removed by default installation. So, i added back that IP and restarted the server. My server communication started.

[rseiler]

Funny, since I'm looking at the same issue today. Do you have one NIC or two? We have two, and the second one purposefully doesn't have a gateway (there's a warning when you try to enter one), so I wonder if that's the issue. If there's only one NIC, I can certainly see how that would be the problem--though you'd have more noticeable problems than this, I think.

[tiru321]

Answer1:
I have 4 NICs. In this case you have to set priority on Network Adapters windows. Open Network and Sharing Center, Left side click Change Adapter Settings, hope you will your two NICs, When you on that window, press ALT key once, you will get Menu bar, go to Advanced Menu and Select Advanced Settings, on Adapters Binding tab, below connections; select & move internal communication NIC to top & ok.\

Answer2:
When you have two NICs, we will not use two gateways directly from Network adapter settings. If you are use NIC1 for internal access & NIC2 for external or something else; use "Route ADD" command at command prompt and add gateway and assign NIC2 gateway through Graphical window, your problem will be solved.

If not solved your issue above, post me your senario details; hope i will have answer

[rseiler]

My thought in having two NICs was for RDS: NIC1 handles the RDS traffic, while NIC2 handles backchannel communication between the RDS server and our domain server (transferring files that people open, etc). I'm just trying to distribute the load a bit, and the traffic accumulation on each (light for NIC1, heavy for NIC2) bears that out.

There's only one subnet, so I don't think adding a route is appropriate, right? NIC1 has the gateway configured, NIC2 does not.

I looked at the bindings and see that right now the internal-only virtual network I setup for HyperV is first (it didn't even exist initially--I just added it today), NIC2 is second, and NIC1 is last.

Armed with that information, what do you suggest?

Thanks

[tiru321]

If your subnet is having same gateway for two NICs, remove gateway addresses from two nics and just add one command line "route add" to your gateway. this will resolve your issue. So, on graphical screen both the networks will not have gateways.
Later, on application you do which NIC is using for what.... hope this also will help

[rseiler]

It might very well have resolved it, but I was still unclear on the particulars. I found a workaround, however: set the Hyper-V Network Management Service on delayed automatic start (in the properties of the service). That allows enough time for the network to start before Hyper-V jumps in and tries to use it.