Release: VMware vCenter Server 5.5.0.b & vCenter Server Appliance 5.5.0b

At December 22 VMware released vCenter Server 5.5.0.b as well as vCenter Server Appliance 5.5.0b.

This release does not contain new features or enhancements but contains resolved issues only.

The release notes are here.

Download here 

Resolved issues

Upgrade and Installation

  • Upgrading the vSphere Web Client to vSphere 5.5 fails with an error
    Attempts to upgrade the vSphere Web Client to vSphere 5.5 fails when they are installed in a custom, non-default location. An error message similar to the following is displayed:

    Error 29107. The service or solution user already registered...

    This issue is resolved in this release.

vCenter Server, vSphere Client, and vSphere Web Client

  • vCenter Server 5.5 displays a warning message in the yellow configuration issues box on the Summary tab of the hosts
    When you connect to VMware vCenter Server 5.5 using the vSphere Client or the vSphere Web Client, the Summary tab of the ESXi 5.5 host displays a warning message similar to the following in the yellow configuration issues box:

    Quick stats on <hostname> is not up-to-date

    This issue is resolved in this release.

  • Attempts to export log bundle using the Log Browser fails
    When you attempt to export a log bundle using the Log Browser interface, the browser window displays a Secure Connection Failed error page with the following message:

    Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number.

    This issue is resolved in this release.

    Note: If you are upgrading from the vCenter Server 5.5 version, see the workaroundprovided in the known issues section.

  • Attempts to log in to vSphere Web Client result in an error message
    Attempts to log in to the vSphere Web Client result in an error message if the Local OS identity source is not configured in the SSO configuration page. An error message similar to the following is displayed:

    Failed to authenticate to inventory service <server IP>:10443

    This issue is resolved in this release.

vCenter Single Sign-On

  • After installation of vCenter Single Sign-On 5.5 attempts to connect to the vCenter Single Sign-On server might fail
    After you install the vCenter Single Sign-On 5.5 on a Windows system that is not domain joined and has multiple network interfaces, attempts to connect to the SSO server from other components might fail. You might see a message similar to the following:

    Could not connect vCenter Single Sign On....make sure the IP address is specified in the URL.

    This issue is resolved in this release.

  • When upgrading from vCenter Server Appliance 5.0.x to 5.5, vCenter Server fails to start if you select an external vCenter Single Sign-On
    If you select an external vCenter Single Sign-On instance while upgrading the vCenter Server Appliance from 5.0.x to 5.5, vCenter Server fails to start after the upgrade. In the appliance management interface, vCenter Single Sign-On is listed as Not configured.

    This issue is resolved in this release.

  • Attempts to upgrade vCenter Single Sign-On to 5.5 fails if the SSL certificates being in PKCS12 format
    When you upgrade from vCenter Single Sign-On 5.1 to 5.5, the installer fails and rolls back, before you select an SSO deployment method, with the following error message:

    vCenter Single Sign-On Setup Wizard ended prematurely because of an error

    An error message similar to the following is logged in the vim-sso-msi.log file:

    DEBUG: Error 2896: Executing action ExtractKeystoreInfo failed.

    This issue is resolved in this release by displaying the following warning message:

    Setup has detected a problem with your current configuration which will cause upgrade to fail. Your certificate key store format might be unsupported. See VMware KB 2061404.

  • Upgrade to vCenter Single Sign-On 5.5 fails before you select the deployment type
    Attempts to upgrade to vCenter Single Sign-On 5.5 fail before you can select the deployment type. Error messages similar to the following are logged in the vminst.logfile:

    VMware Single Sign-On-build-1302472: 09/26/13 15:18:19 VmSetupMsiIsVC50Installed exit: Error = 1605
    VMware Single Sign-On-build-1302472: 09/26/13 15:18:19 VmSetupGetMachineInfo exit: Error code = 1605

    This issue is resolved in this release.

  • Active Directory is not added automatically as identity resource in vCenter Single Sign-On 
    When you initially install the vCenter Single Sign-On in a Windows system that is part of an Active Directory, the Active Directory is not automatically added as the default identity resource in the vCenter Single Sign-On server.

    This issue is resolved in this release.

  • Unable to edit a vSphere 5.5 Identity Source in the vSphere Web Client
    You cannot edit a vSphere 5.5 Identity Source in the vSphere Web Client as the Edit icon is disabled for the Active Directory Identity Source. You see a warning message similar to the following:

    Edit Identity Source (Not available)

    This issue is resolved in this release.

  • Unable to modify password or remove users from system-domain after you upgrade from vCenter Server 5.1 to 5.5
    After you upgrade from vCenter Server 5.1 to vCenter Server 5.5, you are unable to remove the users from system-domain or modify the password for these users.

    This issue is resolved in this release.

  • vCenter Single Sign-On Identity Management service repeatedly logs the message: Enumerate trusts failed Failed to enumerate domain trusts for domain_name (dwError – 5)
    When you configure the Active Directory (Integrated Windows Authentication) Identity Source in vCenter Single Sign-On, the vmware-sts-idmd.log file, located atC:ProgramDataVMwareCISlogsvmware-sso, repeatedly logs the following message:

    INFO [ActiveDirectoryProvider] Enumerate trusts failed Failed to enumerate domain trusts for domain_name(dwError - 5)This issue is resolved in this release.

Virtual Machine Management

  • Attempts to clone, create, or storage vMotion a virtual machine fails when the destination data store is a Storage DRS POD
    In vCenter Server, operations that consume storage space such as virtual machine creation, cloning, or storage vMotion might fail if the destination data store is a Storage DRS POD and the storage device has the de-duplication feature turned on. The following error is displayed:

    Insufficient disk space on datastore xxxxx

    This issue is resolved in this release.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Current ye@r *