250 Hello

Random Musings on Exchange and Virtualization

Hyper-V Did Not Find Virtual Machines to Import - Error 32784

Hyper-V Did Not Find Virtual Machines to Import - Error 32784

  • Comments 7
  • Likes

When importing a VM into Windows Server 2012 that was exported from Windows 2012 R2 you will be unable to import the VM.  If you import the VM using PowerShell’s Import-VM cmdlet the error message is not very descriptive – “The operation cannot be performed because the object is not in a valid state”.  You will also find EventID 15040 in the VMMS event log. 

The operation cannot be performed because the object is not in a valid state

The full error message for reference:

Import-VM '.\Virtual Machines\F5164EF0-5F87-40F1-9872-C669406A18A5.XML'

Import-VM : Failed to import a virtual machine.

The operation cannot be performed because the object is not in a valid state.

At line:1 char:1

+ Import-VM '.\Virtual Machines\F5164EF0-5F87-40F1-9872-C669406A18A5.XML'

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidOperation: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [Import-VM], Virtualizatio

nOperationFailedException

+ FullyQualifiedErrorId : InvalidObjectState,Microsoft.HyperV.PowerShell.Commands.ImportVMCommand

 

If you look in the Microsoft-Windows-Hyper-V-VMMS/Admin event log, EventID 15040 should be present, stating that “Failed to import a virtual machine”. 

EventID 15040 Failed to import a virtual machine

Not much to go on and troubleshoot there…

Let’s retry this using the GUI…..

If you used the Hyper-V Manager to import the same VM it provides a clue:

Importing 2012 R2 Into 2012 Using Hyper-V Manager

Importing 2012 R2 Into 2012 Using Hyper-V Manager

 

Hyper-V Did Not Find Virtual Machines To Import From Location Error 32784

Now that we have an error code, we can plug that into our favourite search engine.  Which should lead you to the following KB article:

KB 2868279 Moving a virtual machine (VM) from a Windows Server 2012 R2 Hyper-V host to a Windows Server 2012 Hyper-V host is not a supported scenario under any circumstances.


I wanted to publish this quick post so folks who gravitate to importing via PowerShell can search and easily find the cause of the issue since it is the GUI that provides the clue.

Cheers,

Rhoderick

 

Can You Help Us?  -- Yes !

If you would like to have Microsoft Premier Field Engineering (PFE) visit your company and assist with the topic(s) presented in this blog post, then please contact your Microsoft Premier Technical Account Manager (TAM) for more information on scheduling and our varied offerings!

If you are not currently benefiting from Microsoft Premier support and you’d like more information about Premier, please email the appropriate contact below, and tell them you how you got introduced!

US

Canada

For all other areas please use the US contact point.





Comments
  • Thank you.

  • thanks for sharing.

  • thanks for sharing.

  • Thanks for sharing Rhoderick. Have a nice day.

  • perhaps not direct import export, but we can:
    1. Remove the integration services from the VM,
    2. Build a new VM on 2012 host using the same VHD(x) disks
    but I cannot imagine why would anyone want to downgrade from 2012 R2 to 2012..

  • Exactly Sam, and that's what's in here http://blogs.technet.com/b/rmilne/archive/2014/09/03/importing-server-2012-r2-hyper-v-vm-into-server-2012.aspx

    In terms of wanting this, its kinda clear cut on the import/export side. However this also applies to live migration too - so if someone moved the VM over to test out a net new 2012 R2 box then it cannot move back to 2012.

    I do agree - In general it is normally upwards and onwards when it comes to such things.

    Cheers,
    Rhoderick

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Post Comment Fixer