Event id 21502 failed to register. 'SRV-FS6' failed to start. Event ID 1196 Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name (s) for the following reason: The handle is invalid. Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server. I see I can right click on the resource and choose "delete. I can't bring the resource online at all. A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because connected host has failed to respond (0X8007274C) Nov 2, 2020 · On Windows Server 2019 Hyper-V Cluster VM failed to start after proper shutdown. Jan 21, 2015 · ID: 21502 'Hyper-V Replica Broker RBROKER' failed to register the service principal name: Insufficient access rights to perform the operation. I tried to migrate the server manually, but as you can see in the screenshot below it still failed: Event ID 21502 'Virtual Machine SRV-FS6' failed to start. These failing NICs were grouped together in weird ways, the manager seemed to randomly decide which NICs should talk to eachother. Event ID 1069 & 21502. " The help articles point to a configuration issue, but since most of the VMs did live migrate, I don't believe this is accurate. Looks like some config file got corrupted, can I just remove the config file? Tried rebooting one of the hosts in the cluster but that didnt do it. Action Oct 30, 2020 · Event ID: 21502 - 'Virtual Machine Configuration <>' failed to register the virtual machine with the virtual machine management service. Joined it to the existing cluster being limped along by Node B. Let it get fully patched, installed current HP Support Pack, installed hyper-v and failover cluster manager. VM failed to live migrate because a virtual switch used by the VM doesn't exist on the destination node "Host2". (0×80072746) Caused By Wrong Jumbo Frame Settings. Cluster interfact Local Area Connection 2 failed, etc. Feb 14, 2018 · HyperV VM Refuses to Power up Following a Power Loss in HyperV Cluter. Feb 12, 2026 · Event ID 21502 Information regarding Event ID 21502 Live migration failed because a virtual switch used by the VM doesn't exist on the destination node "Host2" Description Live migration of VM failed. and Event ID: 21502 'Virtual Machine Configuration [server]' failed to register the virtual machine with the virtual machine management service. " Nov 2, 2020 · On Windows Server 2019 Hyper-V Cluster VM failed to start after proper shutdown. Dec 17, 2013 · Event ID: 21502 The Virtual Machine Management Service failed to establish a connection for a Virtual machine migration with host XXXX. The Virtual Machine Management Service failed to register the configuration for the virtual machine '03059663-1988-4147-929F-4D543925C4EA' at '\\host-01\c$\ClusterStorage\Volume1\<<My Server>>': General access Sep 25, 2023 · I was patching a customers HyperV Clustered servers but found that one server failed to migrate to a different clustered node, when I tried to Drain the Roles. 1205, and 1254. Feb 12, 2026 · Live migration in Hyper-V allows virtual machines (VMs) to be moved between hosts with minimal downtime—a critical feature for high availability and maintenance in Windows Server environments. Feb 12, 2026 · Failed to create Planned Virtual Machine at migration destination: Logon failure: the user isn't granted the requested logon type at this computer. . Jan 12, 2022 · If the virtual machine starts or does not start, in both cases I get these errors: Event ID: 21502 'Virtual Machine Configuration ActiveDirectory' failed to register the virtual machine with the virtual machine management service. Properly diagnosing Oct 16, 2015 · So, I wiped and reinstalled 2012R2 on Node A. Forcibly moved VMs from Node B to Node A. ID: 1254 Clustered role 'RBROKER' has exceeded its failover threshold. Any help would be greatly appreciated. I am getting event IDs 21502, 1069. (0x80072098). We would like to show you a description here but the site won’t allow us. Most failed the first time but I was finally able to get them all over. Sep 13, 2023 · The thread discusses an issue where a user accidentally deleted a VHD file and restored it from a backup, leading to errors when attempting to start a V Dec 17, 2013 · Hyper-V MVP Didier Van Hoye (@WorkinghardinIT) has written a nice blog post on how to solve when you get failed Live Migrations with Event ID 21502 Planned virtual machine creation failed for virtual machine ‘VM Name’: An existing connection was forcibly closed by the remote host. A few VMs didn't live migrate, and I get the error 21502, "Failed migration at destination host. (0x80070569) Additionally, when you do a recovery checkpoint and try to convert it to a reference point by using the ConvertToReferencePoint method, the conversion might fail. Despite its capabilities, live migration can fail due to a wide array of factors—hardware incompatibility, authentication, network configuration, VM settings, and storage issues. eripzjx txbtk lfdw aycxrwut hptqy xsipx xfaqyvd gkctcs kzaxl bsfyim