SCVMM 2012 SP1 - V2V conversion problem - error 2901

I'm desperately trying to convert vSphere 5.1 VMs to Windows Server 2012 Hyper-V VMs, and I'm constantly getting  the following error:
The operation did not complete successfully because of a parameter or call sequence that is not valid.

(The parameter is incorrect (0x80070057))

Open in new window

I've succeeded to convert few VMs, and the common thing for all of them is that they are "small", (small hdd, low memory allocation, such as DC on Windows Server 2012 Core, and some Windows Server 2012 with GUI machines). But for "larger" VMs I'm constantly getting mentioned error.

My question is: Is there any way for me to know what actually went wrong with the conversion, so that I can change this in my source VM and try again? How can I get more descriptive info than "The parameter is incorrect"?

Who is Participating?
fd4uAuthor Commented:
Yeah, again I've found the solution myself. I'm faster then experts :)
I've worked around this in somewhat strange way. First, I've concluded that it happens with "large" vmdk files. Conversion of VMs with wmdk files up to 60 GB has went well, but for larger files I was constantly getting error 2901 (0x80070057). So I've invented following (successful) procedure:
If ESXi VM's disks are set to Thick provisioned change that by cloning the VM and setting Thin provisioning on Storage page (the third page) of the Clone Virtual Machine wizard. The original VM stays intact. This way vmdk file size will be significantly reduced of course.

Manually copy all cloned VM's files to SCVMM Library. The default location is \\servername\MSSCVMMLibrary, so that all files should be located in \\servername\MSSCVMMLibrary\vmname. This way all the files will be on the local machine before conversion, so any network delay will be avoided.
Refresh the library by right-clicking library server and selecting Refresh option.
Convert VM from the library instead of original from ESXi host.
Nice thing with this procedure is that this can be done without even connecting SCVMM to vCenter nor ESXi hosts!

Fat Dragon
fd4uAuthor Commented:
I've marked this solution as Good instead of Excellent because the solution is actually work around. One can find better solution so that conversion of large files can be possible also. But one thing is for sure: THERE'S NO MORE ERROR 2901! :)
I had this problem and spent days trying to fix it.  I even paid for MS support, and they were no help.  It turns out the problem has to do with how SCVMM was connecting to the ESX hosts.  I had used a domain account to connect to both vCenter and the ESX hosts, but that was the problem.  To solve it, connect to vCenter with the domain account, but use a local esx account to connect to each host (I used root).  I was able to see an error in the vCenter logs that noted the rejected connection.  I also enabled a secure connection and accepted the certificates in SCVMM, but I don't know if that was part of the solution.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.