VMware VirtualCenter Single Sign-On and VMware vCenter Lookup services fail to start after upgrading to VMware vCenter Server 5.1
search cancel

VMware VirtualCenter Single Sign-On and VMware vCenter Lookup services fail to start after upgrading to VMware vCenter Server 5.1


Article ID: 340222


Updated On:


VMware vCenter Server VMware vSphere ESXi


  • VMware VirtualCenter Single Sign-On (SSO) service fails to start after:

    • Upgrading to vCenter Server 5.1 from a previous version of vCenter Server
    • Applying an update on vCenter Server 5.1

  • VMware vCenter Lookup service fails to start after upgrading to vCenter Server 5.1
  • You see errors similar to:

    • Error 29942: Could not start service vCenter Single Sign On
    • Error 20010: Failed to Configure LookupService

  • The SSO Catalina logs, located at C:\Program Files\VMware\Infrastructure\SSOServer\logs\catalina*, may contain entries similar to:

    SEVERE [WrapperSimpleAppMain] org.apache.catalina.startup.Bootstrap.initClassLoaders Class loader creation threw exception
    java.lang.NoSuchFieldError: threadAllocatedMemorySupport
    at sun.management.VMManagementImpl.initOptionalSupportFields(Native Method)
    at sun.management.VMManagementImpl.<clinit>(VMManagementImpl.java:47)
    at sun.management.ManagementFactory.<clinit>(ManagementFactory.java:468)
    at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504)
    at org.apache.catalina.startup.Bootstrap.createClassLoader(Bootstrap.java:158)
    at org.apache.catalina.startup.Bootstrap.initClassLoaders(Bootstrap.java:91)
    at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:227)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)

  • In the C:\ProgramData\VMware\Infrastructure\Inventory Service\Logs \ wrapper.log file, you may see entries similar to:

    INFO | jvm 4 | <YYYY-MM-DD>T<time> | java.lang.NoClassDefFoundError: Could not initialize class java.net.InetAddress
    INFO | jvm 4 | <YYYY-MM-DD>T<time> | at org.tanukisoftware.wrapper.WrapperManager.openSocket(WrapperManager.java:3388)
    INFO | jvm 4 | <YYYY-MM-DD>T<time> | at org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:4068)
    INFO | jvm 4 | <YYYY-MM-DD>T<time> | at java.lang.Thread.run(Unknown Source)
    INFO | jvm 4 | <YYYY-MM-DD>T<time> | Server daemon died!</time>

  • The VMware vCenter Lookup service configuration fails
  • In the C:\ProgramFiles\VMware\Infrastructure\SSOServer\utils\logs\ discover-is.log file, you may see an entry similar to:

    ERROR: Could not connect to HTTP invoker remote service at [https://localhost:7444/ims/CommandServer]; nested exception is java.net.ConnectException: Connection refused: connect


VMware vSphere ESXi 5.1
VMware vCenter Server 5.1.x


This issue occurs when your Java Runtime environment (JRE) is corrupt. VMware vCenter Server and its services require JRE.


Note: Stop the java.exe process if it is running in Windows Task Manager.

To resolve the issue, overwrite the existing JRE folder (located in C:\Program Files\vmware\infrastructure\JRE) with a working copy from an existing install, or from the install media and replace the Java Cryptography Extension (JCE) files.
To collect the JRE folder from the Installer and replace JCE:
  1. Navigate to C:\Program Files\VMware\Infrastructure\jre.
  2. Take a backup of the current JRE folder.
  3. Launch the installer for SSO.
  4. Wait for the wizard to load. Do not click Next.
  5. Run the %temp% command.
  6. Search for jre.zip. If the %temp% does not contain the jre.zip, use the copy created in # Step 1.
  7. Extract contents from the jre.zip file and copy to C:\Program Files\vmware\infrastructure\JRE.
  8. Download JCE files from Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 6.

    Note: The preceding link was correct as of January 19, 2015. If you find the link is broken, provide feedback and a VMware employee will update the link

  9. Copy US_export_policy.jar and local_policy.jar files downloaded from the .zip file to C:\Program Files\VMware\Infrastructure\jre\lib\security.
  10. Proceed with the SSO installation.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box
VMware vCenter Server 5.1 にアップグレードした後、VMware VirtualCenter Single Sign-On および VMware vCenter Lookup Service を起動できない
升级到 VMware vCenter Server 5.1 之后,VMware VirtualCenter Single Sign-On 和 VMware vCenter Lookup Service 无法启动