Symptoms
Article Summary:This article provides information on an issue in which virtual machines in a Windows Server 2012 Hyper-V cluster are able to quick migrate but not live migrate.Issue You may find that you are unable to live migrate virtual machines in a Windows Server 2012 Hyper-V cluster but are still able to quick migrate them. Attempting to live migrate results in the following error in the cluster node's event log (which will also show up in the Events section of Failover Cluster Manager):------------------------------ Event ID 21502 Live migration of 'Test' failed. Virtual machine migration operation for 'Test' failed at migration source 'nodexxx'. (Virtual machine ID ED1AB74B-A4E5-4F18-8ECB-92D0F058EF85) The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host 'nodexxx': The logon attempt failed (0x8009030C). The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source host: The logon attempt failed (0x8009030C).------------------------------ No other errors are generated. Solution 1. Make sure the cluster networks are configured properly.2. Verify that the Hyper-virtual networks/virtual switches have consistent names. These names are case-sensitive.3. Run a Cluster Validation Report, excluding the storage test.4. Verify that the cluster name has been properly registered within DNS. Follow the steps below in order to fix the issue if the configuration is correct and the Validation Report does not report any issues: 1. Run ipconfig /registerdns on all nodes.2. Give the cluster name object (CNO) full control of the cluster name's host record in DNS.3. Run ipconfig /flushdns on all nodes and check the properties of the cluster name. 4. Take the cluster name offline and perform the Repair action. 5. Check the results.
