Search the VMware Knowledge Base (KB)
View by Article ID

"Exception: Failed to configure identity manager" error when upgrading to vCenter Server 6.5 (2148200)

  • 15 Ratings
Language Editions

Symptoms

  • Upgrading to vCenter Server 6.5 fails with this error:

    Encountered an internal error.  Traceback (most recent call last):   File "D:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 2018, in main     vmidentityFB.boot()   File "D:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 347, in boot     self.configureIdentityManager(self.__idmRetryCount, self.__idmRetryInterval)   File "D:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.p ", line 554, in configureIdentityManager     raise Exception('Failed to configure identity manager') Exception: Failed to configure identity manager

  • In the vmware-sts-idmd.log file, there is an error similar to:

    [ERROR] [IdmServer] IDM Server has failed to start java.lang.UnsatisfiedLinkError: Unable to load library 'ssleay32.dll': The specified module could not be found.

    Note: Thevmware-sts-idmd.log file is found in the VMware-VCS-logs-<year><month><day><hour><minute><second>.zip file which is created on on the vCenter Server after a failed upgrade.
  • In vmidentity-firstboot.py_PID_stdout.log you see the following error,

    2016-11-30T14:53:56.901Z Exception: Traceback (most recent call last):
      File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 2018, in main vmidentityFB.boot()
      File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 346, in boot self.upgradeSystemDomainAdmins()
      File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 1968, in upgradeSystemDomainAdmins raise Exception('Failed to upgrade system domain admins.') Exception: Failed to upgrade system domain admins.

Cause

This issue occurs due to conflicting openssl libraries installed in the vCenter Server operating system.

Resolution

This is a known issue affecting vCenter Server 6.5.

Currently, there is no resolution.

To workaround this issue uninstall, the application which published the conflicting Openssl libraries.

Additional Information

Environment variables listed under OPENSSL_CONF can also cause this issue.

For example:

If OPENSSL_CONF=C:\OpenSSL-Win32\bin\openssl.cfg, is listed instead of the default libraries included with vCenter Server, you can check the environmental variables by opening a command prompt and running the set command on the vCenter Server.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 15 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 15 Ratings
Actions
KB: