<div>
Here is the solution from technet<br />
<a href="http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/5b731f1a-f495-4d88-a875-0eea77ecd6b4" rel="ugc nofollow">http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/5b731f1a-f495-4d88-a875-0eea77ecd6b4</a><br />

</div>


<div>
I saw that, however I'm getting the error when trying to export. &nbsp;The .EXP file that needs editing is never created. &nbsp;None of the folder structure for exporting the VM is created. &nbsp;Removing the GUID appears to be done as part of the importing process.<br />
<br />
<a href="http://www.virtualizationadmin.com/articles-tutorials/general-virtualization-articles/cloning-hyper-v-virtual-machines-right-way-part4.html" rel="ugc">http://www.virtualizationadmin.com/articles-tutorials/general-virtualization-articles/cloning-hyper-v-virtual-machines-right-way-part4.html</a>
</div>


<div>
Is it possible that you will export to another location just as a test ?<br />
cause maybe it's related to the machine you try to export to can be a lot of things like writing permissions or bad disk<br />
<br />
and if you can give the scenario what machine you export to where?<br />
<br />
Thanks,<br />
<br />

</div>


<div>
I'm trying to export to an external drive. &nbsp;I have successfully exported to that drive in a test environment. &nbsp;I might be able to find another location, although the export will be about 70GB. &nbsp;Unfortuately, I won't be able to export to the same box.
</div>


<div>
So the test environment was another location?<br />
if so you should check the destination cause it's sounds like the problem is there.<br />
<br />
waiting for updates. &nbsp;<br />

</div>


<div>
I guess I'm not understanding your question. &nbsp;The test environment VM was exported to the same external drive, no issue. &nbsp;When trying to export to the external drive in production, I'm getting the error.<br />
<br />
In production, I'm trying to export a DC to an external drive to bring up in a test environment.<br />
<br />
I can attempt to export to another location.
</div>


<div>
This link describe troubleshoot for this error please take a look<br />
<br />
<a href="http://www.petri.co.il/fixing-hyper-v-export-errors.htm" rel="ugc">http://www.petri.co.il/fixing-hyper-v-export-errors.htm</a>
</div>


<div>
The space in the file name, good catch msmamji. &nbsp;That was it. &nbsp;I didn't even consider that. &nbsp;Thank you both for your help!
</div>


<div>
<div class="content wysiwyg-content">
When trying to export a VM in Hyper-V, I am receiving the following error:<br />
<br />
Failed to copy file from 'E:\Hyper-V\Virtual Hard Disks\machine.vhd' to 'I:\VM Export\machine\Virtual Hard Disks\machine.vhd': One or more arguments are invalid (0x80070057)<br />
<br />
I'm trying to setup a test environment to test another implementation. &nbsp;The machine I'm trying to export is a DC. &nbsp;I've read this is not best<br />
practice, but this was suggested to me by one of our consultants. &nbsp;I understand not to ever put this VM into production and am assuming<br />
this is why MS states this is not recommended.<br />
<br />
Any suggestions would be greatly appreciated.
</div>
</div>


When trying to export a VM in Hyper-V, I am receiving the following error:

Failed to copy file from 'E:\Hyper-V\Virtual Hard Disks\machine.vhd' to 'I:\VM Export\machine\Virtual Hard Disks\machine.vhd': One or more arguments are invalid (0x80070057)

I'm trying to setup a test environment to test another implementation.  The machine I'm trying to export is a DC.  I've read this is not best
practice, but this was suggested to me by one of our consultants.  I understand not to ever put this VM into production and am assuming
this is why MS states this is not recommended.

Any suggestions would be greatly appreciated.

Hyper-V Export Error

Microsoft Virtual Server was a virtualization solution that facilitated the creation of virtual machines on the Windows XP, Windows Vista and Windows Server 2003 operating systems. Virtual machines are created and managed through a web-based interface that relies on Internet Information Services (IIS) or through a Windows client application tool called VMRCplus. Features included Linux guest operating system support, Virtual Disk Precompactor, symmetric multiprocessing (SMP), x64 host operating system support, the ability to mount virtual hard drives on the host machine and additional operating systems support, including Windows Vista, and a volume shadow copy writer.