There Was an Error During Move Operation… Migration Did Not Succeed. Could Not Start Mirror Operation For The VHD File. The User name or Password is Incorrect (”0x8007052E’) #HyperV

3 min read

Sometimes I just need my blog as Knowledgebase to find something in the future, so this is exactly one of this blog post.

When I was migrating a Virtual Machine from Host A to Host B using Shared-Nothing Live Migration, the migration operation failed with the following error:

PowerShell Error: S.NOTHING-LM01

Hyper-V Manager Error:


SCVMM Error:


The error is consistent between PowerShell, Hyper-V Manager and VMM Sad smile .

The environment is very simple, here is a quick overview:

Two Hyper-V standalone servers 2012 R2 joined to the same domain managed by SCVMM. Host A was in production for quite some time, however Host B is new virgin host just deployed and fully patched Winking smile

If we look at the migration settings for both nodes, we found the following:



As you see the only difference is the incoming live migration network subnets, Host A has two subnets however Host B has only one subnet, but sure enough this is not the case since the migration will take place only on the 25.0/24 subnet.

Let’s do the opposite side, we will create a demo VM on Host B and then migrate to Host A.

The fast test will be… of course with PowerShell Smile

PC C:/>New-VM DEMO-VM -MemoryStartupBytes 4096MB -Generation 2 -Path “D:\VirtualMachines” -NewVHDPath “D:\VirtualMachines\DEMO-VM\Virtual Hard Disks\DEMO-VM.vhdx” -NewVHDSizeBytes 100GB -Verbose
PC C:/>Set-VMProcessor DEMO-VM -CompatibilityForMigrationEnabled $true -verbose
PC C:/>Start-VM DEMO-VM -verbose
PC C:/>Move-VM DEMO-VM -DestinationHost SC-MGMT -IncludeStorage -DestinationStoragePath “D:\VMs\DEMO-VM” –Verbose


The VM moved successfully Disappointed smile

What are the symptoms that we observed so far:

  • Shared-Nothing Live Migration from Host A to Host B Failed!
  • Shared-Nothing Live Migration from Host B to Host A Succeeded!

Let’s try to move back the DEMO-VM from Host A to Host B…


That error is, unfortunately, a misleading error. There is nothing wrong with the username or the password, I have full admin privilege on both Hyper-V nodes. The real problem that I have two different Management NICs with two different DNS servers set on each Surprised smile . The target host server must be resolvable by DNS, for this reason HOST B was able to resolve HOST A but not vice versa. The solution was simple, remove the second DNS server, flush and register the DNS on host A, and then finally flush the Address Resolution Protocol (ARP) cache!

ipconfig /flushdns
ipconfig /registerdns
command arp -d *

And here you go… I was able to move back the DEMO-VM from Host A to Host B!


Lessons Learned: Only one Management NIC must be set with DNS and Gateway, and the other network traffic such as (Live Migration, Storage, Cluster, iSCSI, Backup, etc…) must be set with only IP address, because failing to resolve the target host server via DNS will cause the migration to fail.

Hope this helps!

Until then… N’joy your day!


About Charbel Nemnom 579 Articles
Charbel Nemnom is a Cloud Architect, Swiss Certified ICT Security Expert, Microsoft Most Valuable Professional (MVP), and Microsoft Certified Trainer (MCT), totally fan of the latest's IT platform solutions, accomplished hands-on technical professional with over 17 years of broad IT Infrastructure experience serving on and guiding technical teams to optimize the performance of mission-critical enterprise systems. Excellent communicator is adept at identifying business needs and bridging the gap between functional groups and technology to foster targeted and innovative IT project development. Well respected by peers through demonstrating passion for technology and performance improvement. Extensive practical knowledge of complex systems builds, network design, business continuity, and cloud security.

Be the first to comment

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.