- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Poceh,
I tried but the error remain ![]()
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Fantastic!
It works!
Thanks you very much!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cool it worked for me
Thanks lot
Cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I could not find converter-client xml file in Installer folder
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Find at %ProgramFiles(x86)%\VMware\VMware vCenter Converter Standalone\converter-client.xml
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also, change in the following file
%ProgramFiles(x86)%\VMware\VMware vCenter Converter Standalone\converter-client.xml
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Install VMWare converter v6.2.0 build 8466193
- 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
- Restart all VMWare vCenter Converter services.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This tip worked fine on vCenter 5.5. with with ESXi 5.5 and Converter 6.2. /Thanks all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It worked for me
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Perfect! This works for me!
Thanks kolonuk!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try to find XMLs in folder "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\"
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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