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

Upgrading from vSphere 5.x to 6.0 fails (2110943)

  • 26 Ratings
Language Editions

Symptoms

  • SSL certificates are not compatible in vCenter Server after upgrading from vCenter Server 5.x to 6.x
  • You see the warning:
The system name in the vCenter Server 5.5 SSL certificate and the vCenter Single Sign-On 5.5 SSL certificates are not compatible. Please replace either the vCenter Server SSL certificates or the vCenter Single Sign-On SSL certificates so both vCenter Server and vCenter Single Sign-On SSL certificates use the same system name.

Note: For additional symptoms and log entries, see the Additional Information section.

Purpose

Regenerate SSL certificates on the vCenter Server 5.x to resolve SSL certificate issue during vCenter Server 5.x to 6.0 upgrade.

Cause

This issue occurs when: 
  • You Copy the SSL certificates during unsupported migration-based upgrade from previous versions of 5.x. 
  • Installing vCenter Server 5.x with only the IP address of the host operating system and then upgrading to vCenter Server 6.0 using the fully qualified domain name (FQDN).

Resolution

This is a known issue affecting vCenter Server 6.0. 

Currently, there is no resolution.

To work around this issue, regenerate the SSL certificates on the vCenter Server 5.x before upgrading to vCenter Server 6.0.
 
To regenerate the SSL certificates, use one of these options:
  • Replacing the vCenter Server certificates with CA-signed certificate. For related information, see the VMware Knowledge Base article (2096030).
  • Replace vCenter Server certificates with default-signed certificates. For related information, see the VMware Knowledge Base article (2074942).
  • Reinstall the vCenter Server stack:
    1. Uninstall vCenter Server in this order:
      • vCenter Server
      • vCenter Inventory Service
      • vSphere Web Client
      • vCenter Single Sign-On

    2. Rename the following directories under C:\ProgramData\VMware to ensure new certificates are generated using the correct hostname.

      • CIS to CIS.old
      • Infrastructure to Infrastructure.old
      • SSL to SSL.old
      • VMware VirtualCenter to VMware VirtualCenter.old
      • vSphere Web Client to vSphere Web Client.old

    3. Re-install vCenter Single Sign-On, vSphere Web Client, vCenter Inventory Service, and VMware VirtualCenter Server service.
    4. Reconnect to the existing database.
    5. Reconnect all of the hosts to 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

  • 26 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.
  • 26 Ratings
Actions
KB: