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

After upgrading to vCenter Server 5.0, the vCenter Service Status and Hardware Status tab cannot be accessed (2007824)

  • 16 Ratings


After upgrading to vCenter Server 5.0:

  • You are unable to access the vCenter Service Status and Hardware Status tab.

  • In the vws.log file, you see entries similar to:

    [2011-09-14 13:45:07,570 main INFO com.vmware.vim.vws.VwsContextListener] Starting VWS
    [2011-09-14 13:45:07,739 VwsInit INFO] Loading local SSL certificate
    [2011-09-14 13:45:14,993 http-8443-6 INFO com.vmware.vim.vmomi.core.types.impl.VmodlContextImpl$NonValidatingClassPathXmlApplicationContext] Refreshing com
    .vmware.vim.vmomi.core.types.impl.VmodlContextImpl$NonValidatingClassPathXmlApplicationContext@4f0fb89a: display name [com.vmware.vim.vmomi.core.types.impl.VmodlContextImpl$NonValidatingClassPathXmlApplicationContext@4f0fb89a]; startup date [Wed Sep 14 13:45:14 PDT 2011]; root of context hierarchy
    [2011-09-14 13:45:40,692 http-8443-6 INFO com.vmware.vim.vimclient.VimClientFactory] VMODL context has been initialized for CMS
    [2011-09-14 13:45:48,623 http-8443-6 ERROR com.vmware.vim.vimclient.VimClientFactory] Failed login to VC with NoClientCertificate exceptioncom.vmware.vim.binding.vim.fault.NoClientCertificate:
    inherited from com.vmware.vim.binding.vim.fault.VimFault:
    inherited from com.vmware.vim.binding.vim.fault.NoClientCertificate: Client connected without supplying a certificate.

  • In the sms.log file, you see entries similar to:

    2011-09-14 13:44:31,844 [main] DEBUG com.vmware.vim.sms.extension.CertTool - Found keystore: C:\ProgramData\VMware\VMware VirtualCenter\SSL\sms.keystore
    2011-09-14 13:44:31,955 [main] DEBUG com.vmware.vim.sms.extension.CertTool - Found truststore: C:\ProgramData\VMware\VMware VirtualCenter\SSL\sms.truststore
    2011-09-14 13:44:35,144 [main] DEBUG com.vmware.vim.sms.extension.CertTool - Added vpxd certificate to truststore
    2011-09-14 13:44:39,734 [Thread-15] DEBUG com.vmware.vim.sms.ServiceImpl - Initializing service...
    2011-09-14 13:44:44,271 [Thread-16] DEBUG com.vmware.vim.sms.StorageManagerImpl - [loadProviders] Loading previously registered providers from XDB
    2011-09-14 13:44:45,839 [main] DEBUG com.vmware.vim.sms.util.Crypt - private key format: ASN1Sequence
    2011-09-14 13:44:46,220 [main] INFO org.springframework.web.context.ContextLoader - Root WebApplicationContext: initialization completed in 33750 ms
    2011-09-14 13:44:46,584 [Thread-15] DEBUG com.vmware.vim.sms.util.VpxdConnection - Attempting to log in to vpxd at https://localhost:8089/sdkas extension 'com.vmware.vim.sms'
    2011-09-14 13:44:47,245 [Thread-15] ERROR com.vmware.vim.sms.util.VpxdConnection - Failed to connect to vpxdcom.vmware.vim.binding.vim.fault.NoClientCertificate:inherited from com.vmware.vim.binding.vim.fault.VimFault:inherited from com.vmware.vim.binding.vim.fault.NoClientCertificate: Client connected without supplying a certificate.

  • Custom certificate is already created.

  • The SSL certificates were created without an alias in vCenter Server 4.x, which does not work in vCenter Server 5.0.


This issue occurs if the vCenter Server certificates are replaced or corrupt.


To resolve this issue:

  1. Set up and configure OpenSSL. For details, see Configuring OpenSSL for installation and configuration of CA signed certificates in the vSphere environment (2015387).

  2. Click Start > Run, type cmd, and click OK. The Command Prompt window opens.

  3. Navigate to:


  4. To generate the rui.key and rui.crt files, run the command:

    openssl req -nodes -new -x509 -keyout rui.key -out rui.crt -days 3650 -config openssl.cfg

  5. To generate the rui.pfx file, run the command:

    openssl pkcs12 -export -in rui.crt -inkey rui.key -name rui -passout pass:testpassword -out rui.pfx

    Note: testpassword is the default password and must not be changed.

  6. Copy these files to the SSL directory located at C:\ProgramData\VMware\VMware VirtualCenter\:

    • rui.pfx
    • rui.key
    • rui.crt

  7. Reset the VPXD db password:
    1. Click Start > Run, type cmd, and click OK. The Command Prompt window opens.
    2. Navigate to:

      C:\Program Files\VMware\Infrastructure\VirtualCenter Server

    3. Run the command:

      vpxd.exe -p

    4. When prompted, enter the password.

  8. Stop and restart these services:

    • VMware VirtualCenter Server
    • VMware VirtualCenter Management Webservices
    • vCenter Inventory Service
    • VMware vSphere Profile-Driven Storage Service

    Note: After the above steps, the ESX/ESXi hosts may become disconnected from the vCenter Server and may require reconnecting.

Additional Information

See Also

Update History

02/06/2012 - Added additional symptom on SSL certificates 06/28/2012 - Added note that testpassword is mandatory. 06/28/2012 - Changed link to openssl download. 03/08/2013 - added linked kb article

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.


  • 16 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.
  • 16 Ratings