Hyper-v Cluster Server 2022 - Network outage - cluster node cannot start hyper-v service?

Erik Tank 1 Reputation point

We have a 2022 hyper-v cluster with 3 nodes. 1 of the nodes seems to have an issue. When loading hyper-v manager and connecting to the local computer, it errors out:

An error occurred while attempting to connect to server "servername", Check that the Virtual Machine Management service is running and that you are authorized to connect to the server. Hyper-v encountered an error trying to access an object on computer "servername" because the object was not found. the object might have been deleted. verify that the virtual machine management service on the computer is running.

The service is not running - when I try to start the service, I get an error that there isn't enough memory. available. Event logs say that the cluster components are not able to start due to memory. The system says it's using 19 out of 448GB of memory... so there's plenty of memory, plenty of storage.

Anyone seen this before or know how to correct it? I've done dism, and sfc - many reboots. ALWAYS hangs on the reboots for 30 minutes or so trying to shut down the cluster services. So I've evicted it from our cluster as it was screwing up everything else to (delays galore, etc.)

I've tried to uninstall and reinstall hyper-v and cluster failover management services - and still get this blasted error just trying to connect to hyper-v manager.

A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,521 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
953 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Xu Gu (Shanghai Wicresoft Co,.Ltd.) 501 Reputation points Microsoft Vendor

    Hi ErikTank,

    Based on your description, I made the following analysis:
    (1) First of all, we want to make sure that Hyper-V Manager is running as an administrator.
    (2) Second, we look at Hyper-V related services in "Services" to see if there is a service "Hyper-V Virtual Machine Management", and if so, start the service and set the "Startup type" to "Automatic".
    (3) If you do not have the service, you need to install the service manually, but because you have already configured the cluster, this situation may not exist.
    (4) We also need to ensure that a dedicated network interface is created for the virtual switch to ensure the reliability of the network.
    (5) For the memory error you said, I think the following link may help you:
    Note: The second link has some similar errors to your issue:

    Hope my answer helps you!

    Best Regards,
    Xu GU

    0 comments No comments

  2. Erik Tank 1 Reputation point

    1) yes as domain admin
    2) is set to automatic - but as I stated, it fails to start due to out of memory (not storage)
    3) I already tried to uninstall and reinstall hyper-v which cannot be done without fully evicting and destroying the cluster components as well - done and problem persisted after reinstalling cluster and hyper-v roles.
    4) there WAS a SET created prior to everything going SNAFU called vSwitch which is no longer present in the system and all SET commands in powershell fail saying hyper-v isn't installed, when it is.
    5) Those are storage errors, not MEMORY errors and were not related. I found those before creating this post as well.

    I nuked it from orbit and reinstalled everything from scratch and it's working fine again.

    0 comments No comments