Since I was going to have to troubleshoot the problem anyway, I decided to write about it. I was working on something unrelated and needed to add a Hyper-V host to Virtual Machine Manager. The error message that I showed you in the very first figure in this article is real. However, there is a method to the madness. Admittedly this advice is so clichéd that it sounds almost laughable.
#Setup code on time server 2912 windows
Clock skew can cause a variety of problems for Windows Server and Virtual Machine Manager.Īnother thing that I would recommend doing is pausing for a few minutes, or possibly even rebooting the Virtual Machine Manager server and the Hyper-V host. First, compare the clock on your Virtual Machine Manager server against the clock on the Hyper-V host that you are having trouble with. Three recommendationsīefore you delve too far into the troubleshooting process, there are a few things that I recommend doing. Therefore, this is the area in which we would need to focus our troubleshooting efforts. If we take a closer look at the Jobs window, we can see that the Details pane reveals that the problem occurred while adding the virtual switch extensions to the Hyper-V host. The Installed On date confirms that this is a new instance of the agent and that the agent isn’t left over from another time. In fact, a quick peek at the Hyper-V host’s control panel reveals the presence of the agent that was installed. Step 1.2 involved installing an agent onto the Hyper-V host. If you examine the Details tab, however, you can see the actual steps that were performed in an effort to add the Hyper-V host to VMM. The error message shown in the screen capture above seems to imply that HTTP connectivity cannot be established between the Virtual Machine Manager server and the Hyper-V host that is being added. Unless you take the time to really understand what is going on, you can waste a lot of time chasing the wrong problem. Over time, however, I have learned that VMM error messages can be misleading. Furthermore, the error description specifically tells you that a file transfer has failed and that you should check to make sure that the HTTP service is running and that no firewall rules are blocking HTTP traffic. After all, the error number (2940) is a file-transfer error code. On the surface, this particular problem would seem to be relatively straightforward.
As you can see, this window displays the error message, an error code, and a brief description of the error. When VMM fails to add a Hyper-V host, the Jobs window will typically display a message similar to the one that is shown in the image below. That being the case, I wanted to take the time to walk you through some possible causes. Every once in a while, however, things do, not work the way they should, and the process of adding the host fails.
Adding a Hyper-V host to System Center Virtual Machine Manager should be a simple matter.
0 kommentar(er)
