vCenter

Hi,

I want to migrate VMs from vCenter 5.5.0 U1b to vCenter 6.5 U1b using Converter Standalone 6.2.

When Converter tries to connect the source vCenter (5.5) I receive this error:

"A general system error occurred: SSL Exception: error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol"

The error seems to be related to the certificate.

Could you help me?

Thanks

Andrea

Ok, this is because of TLS1.0 disablement in new versions but not in vCenter 5.5

As workaround you can enable TLS1.0 in converter-server.xml, converter-worker.xml and converter-agent.xml by changing tag <sslOptions> from 123422720 to 56313856 and then restart services.

HTH

Hi Poceh,

I tried but the error remain :-(

Thanks

I'm forgot - put the same option in converter-client.xml placed in installation folder.

If still not working the best way is to upgrade 5.5 to latest available.

HTH

Fantastic!

It works!

Thanks you very much!

I could not find converter-client xml file in Installer folder

Find at %ProgramFiles(x86)%\VMware\VMware vCenter Converter Standalone\converter-client.xml

also there are 3 files in here

C:\ProgramData\VMware\VMware vCenter Converter Standalone

I changed dose as well but still have this same problem. Did anyone find a proper solution?

Also, change in the following file

%ProgramFiles(x86)%\VMware\VMware vCenter Converter Standalone\converter-client.xml

HI, I make all step by step of this treat, but when its converting I get the next same issue by the side of the destination my vmware esx 5.1 (Im converting from a Hyperv VM):

Maybe I have to change values in the esxi 5.1 by I´dont know where I have to do it...

Thanks.

Hernán

Probably you miss to change sslOptions in some XML file or don't restart services after change of sslOptions value.

HTH

I recheck all xml in the server 2012 64bit where I install the convert vmware standalone 6.2, and targetting to another server 2012 with the hyperv VM.

I try again to another destination (not a esxi 5.1), to Vcenter Vmware with server 2008r2 64bit, where I do the same, installing and modify the ssl value´s in the xml file but still the same issue:

This is what console show´s whe is converting:

I don´t know what more I can do...

Thanks

Could you upload log bundle?

I have the same problem as hernanSue. :smileysad:

I use vCenter Converter Standalone Server 6.2.0 convert to ESXi 5.5.0.

Have changed all references of "123422720" to "56313856" in documents.

edit the converter-worker.xml, find the <useSsl>true</useSsl> and change the value to <useSsl>false</useSsl>

Restart the service on the machine.

Always failed at 1% with FAILED: An error occurred during the conversion: 'SSL Exception: error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:
unsupported protocol'

Thanks a lot.

Attachment(s)

vmware-converter-server-17.log.zip   7 KB 1 version

Cool it worked for me

Thanks lot

Cheers

Great, it works .

Thank you and Merry Christmas !

Its work for me. I enable TLS1.0 in "converter-agent.xml by changing tag <sslOptions> from 123422720 to 56313856". That´s it.

I´ve Vmware ESXi v4.1.0 version installed.

This worked for me.

Go to C:\ProgramData\VMware\VMware vCenter Converter Standalone

Open to edit the converter-worker.xml

Find the <useSsl>true</useSsl> and change the value to <useSsl>false</useSsl>

Restart the Restart the VMware vCenter Converter Standalone Worker service on the machine

This solution is for ESX 5.5 or older version that need TLS 1.0

source: VMware Knowledge Base

I had this same issue when attempting to migrate a virtual machine from an ESXi 5.0.0 host to a new ESXi 6.5.0 host. I was using the VMWare Converter standalone utility version 6.2.0. I ended up downgrading to VMWare Converter version 6.1.1 which worked just fine.

OK, just to consolidate info in one place, as no one specified ALL the correct info in all the posts I could find:

This is how it worked for me - I was moving machines from ESX 5.1.0 build 799733 to ESX 6.5.0 Update 1 build 5969303

1. Install VMWare converter v6.2.0 build 8466193
2. Change all references of "123422720" to "56313856" in the following files:
   • C:\ProgramData\VMware\VMware vCenter Converter Standalone\converter-agent.xml
   • C:\ProgramData\VMware\VMware vCenter Converter Standalone\converter-server.xml
   • C:\ProgramData\VMware\VMware vCenter Converter Standalone\converter-worker.xml
   • C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\converter-client.xml
3. Restart all VMWare vCenter Converter services.

This tip worked fine on vCenter 5.5. with with ESXi 5.5 and Converter 6.2. /Thanks all.

It worked for me

Perfect! This works for me!

Thanks kolonuk!

Con esto pude resolver el problema.

Gracias

Thanks, It worked.

good help but checge folder + copy files:

- converter-agent.xml

- converter-server.xml

- converter-worker.xml

- converter-client.xml

old program update, if i update the program, you lose again i configure the files with the same problem

Downgrading to 6.1.1 also fixed mine.

https://my.vmware.com/group/vmware/details?downloadGroup=CONV611&productId=702&rPId=20185#errorCheckDiv

I had the problem with the converter 6.2 ... there is no longer a converter-worker.xml there is only one singel file - converter-client.xml

so I entered the SSL option code, then the converter could connect... and then I tried to convert a VM and it spit into my face with a message "cant read hardware settings". wtf?

I belive it can't by design... and this has to do with some no longer supported storage configurations. With the other direction I had to hack the vmx files, then the converter 6.2 did convert my player 6.5 VMs... the root cause was a vmdk file pointing to a physical disk. But I wont touch my "golden sample" which contains 5 years of lessons, research and tests. And there are only iSCSI or local volumes...

I have to say today I lost my faith in VMware products... also because of a purple screen with an original and vmware supported Intel Quadport E1000 card in a VMware supported mainboard...

Try to find XMLs in folder "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\"

HTH

The "can't retrieve hardware information" error comes from the format of old .VMX files (< ESX 5.5 or < WS 10) aid it is not related to the SSL problem, that happens with VMX files on a regular hard drive too. I know the workarounds, but the solution is to do the convert with an older converter version.

The thread is about SSL connections and fix for TLS1.0 with XML files.

If you experience issues to connect with UI, the same issue will happens with services' connections, so you can't change only value in converter-client.xml and work successfully.

For your other problem(s) you must open new thread(s) attaching appropriate logs into.

Regards

I'll give it a try. The VMX version incompatibility  I have found out this by myself, but maybe the converter 6.1.1 is more stable and doesn't just stop. On the other hand it could be related to my network card, becasue it gave me a purple screen on heavy usage recently.

I get an Access Denied error message when I try to save the changed file.  All of the VMWare Converter services are off.  Next idea?

Do the changes in configuration XML files "as administrator". After that restart services.

HTH

None of the options worked for me so as a workaround, I removed one host from the cluster and vCenter altogether and just pointed the converter tool to the ESXi host directly, as soon as it finished, i simply put the host back into vCenter with the new converter VMs..

Segue esse tutorial.

https://pupuweb.com/vmware-vcenter-converter-standalone-show-ssl-exception-error-14077102-ssl23_get_server_hello-unsupported-protocol/