In case you see this one:
Physical to Virtual Conversion with Hyper-V VMM 2008 R2,
Succeeded in P2V conversions of the same server a number of times already, but now I repeatedly get the following error at x% of the conversion:
The operation did not complete successfully because of a parameter or call sequence that is not valid.
(The parameter is incorrect (0x80070057))
I tried a reboot of VMM, but this did not help.
Based on this description here are the best steps to address this issue:
P2V Hyper-V VMM 2008 R2
Are you using a template from vmm to perform this action?
Might be a P2V migration test failed at step (Deploy file using LAN) with error message?
The operation did not complete successfully because of a parameter or a call sequence that is not valid. (The parameter is incorrect (0x80070057))
Do you see audit failures in the security log (unknown user or password for the computer account of the VMM server)?
Is the VMM server running with local system account?
screenshot of the error on the vmm console?
Can you please Repro and collect traces on the VMM server?
Are you doing the P2V with multiple disks or only one?
We can try to select only one Disk for testing purposes,
Are we deploying the new VM in the same Hyper-v Server?
HostAgentInvalidArg 2901 0x80070057
Do you have any Multipath software installed with "Storage Manager for SANs" feature running on the Physical server?
Do you have Nic Teaming?
Can you run the VMMCA (Virtual Machine Manager Configuration Analyzer) on both the VMM server and in this case, the P2V Source computer?
SCVMM Comprehensive Updates June 2010
Description of the System Center Virtual Machine Manager 2008 R2 hotfix rollup package: June 8, 2010
Description of the System Center Virtual Machine Manager 2008 R2 Admin Console hotfix rollup package: June 8, 2010
Have you already installed and run the VMMCA available from this link:
The VMMCA It only checks to see it that optional integration component is configured and provides a “Warning” if it is not found.
Can you check the Hyper-V host and make sure it does not have any mounted VHDs already for this VM?
Apply also those on the Physical Server:
For more information about WinRM 2.0, click the following article number to view the article in the Microsoft Knowledge Base:
968929 Description of the Windows Management Framework on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008
2:An update package for Background Intelligent Transfer Service (BITS) is nowavailable for Windows Server 2003 and for Windows XPhttp://support.microsoft.com/kb/923845/en-us
Can you try the following:
1. Uninstall the p2v agent from the source machine.2. Go to Regedit->HKLM\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings on the VMM server3. Create a new DWORD reg entry named “P2VBITSTcpPort” and give it a decimal value between 16000-32000 . Say 30443 decimal..4. Go to system services (services.msc) and restart Virtual Machine Manager service Then try to p2v the machine again.
Try the P2V with only a disk, for example c:\
If that works,
So we can try some additional actions:
on that server
msconfig and disable all 3 party stuff,
Or we can also try this tool to convert just the d: driver to a vhd file
The only thing I am seeing is that this specific server or disk has something different running that is affecting the P2V.
That is why as a best practice if we found issues, disabling all the 3 party services/applications should help.
Hope this helps