StarWind Software

Just downloaded the latest version today and tried to perform a cmd line conversion of a powered off VM on VMware ESXi 6.7 to local disk as a VHD. The GUI to the same VM works fine however cmd line does not. I keep getting this error.

???ERROR: VMwareFile::InternalParseFile: CreateFile is fail - 3. The system cannot find the path specified.
???ERROR: VMwareFile::InternalParseFile: Error open file - [local_dc22] wp-w2019-az01/wp-w2019-az01.vmdk
???ERROR: RunConsole: Error create input image - 2

I've tried specifying the "in_file_name" in several different ways all no success.

Here is what I am running:
V2V_ConverterConsole.exe convert in-host_type=esx in_host_address="10.72.71.31" in_host_port="443" in_host_username="root" in_host_password="Password" in_file_name="[local_dc22] wp-w2019-az01/wp-w2019-az01.vmdk" out_host_type=local out_host_address=localhost out_vm_name="wp-w2019-az01" out_file_name="A:\WP-W2019-AZ01\wp-w2019-az01.vhd" out_file_type="ft_vhd_thick"

Anyone have any luck with the cmd line?

See attached logs

Hi,

Please double-check the paths. Please try conversion without attaching to the VM.

Hi yaroslav (staff)

I  double, triple, quadruple etc checked the path.  Furthermore if you review the attached logs for the same process using the GUI you'll see the path is the exact same path. 
You said "Please try conversion without attaching to the VM"  <<< what exactly do you mean?  I don't follow.

Thanks

There are no logs attached, please attach the full conversion logs from C:\Program Files\StarWind Software\StarWind V2V Converter\logs.

Please see attached two log file. One is for the failed cmd line log and the other is the successful GUI log using the same identical information.

The main difference I see in the logs is that the successful GUI method uses a different function called ESXVmdk::ParseFile: to access the datastore whereas the failed command line method uses a function called VMwareFile::InternalParseFile:

Hi,
Thanks for your collaboration let us wait for the R&D team response (I had to escalate this matter to them).

Just a quick question. Initially, you have converted with GUI, then with CLI, am I right? Did you remove the file from the destination directory? V2V might be erring like that if the file with the same name already exists in the destination directory.

yaroslav, this has nothing to do with the destination location. The logs clearly show an error connecting to the ESXi datastore. This is a very simple setup and could be easily tested on your own systems and provide feedback. Has engineering wade in on this yet?

Has any member on this forum had success with using the cmd line to export a VM from VMware ESXi 6.7U3 host?

We need to be sure that the file was removed in the destination location. Please could you confirm that?

Yes, destination folder was and is empty every attempt I make.

Thank you for the update and confirming file removal after it was converted with GUI. Will further investigate the issue.

Hi,
Please try using in_host_type instead of in-host_type.

well sir, thank you very much for catching that mistake on my part. That was exactly the problem. It is working great! Thank you!!

quick follow up question... if the VM has two disks (two VMDK's) I assume I would need to just run the command again and capture the second disk (WP-W2019-AZ01_1.vmdk), correct?

thanks!

Hey,

No worries, always here to help. Yes, the disks have to be converted one by one. You still can try running the commands from some batch file.