vCenter Migration fails with Error : Internal error occurs during upgrade setup | Os Windows is currently not supported | Cannot generate certificates on remote Windows target with address=127.0.0.1

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• vCenter Migration fails with Error : Internal error occurs during upgrade setup | Os Windows is currently not supported
• Cannot generate certificates on remote Windows target with address=127.0.0.1

MA log :

2020-04-20T13:30:28.266Z INFO deployer.migration_env_deployer Preparing migration environment...2020-04-20T13:30:28.266Z INFO deployer.migration_env_deployer Setup targets: [<model.components.Target object at 0x0000000004011CC0>]
2020-04-20T13:30:28.266Z INFO os_utils Trying to retrieve the host localhost python2 path2020-04-20T13:30:28.321Z INFO deployer.migration_env_deployer Created target configuration for target: Windows target with address=127.0.0.1

                Python2: None

                Python3: C:\mig7984.tmp\PFiles\VMware\CIS\python\python.exe

                Working Directory: C:\mig7984.tmp\PFiles\VMware\CIS\cis_upgrade_runner\upgrade_working_directory

                Export Directory: None

                Upgrade Scripts Directory: C:\mig7984.tmp\PFiles\VMware\CIS\cis_upgrade_runner\payload\component-scripts

                Logs Directory: C:\Users\ADMDIN~1.LEN\AppData\Local\Temp\vcsMigration

2020-04-20T13:30:28.483Z ERROR deployer.migration_env_deployer Cannot generate certificates on remote Windows target with address=127.0.0.1.
2020-04-20T13:30:28.484Z ERROR deployer.migration_env_deployer Remote command stdout:

Remote command stderr: 2020-04-20T13:30:28.472Z ERROR __main__ Os Windows is currently not supported^M

Environment

VMware vCenter Server 6.5.x

Cause

This usually happens when the OpenSSL DLL files are being used by third party applications.
We can check if any third party applications are installed from Path Variables. You can use set command in CMD prompt or by echo "%path%

For Example:

Run echo "%path% in RUN Window

Path=C:\Program Files\EMC NetWorker\nsr\bin;C:\Program Files (x86)\VMware\VMware vSphere CLI\Perl\site\bin;C:\Program Files (x86)\VMware\VMware vSphere CLI\Perl\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\MIT\Kerberos\bin;C:\Program Files\VMware\vCenter Server\openSSL

Or

Path=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Dell\SysMgt\oma\bin;C:\Program Files\Dell\SysMgt\shared\bin;C:\Program Files\Dell\SysMgt\idrac;C:\Program Files\MIT\Kerberos\bin;C:\Program Files\VMware\vCenter Server\openSSL

Resolution

From the above output we can see there are third party software's which can load the OpenSSL/Pyhton DLL files used by VMware.

To resolve this issue we can suggest the following.

1. Remove 3rd party applications.
2. Update the Environmental Variable and remove the third party applications path from Path Variable.
3. Update the Path Variable and set C:\Program Files\VMware\vCenter Server\openSSL as the first line.
4. Open C drive in Explorer and search for libeay32.dll and ssleay32.dll on the entire C drive. If you see these files other than VMware path, rename those files (please make a note of those locations). Rename the DLL files to .dll_

For Example:


Once done, retry the Migration.