VMware vCenter Converter Standalone User Guide

Release Notes

・ VMware vCenter Converter Standalone 6.3 Release Notes.pdf |
・ VMware vCenter Converter Standalone 6.4 Release Notes.pdf |
・ VMware vCenter Converter Standalone 6.6 Release Notes.pdf |

User's Guide

・ using-vcenter-converter-sa-62.pdf |
・ using-vcenter-converter-sa-63.pdf |
・ using-vcenter-converter-sa-64.pdf |
・ using-vcenter-converter-sa-66.pdf |

Troubleshooting

Unable to create a VSS snapshot of the source volume

Converter Standalone 6.2
vSphere 7.0u3
Windows Server 2003 SP1

FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 2147754774 (0x80042316).

CAUSE

Multiple providers are associated with the operating system.

・ VMware Converter fails at 1% on Windows Server 2003 with the error code 2147754774 (1035241).pdf |

SOLUTION

To check if there are multiple providers and delete the second provider.

Error 29190: Could not generate secure sokets layer (SSL) key

Converter Standalone 6.6
vSphere 8.0u3
Windows Server 2012 R2

During install local client popup openssl.exe application was unable to start 0xc00007b and error 29190 could not generate secure sokets layer (SSL) key.

CAUSE

The api-ms-win-crt.dll lost on directory C:\Windows\SysWOW64.

SOLUTION

In the operating system of the source machine, download and install Visual C++ Redistributable for Visual Studio 2015

The converter virtual machine will auto revert to bootable snapshot while restart or shutdown operation system

Converter Standalone 6.6
vSphere 8.0u3

SITUATION

During converter 6.6 convert an physical machine to vSphere 8.0u3, and the final synchronization not commit. After convert job finished, power on the virtaul machine, change something, and then restart or shutdown system, the virtaul machine will be reconfiguration and revert snapshot.

The vmx file config is normal:

[root@ESXi-200:~] grep converter /vmfs/volumes/datastore02/remote-machine.sj.com/remote-machine.sj.com.vmx
converter.backupTime = "2024-10-23T07:32:37.462421Z"
converter.nextBitmapId = "IncrementalConversion(job-4:2)-[52 6c 16 10 1a 74 2f a1-06 cc b4 e8 9a 0e 1c 45]"
converter.cloningIteration = "2"
converter.isP2V = "1"
converter.isBackupSnapshot = "0"
converter.isBootableSnapshot = "1"
converter.backupType = "incremental"

So maybe converter standalone client will schedule connect with vSphere, and reconfiguration virtaul machine to traditional state.

SOLUTION

a. Deactivate the convert job, and it will not reconfigure destination virtual machine and then remove all snapshots of convert manual;
b. Commit the final synchronization of convert job.