VMware

vCenter Server 5.5.0a Release Notes

VMware vCenter Server™ 5.5.0a | 31 OCT 2013 | Build 1378901

vCenter Server Appliance 5.5.0a | 31 OCT 2013 | Build 1398493

Last updated: 21 JAN 2014

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of VMware vCenter Server 5.5.0a includes a number of bug fixes that have been documented in the Resolved Issues section.

Earlier Releases of vCenter Server 5.5

Features and known issues of vCenter Server are described in the release notes for each release. To view release notes for earlier releases of vCenter Server 5.5, see VMware vSphere 5.5 Release Notes.

Internationalization

VMware vSphere 5.5 is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Korean
  • Simplified Chinese

Compatibility and Installation

ESXi, vCenter Server, and vSphere Web Client Version Compatibility

The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware vSphere components, including ESXi, VMware vCenter Server, the vSphere Web Client, and optional VMware products. Check the VMware Product Interoperability Matrix also for information about supported management and backup agents before you install ESXi or vCenter Server.

The vSphere Client and the vSphere Web Client are packaged on the vCenter Server ISO. You can install one or both clients by using the VMware vCenter™ Installer wizard.

vSphere Client Connections to Linked Mode Environments with vCenter Server 5.x

vCenter Server 5.5 can exist in Linked Mode only with other instances of vCenter Server 5.5.

Installation Notes for This Release

Read the vSphere Installation and Setup documentation for guidance about installing and configuring vCenter Server.

Although the installations are straightforward, several subsequent configuration steps are essential. Read the following documentation:

Upgrades for This Release

For instructions about upgrading vCenter Server, see the vSphere Upgrade documentation.

Open Source Components for VMware vSphere 5.5

The copyright statements and licenses applicable to the open source software components distributed in vSphere 5.5 are available at http://www.vmware.com/download/vsphere/open_source.html, on the Open Source tab. You can also download the source files for any GPL, LGPL, or other similar licenses that require the source code or modifications to source code to be made available for the most recent available release of vSphere.

Product Support Notices

  • vSphere Web Client. Because Linux platforms are no longer supported by Adobe Flash, vSphere Web Client is not supported on the Linux OS. Third party browsers that add support for Adobe Flash on the Linux desktop OS might continue to function.

  • VMware vCenter Server Appliance. In vSphere 5.5, the VMware vCenter Server Appliance meets high-governance compliance standards through the enforcement of the DISA Security Technical Information Guidelines (STIG). Before you deploy VMware vCenter Server Appliance, see the VMware Hardened Virtual Appliance Operations Guide for information about the new security deployment standards and to ensure successful operations.

  • vCenter Server database. vSphere 5.5 removes support for IBM DB2 as the vCenter Server database.

  • VMware Tools. Beginning with vSphere 5.5, all information about how to install and configure VMware Tools in vSphere is merged with the other vSphere documentation. For information about using VMware Tools in vSphere, see the vSphere documentation. Installing and Configuring VMware Tools is not relevant to vSphere 5.5 and later.

  • vSphere Data Protection. vSphere Data Protection 5.1 is not compatible with vSphere 5.5 because of a change in the way vSphere Web Client operates. vSphere Data Protection 5.1 users who upgrade to vSphere 5.5 must also update vSphere Data Protection to continue using vSphere Data Protection.

Resolved Issues

This section describes resolved issues in this release in the following subject areas:

Upgrade and Installation

  • Attempts to upgrade vCenter Single Sign-On (SSO) 5.1 Update 1 to version 5.5 might fail with error code 1603
    When the SSL certificate for the SSO service does not provide the IP address of your SSO system in the Subject Name or Subject Alternate Name (SAN) field, and the registry entry value has the IP address instead of the Fully Qualified Domain Name (FQDN) of the SSO system, the SSO upgrade rolls back.
    This issue occurs because the SSO 5.1 installer generates an SSL certificate with Subject Alternate Name enabled with FQDN. When SSO 5.1 is updated to SSO 5.1 Update 1, the SSO installer changes the fqdnip registry entry from the FQDN of the SSO system to the IP address of the system. When you Update SSO 5.1 Update 1 to version 5.5, the installer fails because it compares the FQDN of the SSO systems in the SSL certificate with IP address in the related registry.

    The vim-sso-msi.log file contains entries similar to the following:
    • Action 10:06:03: PostInstallScripts. Importing Lookupservice data...
      CustomAction DoUpdateAndMigrateTasks returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)


    • MSI (s) (0C:E8) [08:55:53:996]: Hello, I'm your 64bit Elevated custom action server.
      Action 08:55:54: PostInstallScripts. Configuring SSO Components...
      PostInstallScripts: PostInstallScripts
      PostInstallScripts: PostInstallScripts
      PostInstallScripts: PostInstallScripts
      CustomAction BootstrapAll returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 08:56:09: InstallFinalize. Return value 3.
      MSI (s) (0C:B4) [08:56:09:908]: User policy value 'DisableRollback' is 0

    This issue is resolved in this release. If SSL certificates of SSO 5.1 Update 1 use the IP address in the SAN field when you attempt an upgrade to SSO 5.5, a message indicates that SSO requires an FQDN to continue with the upgrade. You need to accept this message and allow SSO to use FQDN instead of IP address.
  • Attempts to log in to the vCenter Server might be unsuccessful after you upgrade from vCenter Server 5.1 to 5.5
    You might be unable to log in to the vCenter Server after you upgrade from vCenter Server 5.1 to 5.5. Error messages similar to the following might be displayed:

    Failed to import identity source:EMEA-Alias
    java.lang.IllegalArgumentException: Ids non-local-os or non-system-domain domainName [EMEA] should contain a '.'


    This issue occurs when vCenter Single Sign-On (SSO) is unable to recognize Single Label Domain (SLD) identity source during the upgrade, and as a result, the existing identity sources are not added to the new SSO installation.

    This issue is resolved in this release.
  • Unable to change the vCenter SSO administrator password on Windows in the vSphere Web Client after you upgrade to vCenter Server 5.5 or vCenter Server Appliance 5.5
    When you upgrade to vCenter Server to version 5.5 or vCenter Server Appliance (VCSA) to version 5.5, you might be unable to change the vCenter Single Sign-On (SSO) administrator password on Windows in the vSphere Web Client. The account information fields are grayed out when you attempt to edit the user details.
    You might encounter the following issues:
    • In the vSphere Web Client, the Change Password option of the drop-down menu in the upper-right corner might be disabled.
    • All the fields in the Edit User Details dialog box might be disabled.

    You might not encounter this issue when you perform a new installation of Windows based SSO 5.5 or VCSA 5.5.

    This issue is resolved in this release.

vCenter Server and vSphere Client

  • VPXD service might fail due to MS SQL database deadlock for the issues with VPXD queries that run on VPX_EVENT and VPX_EVENT_ARG tables
    The VPXD service might fail due to MS SQL database deadlock for the issues with VPXD queries that run on VPX_EVENT and VPX_EVENT_ARG tables. This deadlock occurs because of a database connection that adds new events into the VPX_EVENT parent table and VPX_EVENT_ARG child table.

    This issue is resolved in this release.
  • Attempts to search the inventory in vCenter Server by using vSphere Web Client might not return any results with proper permissions
    Attempts to search the inventory in a vCenter Server by using vSphere Client might not return any results.
    Attempts to search the inventory in vCenter Server using vSphere Web Client might also fail with an error message similar to the following::
    Access to perform that operation is denied.

    When you attempt to connect to the vCenter Server using vSphere Web Client with proper permissions, the inventory will be displayed as empty.
    These issues occur when the inventory service is unable to compute the permissions properly.

    This issue is resolved in this release.
  • vCenter Server 5.5 might fail to start after vCenter Single Sign-On Server restarts
    If you restart the vCenter Single Sign-On Server or the vCenter Server system where Active Directory or OpenLDAP identity source is configured, the vCenter Server might fail to start and logs an error message similar to the following:

    Unable to create SSO facade: Invalid response code: 404 Not Found

    This issue is resolved in this release.
  • Attempts to log in to vCenter Server Appliance 5.5 using domain credentials in vSphere Web Client are unsuccessful in certain conditions
    Attempts to log in to vCenter Server Appliance 5.5 by using your domain credentials in vSphere Web Client with proper permissions might fail with an error message similar to the following:
    The authentication server returned an unexpected error: ns0:RequestFailed: The specified request failed.. The error may be caused by a malfunctioning identity source.
    This issue occurs when the name of the Active Directory or Open LDAP group that you belong to has a group name that contains parentheses.

    This issue is resolved in this release.

vCenter Single Sign-On

  • Active Directory group users unable to log in to the vCenter Inventory Service 5.5 with vCenter Single Sign-On
    In vCenter Inventory Service 5.5, group names are case sensitive. In case of inconsistencies between the group name in Active Directory and the group name in vCenter Server permissions list, users of the group cannot log in to the Inventory Service with SSO. The following error message is displayed:

    Client is not authenticated to VMware Inventory Service


    This issue is resolved in this release.
  • Attempts to log in to vCenter Single Sign-On and vCenter Server might fail for users with the same common name in OpenLDAP
    If the OpenLDAP identity source contains multiple users with same common name and with different surnames, those users might not be able to log in to vCenter Single Sign-On and vCenter server.
    The vmware-sts-idmd.log file contains entries similar to the following:

    ERROR [ServerUtils] Exception 'com.vmware.identity.idm.InvalidPrincipalException: user <XXXX> doesn't exist or multiple users with same name'

    This issue is resolved in this release.
  • Attempts to log in to vCenter Single Sign-On and vCenter Server might fail for OpenLDAP 2.4 users who have attributes with multiple values attached to their account
    For OpenLDAP 2.4 identity source users have attributes with multiple values attached to their profile, attempts to to log in to vCenter Single Sign-On and vCenter server might fail.
    The vmware-sts-idmd.log file contains entries similar to the following:

    ERROR [ServerUtils] Exception 'com.vmware.identity.idm.InvalidPrincipalException: multiple values for attributes for cn, descrption, upn, firstName, lastName
    and emailAddr are not allowed :< XXXXX>'


    This issue is resolved in this release.
  • Attempts to log in to vCenter Server might fail for an OpenLDAP user whose account is not configured with a UUID
    On OpenLDAP 2.4 servers, if users are configured using only common names and not universally unique identifiers (UUIDs), attempts to log in to vCenter server might fail for those users.

    The vSphere Web Client displays an error message similar to the following:
    Unable to create the managed object for - urn:vmomi:TaskManager:TaskManager:C36FE38B-D9DE-47F1-A116-A85E67838336

    The vmware-sts-idmd.log file contains entries similar to the following:
    [2013-09-26 17:15:31,417 ERROR [IdentityManager] Failed to find person user [<user>@<domain.com>] in tenant [vsphere.local]
    2013-09-26 17:15:31,417 ERROR [ServerUtils] Exception 'java.security.InvalidParameterException: Null or empty values'
    java.security.InvalidParameterException: Null or empty values
     at com.vmware.identity.idm.server.provider.BaseLdapProvider.getStringValue(BaseLdapProvider.java:183)
     at com.vmware.identity.idm.server.provider.ldap.LdapProvider.buildPersonUser(LdapProvider.java:1792)
     at com.vmware.identity.idm.server.provider.ldap.LdapProvider.findUser(LdapProvider.java:416)


    This issue is resolved in this release.

  • Unable to add an Open LDAP provider as an identity source if the Base DN does not contain an “dc=” attribute
    You might be unable to add an Open LDAP provider as an identity source if you do not provide the basic domain name (Base DN) in the form of "dc= ,..." and the user name in the form of “cn= ,dc= ,...”.
    If you provide the base DN in any other format, you cannot add the identity source to vCenter Single Sign-On (SSO).

    This issue is resolved in this release.

  • Active Directory authentication fails when vCenter Single Sign-On 5.5 runs on Windows Server 2012 and the AD Domain Controller is also on Windows Server 2012
    Users cannot authenticate with a vCenter Single Sign-On (SSO) 5.5 system that is installed on Windows Server 2012 when the system is joined to an Active Directory domain controller also running on Windows Server 2012. Users receive this error message when they attempt to log in by using the vSphere Web Client:

    Cannot Parse Group Information


    For more information about this issue, see KB 2060901.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows:

Known issues not previously documented are marked with the * symbol.

Installation Issues

  • Reinstalling vCenter Single Sign-On 5.5 stops after displaying the message: Configuring SSO Components... (KB 2059131)
  • Storage profiles not visible in the vSphere Web client after you install and uninstall vCenter Server
    If you uninstall vCenter Server from the Windows control panel item Add/Remove Programs or Programs and Features, Profile-Driven Storage is also uninstalled. When you reinstall vCenter Server, Profile-Driven Storage service is also installed, but you cannot see previously created Storage Profiles in the vSphere Web Client. New Storage Profiles can still be created.

    Workaround: To uninstall vCenter Server without uninstalling Profile-Driven Storage, use an MSI command. Then, when you reinstall vCenter Server, either through the installer wizard or from the command line, you can still see previously created Storage Profiles in the vSphere Web Client.

    To uninstall vCenter Server, use the following sample command as a model:
    msiexec.exe /x vCenter Server Product code
    For example:
    msiexec.exe /x {E1F05550-4238-4378-87F0-105147A251D9}
    The exact product code for vCenter can be obtained from the registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\VMware vCenter Server.

  • Login might fail for Local OS users if vCenter Single Sign-On 5.5 includes more than one node
    The Local OS identity source is available after install or upgrade, as follows: * The vCenter Single Sign-On installer adds the Local OS identity source to the vCenter Single Sign-On configuration. If you create more than one node, the Local OS from the primary node displays as an identity source on all other nodes. * If you upgrade a vCenter Single Sign-On High Availability environment, Local OS from the primary node displays as an identity source on all other nodes. However, even though the Local OS from the first node displays as an identity source in secondary nodes, Local OS users from the first node cannot log in on those secondary nodes.

    Workaround:None.

  • Installation using Simple Install fails on Windows Server 2008 R2 and Windows 2012 hosts
    If you use Simple Install to install vCenter Server and components on a Windows Server 2008 R2 or Windows 2012 host, and the host is configured to use DHCP IP addressing, the installation fails with warning and error messages.

    Workaround: Take one of the following actions.

    • On a Windows Server 2008 R2 or 2012 host: configure Windows Server to use a static IP and hostname.
    • On a Windows Server 2008 R2 host only: map the DHCP IP and hostname to the system's HOST file in the operating system.

  • During vCenter Single Sign-On 5.5 installation, you cannot specify a host name that is different than the FQDN of the machine on which you are installing vCenter Single Sign-On
    The vCenter Single Sign-On installer does not have the option to specify a host name during installation. The installer always uses the FQDN of the machine on which you are installing vCenter Single Sign-On. You cannot use a CNAME instead of the FQDN during installation.

    Workaround: None.

  • Error message 25205 appears during installation of vCenter Server on Turkish version of Windows Server
    On any Turkish version of Windows Server 2008 or 2012, when you install vCenter Server with the vCenter Server database on the same host machine, Error message 25205 appears.

    Workaround: Install and run the vCenter Server database from a remote English version of Windows Server.

  • Simple Install checks space requirements only on system drive
    Simple Install checks whether enough space is available before it starts the installation. However, it performs the check only if you install on a system drive. If you attempt to install on a non-system drive, the installer does not check whether enough space is available.

    Workaround: Check the disk space available on the target drive before installation. The minimum required free space for Simple Install is 10GB. More space is recommended. See the Installation and Setup documentation.

  • If the vCenter Single Sign-On installation fails and rolls back, the vCenter Server Java Components (JRE) and vCenter tc Server component remain installed
    When the Single Sign-On installation is canceled or fails, the installation rolls back to the pre-installation state, and a message states that the system was not modified. However, the vCenter Server Java Components (JRE) and vCenter tc Server component are still installed.

    Workaround: Remove the components manually in the Windows Programs and Feature control panel.

  • vSphere Authentication Proxy installation fails if the installation path contains non-ASCII characters
    If the installation path contains non-ASCII characters, the vSphere Authentication Proxy installation fails with the error message Error 29106. Unknown Error.

    Workaround: Make sure the installation path contains only ASCII characters.

  • Installation of vCenter Server and related components fails if the user name of the logged-in user contains non-ASCII characters
    If the user name of the user who is currently logged in contains non-ASCII characters, installation of vCenter Server, vCenter Inventory Server, vCenter Single Sign-On, or the vSphere Web Client fails with the error message: The user name contains non-ASCII characters. Please log in with a user name that contains only ASCII characters.

    Workaround: Log in with a user name that does not contain non-ASCII characters and retry the installation.

  • The autoPartition boot option might partition SSDs unintentionally
    In Visor (an ESXi dd image written to a device), the autoPartition boot option is set to TRUE by default. This setting causes all blank local disks, including SSDs that you might have intended to use with vFlash and Virtual SAN, to be partitioned.

    Workaround: Add skipPartitioningSsds=TRUE to the boot options line.

  • During vCenter Server Simple Install, a dialog box displays a warning that a script is causing the browser to run slowly
    The vCenter Server Simple Install option takes a significant amount of time to install or upgrade all required vCenter Server components. This might cause the Internet Explorer browser process that runs the vCenter Server installer autorun screen to display the following warning message:
    A script on this page is causing your browser to run slowly. If it continues to run, your computer might become unresponsive. Do you want to abort the script?

    The warning dialog is displayed when the installation takes longer than the time set by the Windows registry entry: HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles\MaxScriptStatements

    This issue has been observed most frequently on the Windows Server 2012 operating system.

    Workaround: Click No in the warning message, or set the value for the MaxScriptStatements registry entry to 0xffffffff.

Upgrade Issues

  • Upgrading the vSphere Web Client to vSphere 5.5 fails with the error: Error 29107. The service or solution user already registered (KB 2062685)*
  • Upgrade to vCenter Server 5.5 does not detect expired SSL certificates
    When you use Simple Install to upgrade to vCenter Server 5.5, the installer does not detect any expired SSL certificates.

    If you upgrade from 5.1.x to 5.5 using the individual installers in a Custom Install, only the vSphere Web Client detects expired SSL certificates and stops the installation. vCenter Single Sign-On displays a generic warning message to verify the validity of SSL certificates. The vCenter Inventory Service and vCenter Server individual installers do not detect expired SSL certificates.

    Workaround: Before you start the upgrade to vCenter Server 5.5, using either Simple Install or the individual installers in a Custom Install, check the validity of the SSL certificates of vCenter Single Sign-On, the vSphere Web Client, vCenter Inventory Service, and vCenter Server. Replace any expired SSL certificates with valid certificates before starting the upgrade process.

  • After upgrade from vCenter Server Appliance 5.0.x to 5.5, vCenter Server fails to start if an external vCenter Single Sign-On is used
    If the user chooses to use an external vCenter Single Sign-On instance while upgrading the vCenter Server Appliance from 5.0.x to 5.5, the vCenter Server fails to start after the upgrade. In the appliance management interface, the vCenter Single Sign-On is listed as not configured.

    Workaround: Perform the following steps:

    1. In a Web browser, open the vCenter Server Appliance management interface (https://appliance-address:5480).
    2. On the vCenter Server/Summary page, click the Stop Server button.
    3. On the vCenter Server/SSO page, complete the form with the appropriate settings, and click Save Settings.
    4. Return to the Summary page and click Start Server.

  • After you upgrade vCenter Single Sign-On 5.1.x in a high availability deployment with a load balancer to version 5.5, you must reconfigure the load balancer
    During the upgrade from vCenter Single Sign-On 5.1 to 5.5, the file server.xml is migrated, but you must update the file manually after the upgrade.

    Workaround: See the topic Reconfigure the Load Balancer After Upgrading a vCenter Single Sign-On High Availability Deployment to Version 5.5 in the vSphere Upgrade documentation.

  • vCenter Server 5.1 not visible after you upgrade vSphere Web Client and vCenter Single Sign-On to version 5.5
    Suppose you upgrade vSphere Single Sign-On and the vSphere Web Client from version 5.1 to version 5.5, but you do not upgrade the vCenter Server system. If you log in to the vSphere Web Client after the upgrade, vCenter Server system version 5.1 is not visible. This is a problem only for the Windows upgrade, and not when you upgrade vCenter Server Appliance.

    Workaround: Restart the vCenter Server system and the vSphere Inventory service (services.msc). To see the vCenter Server 5.1 inventory, log in as admin@System-Domain. See VMware Knowledge Base article 1003895.

  • The VMware VirtualCenter Server service might not start after you upgrade vCenter Server from version 5.0 Update 2 to version 5.5

    Workaround: Start the VMware VirtualCenter Server service manually:

    1. From the Windows Start menu, open the Administrative Tools control panel item.
    2. Select Services.
    3. Right-click VMware VirtualCenter Server and select Start.

  • vSphere Client and vSphere PowerCLI might fail to connect to vCenter Server 5.5, with a handshake failure
    When installed on a Windows XP or Windows Server 2003 host machine, the vSphere Client and vSphere PowerCLI might fail to connect to vCenter Server 5.5, with a handshake failure. vSphere 5.5 uses the Open SSL library, which, for security, is configured by default to accept only connections that use strong cipher suites. On Windows XP or Windows Server 2003, the vSphere Client and vSphere PowerCLI do not use strong cipher suites to connect with vCenter Server. The error No matching cipher suite is shown on the server side, and the handshake fails on the vSphere Client or vSphere PowerCLI side.

    Workaround: Take one of the following actions.

    For Windows Server 2003 or 64-bit Windows XP, apply the appropriate Microsoft hotfix for your platform:

    For Windows XP 32 bit, Windows XP 64 bit, or Windows Server 2003, take one of the following actions.

    • Before you install the vSphere Client or vSphere PowerCLI on the host machine, upgrade the Windows operating system to Windows Vista or later.
    • On the vCenter Server host machine, reduce the implied security by allowing the server to communicate using weak cipher suites. To do this, include the following section in the vCenter Server vpxd.cfg file:
      <config>
          ...
          <vmacore>
              ...
              <ssl>
                  ...
                  <cipherList>ALL</cipherList>
              ...
              </ssl>
          ...
          </vmacore>
      ...
      </config>
  • Networking is lost after you upgrade the vCenter Server Appliance, if the existing vCenter Server Appliance has a static IP configuration and the existing vCenter Server Appliance and the upgraded vCenter Server Appliance are in different subnets
    Networking is lost after you upgrade a vCenter Server Appliance configured with both of the following conditions:

    • The existing vCenter Server Appliance has a static IP configuration.
    • The existing vCenter Server Appliance and the upgraded vCenter Server Appliance are in different subnets.

    Workaround: To restore networking:

    1. Log in to the vCenter Server Appliance through the virtual machine console.
    2. Run /opt/vmware/share/vami/vami_config_net to reconfigure networking.
  • Attempts to upgrade the vSphere Web Client to version 5.5 results in warning message: Error: 29108
    During the upgrade of the vSphere Web Client to version 5.5, the following warning message is displayed: Error: 29108. The unregistration of the service or Solution user failed.. This error occurs because the installer is unable to remove the application user programmatically.

    Workaround:

    1. Record the exact vSphere Web Client solution user named in the warning message.
    2. Click OK to dismiss the warning message and complete the upgrade to version 5.5 of the vSphere Web Client.
    3. Log in to the vSphere Web Client as the Single Sign-On administrator
    4. In Administration, under Single Sign-On, click Users and Groups, and click the Application Users tab.
    5. To remove the solution the application user named in the warning message, select the row for that user and click Delete.

  • The vSphere Web Client service does not start after upgrade of the vCenter Server Appliance
    When you upgrade the vCenter Server appliance from version 5.0 or 5.1 to version 5.5, the vSphere Web Client service does not start and the following messages appear in the Virgo Server log:
    [ERROR] startup-tracker org.eclipse.virgo.medic.eventlog.default KE0004E Kernel failed to start within 300 seconds.
    [INFO ] startup-tracker org.eclipse.virgo.medic.eventlog.default KE0011I Immediate shutdown initiated.

    Workaround: Start the vSphere Web Client service by using the vCenter Server Appliance management interface.

vCenter Single Sign-On Issues

  • Attempts to install vCenter Single Sign-On 5.5 fails if the password for administrator@vsphere.local contains non-ASCII, high-ASCII, or special characters such as semicolon (;), double quotation mark ("), circumflex (^), and backslash (\)*
    If you use non-ASCII, high-ASCII or special characters such as semicolon (;), double quotation mark ("), circumflex (^), and backslash (\) in the password you set for the vCenter Single Sign-On administrator account, vCenter Single Sign-On installation fails. This issue occurs when you attempt to install vCenter Single Sign-On either using the installer, or when you run a silent installation.

    Workaround: Do not use non-ASCII, high-ASCII and special characters such as semicolon (;), double quotation mark ("), circumflex (^), and backslash (\) in passwords.

  • vdcadmintool might generate password for vCenter Single Sign-On 5.5 with unsupported characters *
    If you use the vdcadmintool utility available at ...\VMware\Infrastructure\VMware\CIS\vmdird\vdcadmintool.exe to generate passwords, and if the password generated by the utility has invalid or unsupported characters such as semicolon (;), double quotation mark ("), circumflex (^), backslash (\)double quotation mark or high-ASCII, the next time you attempt to upgrade vCenter Single Sign-On, the upgrade might fail.

    Workaround: If you have used the vdcadmintool utility to generate password for administrator@vsphere.local, change the password for the user by using the vSphere Web Client.
  • Updated Error after switchover/failover on systems upgraded from vSphere 5.1U1a to vSphere 5.5 that use vCenter Heartbeat
    An environment starts with the following configuration: vCenter Server 5.1U1a with vCenter Single Sign-On, Inventory Service and the vSphere Web Client, plus vCenter Heartbeat 6.5U1. You upgrade to vCenter Server 5.5, and upgrade vCenter Single Sign-On, Inventory Service and the vSphere Web Client at the same time. You upgrade vCenter Heartbeat to version 6.6.
    All the VMware components and services start successfully on the primary/active node. If the primary node goes down and you activate the secondary node, the following error appears in the vpxd log when the vCenter Server service starts on the secondary/active node:
    Unable to create SSO facade: Invalid response code: 404 Not Found.. The vpxd service does not start on the secondary node.

    Workaround: If you install the new versions of vCenter Server and vCenter Heartbeat instead of performing an upgrade, the second node starts up as expected.
    If Single Sign-On must be upgraded rather that a fresh install on a different virtual machine, follow the procedures listed in KB 2059820.

  • Error 29107 appears during vSphere Web Client upgrade from 5.1U1a to 5.5
    During an upgrade of a vSphere Web Client from version 5.1 Update U1a to version 5.5, Error 29107 appears if the vCenter Single Sign-On service that was in use before the upgrade is configured as High Availability Single Sign-On.

    Workaround: Perform the upgrade again. You can run the installer and select Custom Install to upgrade only the vSphere Web Client.

  • If Active Directory services and vCenter services are in different locations, a login by a user who belongs to over 500 groups might take a long time
    Your environment uses an Active Directory setup. This setup is in a different location from vCenter Server and its services. As a result, when a user who belongs to over 500 Active Directory groups logs in with the vSphere Web Client, login might take 10-20 minutes. With the vSphere Client, login for that user might time out.

    Workaround: Change your setup so the Active Directory services and the vCenter Server system are in the same location, or log in as a user who does not belong to so many Active Directory groups.

  • Auto-discovery of Active Directory settings no longer supported with vCenter Single Sign-On 5.5
    The vSphere 5.1 vCenter Single Sign-On version included an autodiscovery feature. That feature was removed from the vSphere 5.5 vCenter Single Sign-On service.

    Workaround: Log in to vCenter Single Sign-On from the vSphere Web Client as a user with vCenter Single Sign-On administrator privileges and add the identity source manually. By default, administrator@vsphere.local has vCenter Single Sign-On administrator privileges.

  • After upgrade, domain administrators, who are part of the local administrators group, cannot log in to vCenter Server
    In your vSphere 5.1 environment, you gave permissions to the local administrators group, which implicitly includes the domain administrator group. You can log in to vCenter Server 5.1 as a member of the domain administrator group. However, when you upgrade to vSphere 5.5, the domain administrator users no longer have the permissions to log in to vCenter Server. Permissions for local users are maintained after the upgrade.

    Workaround: The simplest solution is to log in to vCenter Server as administrator@vsphere.local and to assign permissions directly to the domain administrators group. If other local users who were not inside a subdomain had permissions to manage to vCenter Server users before the upgrade, those users can also log in to vCenter Server and assign permissions to the domain administrators group or any other group.

  • vCenter Single Sign-On installation fails on Windows Server 2008 SP1
    When you attempt to install vCenter Single Sign-On on Windows 2008 SP1 (64 bit), the following warning appears:
    This application is only supported on windows server 2008 64bit, or higher. Make sure windows is not running as domain controller.
    Installation does not complete.

    Workaround: None. Install vCenter Single Sign-On on a Windows 2008 SP2 (64 bit) or higher system.

  • No error occurs when you replace the certificate for a service with a certificate already in use by a different service
    If you are using the Certificate Automation Tool to replace certificates, and you respond to the prompts by replacing an existing certificate with a certificate that is already in use by a different service, the tool does not display an error message. The tool proceeds with the replacement. Because each service must have a unique certificate in the vCenter installation on Windows, authentication does not work properly.

    Workaround: None. Keep track of the certificates that you are using for the different services.

  • Login with vCenter Single Sign-On might require inclusion of domain name
    In vSphere 5.5, vCenter Single Sign-On no longer supports multiple default domains. This might cause problems for users who attempt to log in to a vCenter Server system that is installed on Windows, or for users who log in to the vCenter Server Appliance.

    Workaround: Include the domain prefix with the user name when you log in to a nondefault domain. For example, the user root on the local operating system can log in as localos\root. The user user1 in the domain DOMAIN1 can log in as DOMAIN1\user1.
    This behavior is not considered a bug, but included in the release notes for completeness.

  • vCenter Single Sign-On installation fails if the destination folder includes non-ASCII or high ASCII characters
    If you change the destination folder for vCenter Single Sign-On during installation, and if the new destination folder that you select includes non-ASCII or high ASCII characters, no warning appears but installation fails.

    Workaround: Select destination folders that contain ASCII characters. Special characters are not allowed and generate the error listed in the next known issue.

  • vCenter Single Sign-On fails if the installation folder includes special characters
    If you attempt to install vCenter Single Sign-On in a custom location, and the destination folder name includes characters such as percent (%) or ampersand (&), the installation fails. An error message similar to the following appears:
    Error 20020. Failed to update values in server.xml file

    Workaround: None. See the vSphere Installation and Setup documentation for a complete list of disallowed characters.

  • Warning during vCenter Single Sign-On installation on virtual machine with multiple network interfaces
    You install vCenter Single Sign-On in an environment with multiple network interfaces. One or more of the network interfaces in the environment cannot be resolved with DNS. When the vCenter Single Sign-On installer performs the prerequisite check, a warning that is similar to the following appears:

    DNS resolved IP(<ip_address_1>) does not match the machine reported IP(<ip_address_2>). Certificates will use the machine ip instead of FQDN. It is recommended that you have a static IP address for this to work correctly.

    Workaround: If both the forward DNS lookup and the reverse DNS lookup for the primary interface are correct, you can ignore the warning and proceed with the installation.

Networking Issues
  • The vSphere Web Client lets you configure more virtual functions than are supported by the physical NIC and does not display an error message
    In the SR-IOV settings of a physical adapter, you can configure more virtual functions than are supported by the adapter. For example, you can configure 100 virtual functions on a NIC that supports only 23, and no error message appears. A message prompts you to reboot the host so that the SR-IOV settings are applied. After the host reboots, the NIC is configured with as many virtual functions as the adapter supports, or 23 in this example. The message that prompts you to reboot the host persists when it should not appear.

    Workaround: None

  • Attempts to name a Link Aggregation Group (LAG) port by using surrogate pair characters fails
    In the vSphere Web Client, if you try to rename a LAG port and the new name contains surrogate pair characters, the following error message appears: The port name is not valid. Specify a valid port name. Surrogate pair is a pair of 16-bit values that UTF-16 uses to represent characters that require more than 16 bits.

    Workaround: Do not use surrogate pair characters when you name LAG ports.

  • When you try to deploy a virtual machine on a vSphere Distributed Switch, the error message no free port is available in distributed_switch_name might appear although the switch has free ports
    When you try to deploy a virtual machine on a vSphere Distributed Switch, the error message no free port is available in distributed_switch_name might appear although the switch has many free ports. vCenter Server handles race conditions incorrectly when reserving and deleting distributed ports. This issue causes vCenter Server to decide that no ports of the distributed switch are available if the first available port is being deleted but is not deleted yet. For example, vCenter Server deletes a port when a host disconnects or enters maintenance mode, or when a virtual machine is reconfigured.

    Workaround: Wait for several minutes and redeploy the virtual machine. This time the race condition might not occur.

Storage Issues
  • Storage profiles without storage capabilities might be missing after you upgrade vCenter Server to version 5.5
    After you upgrade to vCenter Server 5.5, storage profiles that you created with an earlier version of vCenter Server are not visible in the vSphere Web Client. This problem affects only storage profiles that do not have any storage capabilities attached.

    Workaround: Before you perform an upgrade, attach storage capabilities to the storage profiles that need to be available in vCenter Server 5.5. After the upgrade, the existing storage capabilities are converted into tags in the Legacy User Label category, and the storage profiles are converted into storage policies referencing these tags.

  • Renamed tags appear as missing in the Edit VM Storage Policy wizard
    A virtual machine storage policy can include rules based on datastore tags. If you rename a tag, the storage policy that references this tag does not automatically update the tag and shows it as missing.

    Workaround: Remove the tag marked as missing from the virtual machine storage policy and then add the renamed tag. Reapply the storage policy to all out-of-date entities.

  • A virtual machine cannot be powered on when the Flash Read Cache block size is set to 16KB, 256KB, 512KB, or 1024KB
    A virtual machine configured with Flash Read Cache and a block size of 16KB, 256KB, 512KB, or 1024KB cannot be powered on. Flash Read Cache supports a minimum cache size of 4MB and maximum of 200GB, and a minimum block size of 4KB and maximum block size of 1MB. When you power on a virtual machine, the operation fails and the following messages appear:

    An error was received from the ESX host while powering on VM.

    Failed to start the virtual machine.

    Module DiskEarly power on failed.

    Failed to configure disk scsi0:0.

    The virtual machine cannot be powered on with an unconfigured disk. vFlash cache cannot be attached: msg.vflashcache.error.VFC_FAILURE

    Workaround: Configure virtual machine Flash Read Cache size and block size.

    1. Right-click the virtual machine and select Edit Settings.
    2. On the Virtual Hardware tab, expand Hard disk to view the disk options.
    3. Click Advanced next to the Virtual Flash Read Cache field.
    4. Increase the cache size reservation or decrease the block size.
    5. Click OK to save your changes.
  • A custom extension of a saved resource pool tree file cannot be loaded in the vSphere Web Client
    A DRS error message appears on host summary page.

    When you disable DRS in the vSphere Web Client, you are prompted to save the resource pool structure so that it can be reloaded in the future. The default extension of this file is .snapshot, but you can select a different extension for this file. If the file has a custom extension, it appears as disabled when you try to load it. This behavior is observed only on OS X.

    Workaround: Change the extension to .snapshot to load it in the vSphere Web Client on OS X.

  • DRS error message appears on the host summary page
    The following DRS error message appears on the host summary page:

    Unable to apply DRS resource settings on host. The operation is not allowed in the current state. This can significantly reduce the effectiveness of DRS.

    In some configurations a race condition might result in the creation of an error message in the log that is not meaningful or actionable. This error might occur if a virtual machine is unregistered at the same time that DRS resource settings are applied.

    Workaround: Ignore this error message.

  • Cannot power on or enlarge the cache reservation of virtual machines that have a virtual Flash Read Cache reservation
    When a virtual machine that has a virtual Flash Read Cache reservation is powered on, the host it resides on uses normal RAM memory to manage the flash reservation. If insufficient memory is available, the virtual machine cannot power on. If the virtual machine is running and you enlarge the Flash Read Cache reservation, the operation fails with a runtime error because the cache cannot be attached.

    Workaround: Move the virtual machine to another host or reduce the memory requirements of Flash Read Cache by configuring a larger Flash Read Cache block size for the affected virtual machine or for another virtual machine running on the same host. You can also reduce the Flash Read Cache reservation of one or more of the virtual machines that reside on the host. After you make these changes, try again to power on or reconfigure the virtual machine. Follow the Flash Read Cache configuration recommendations in the vSphere Storage documentation to minimize the possibility of such errors.

vCenter Server and vSphere Web Client Issues
  • Attempts to disable IPv4 from DHCP to None in the Web console of a VMware vCenter Server Appliance that has IPv4 and IPv6 enabled fails with the error message Failed to set network settings
    By default, both IPv4 and IPv6 are enabled on the default virtual network adapter of the vCenter Server Appliance. To disable IPv4 and use only IPv6, you log in to the Web Console at https://vCenter_Server_Appliance_IP_address:5480, click Network and on the Address tab for the default network adapter change the value of IPv4 Address Type from DHCP to None. When you try to save the changes, the error message Failed to set network settings appears.

    Workaround: Set IPv4 Address Type to Static and then change it to None.

    1. On the Address tab for the default network adapter change the value of IPv4 Address Type from DHCP to Static and save the changes.
    2. Change the value of IPv4 Address Type from Static to None and save the changes.

  • VMware vCenter Server Appliance database disk usage
    vCenter Server Appliance with the vPostgres embedded database might run out of disk space for the disk partition. This might be caused by large or dynamic inventory retention settings. In most situations, vPostgres disk space is filled by historical data kept for statistics, events, and tasks collected by vCenter Server.

    Workaround: Change the vCenter Server data retention settings. Instructions can be found in the vSphere documentation:

    • For statistics, see "Configuring Statistics Settings in the vSphere Web Client" in vCenter Server and Host Management.
    • For events and tasks, see "Configuring vCenter Server in the vSphere Web Client" in vCenter Server and Host Management.

    You can also monitor the disk usage of the vPostgres disk. See the Knowledge Base article Monitor vCenter Server Appliance database disk usage for instructions.

  • Updated VMware vCenter Server Appliance 5.5 root account locked out after password expires
    By default, the password of the local root account in VMware vCenter Server Appliance expires 90 days after the appliance is first powered on. If the password is allowed to expire, the account will be deactivated and inaccessible.

    Workaround: See the VMware Knowledge Base article 2069041 forinstructions on preventing the deactivation and unlocking a root account whose password expired.

  • vCenter Server Appliance large scale deployment requirements
    For vCenter Server Appliance to manage large scale deployments, you must connect to a remote database and modify the virtual machine settings. See Configure Inventory Size for the VMware vCenter Server Appliance in vCenter Server and Host Management for information about memory and sizing options.

    Workaround:

    1. Ensure that virtual machines are configured with a minimum memory and CPU requirements.
      For information about virtual machine configuration, see Configuring Virtual Machines in vSphere Virtual Machine Administration. See Configure Inventory Size for the VMware vCenter Server Appliance in vCenter Server and Host Management for information about memory options.
    2. Log into the vCenter Server Appliance administration interface at https://IP address or FQDN of vCenter Server Appliance:5480 and navigate to Services. In the Inventory Size drop-down menu, select large and click Save Settings.
    3. If you are using the embedded database with your vCenter Server Appliance, increase the disk space to at least 120GB by following the steps outlined in Increase the disk space in vCenter Server Appliance.

    Monitor the vCenter Server Appliance database disk usage regularly as described in Monitor vCenter Server Appliance database disk usage.

  • The Client Integration Plug-in for the vSphere Web Client 5.5 is supported only on Mac OS 10.7 and later
    The Client Integration Plug-in for the vSphere Web Client 5.5 is supported only on Mac OS 10.7 and later. On Mac OS 10.6.x or earlier, either the Client Support Plug-in does not register properly in the browser, or the OVF Tool displays runtime errors during OVF and OVA uploads or downloads.

    Workaround: Upgrade the Mac OS to 10.7 or 10.8.

  • Default folder names generated by the vCenter Server Appliance do not reflect the browser's language setting
    When you access the vCenter Server Appliance using the vSphere Web Client, default folder names generated by the server, such as Discovered Virtual Machines, do not reflect the browser's language setting.

    Workaround: Edit the vpxd locale setting:

    1. Select the vCenter Server instance in the vSphere Web Client inventory.
    2. Click the Manage tab.
    3. Click Advanced Settings.
    4. Click Edit.
    5. In the vpxd.locale text box, type the locale code.

      Valid options include de, en, fr, ja, ko, and zh_CN.

    6. Click OK.
    7. Restart vCenter Server:
      1. Log in to the vCenter Server Appliance configuration interface at https://hostname:5480.
      2. On the vCenter Server tab, select Summary.
      3. Click Stop vCenter.
      4. Click Start vCenter.

  • Attempts to log in using the vSphere Client to vCenter Server fail with an error stating that an unknown connection error occurred
    Attempts to log in using the vSphere Client installed on Windows XP or Windows Server 2003 to a vCenter Sever fail with the following error: An unknown connection error occurred. (The Client could not send a complete request to the server. (The underlying connection was closed: An unexpected error occurred on a send.)). The error is caused by the lack of support for some SSL ciphers on Windows XP and Windows Server 2003.

    Workaround: For Windows Server 2003 or 64-bit Windows XP, apply the appropriate hotfix from http://support.microsoft.com/kb/948963.

    No hotfix is available for Windows XP (32 bit). Microsoft provides limited support for Windows XP, and the hotfix has not been released for it. You must upgrade your host operating system to Windows Vista or later, which supports the use of high cipher strengths.

  • You cannot view the Solutions tab of the EAM Sample Solution in Internet Explorer
    When you click the Solutions tab of the EAM Sample Solution in the vSphere Web Client, an error message might appear: Navigation to the webpage was canceled.

    Workaround: View the Solutions tab of the EAM Sample Solution in another browser, such as Mozilla Firefox or Google Chrome.
    Alternatively, install the EAM Sample Solution SSL certificate in Internet Explorer.

    1. In Internet Explorer, navigate to the EAM Sample Solution management page at the address that you specify while setting up the EAM Sample Solution.
      The default URL is http://<IP_adress_of_machine_where_you_install_the_solution>:8080/eam-sample.
    2. When the page loads, accept the certificate security warning.
    3. Install the EAM Sample Solution certificate by clicking the certificate error icon in the Internet Explorer address bar.
    4. Restart Internet Explorer and open the vSphere Web Client.

  • vCenter Server Appliance checks user permissions based on case-insensitive user name matching
    In previous vSphere releases, the vCenter Server Appliance used case-sensitive matching for user names when checking user permissions. In the vSphere 5.5 release, the vCenter Server Appliance uses case-insensitive matching for user names when checking permissions. This means that two users whose user names differ only in case (for example, User1 and user1) are treated as the same user when vCenter Server checks permissions.

    Workaround: If your vCenter Server Appliance has users whose names differ only in case, rename at least one of the users, and reassign permissions to the renamed users.

  • Error message appears and no vCenter Server instances are available in the vSphere Web Client inventory after you log in
    You might encounter this problem when the vCenter Server instance is managing an inventory that is too large and operating under a heavy load.

    Workaround: Log out and log in to the vSphere Web Client. If this does not resolve the problem, verify that your vSphere environment is running within the recommended configuration maximums.

Virtual Machine Management Issues
  • Virtual machine guest OS does not detect Control key sent from HTML 5 console in Chrome
    When you attempt to sent a Control command to a virtual machine from an HTML 5 console in Chrome, the guest operating system does not react.

    Use an HTML 5 console in Firefox, or use the virtual machine console in the vSphere Web Client.

  • Virtual Machines report USB connection errors when connecting to USB devices attached to a Mac OS X client computer
    When you connect USB devices to virtual machines from a Mac OS X client computer, you see an Error connecting device message in the following cases:

    • You connect more than one USB device or hub to a virtual machine from a Mac OS X client computer.
    • You add a USB device when multiple devices are incorrectly listed as available to connect to the USB controller on the virtual machine, but the devices are already in use by another virtual machine or by the client computer.

    Workaround: Ensure that another virtual machine or client computer is not using the USB device, and connect only one USB device or hub from a Mac OS X client computer to a virtual machine.

Migration Issues
  • Virtual machine drag and drop is not supported across hosts
    You use the vSphere Web Client and attempt to drag and drop a virtual machine from one host to another. A red X indicates that drag and drop is not supported.

    Workaround: Use the Migrate VM action or right-click the virtual machine and select Move to to start the migration wizard.

  • Changing datastores through migration is not allowed if the number of virtual disks is greater than 64
    Storage vMotion and vMotion without shared storage support migration of a virtual machine with up to 64 virtual disks. If the number of virtual disks to be moved is greater than 64, the migration operation is not allowed.
    However, if you use Storage vMotion to selectively move less than 64 disks or to move only the home directory of the virtual machine, the operation succeeds even for the virtual machine with the maximum supported number of virtual disks.

    Workaround:

    • For Storage vMotion, perform multiple migrations, each with up to 64 disks. Use the Advanced option on the Migrate virtual machine wizard to select disks to migrate and to specify the datastore location.
    • For vMotion without shared storage, power off the virtual machine to perform migration.

  • A successful Storage vMotion operation in a vSphere HA cluster might result in an orphaned virtual machine
    After you migrate a virtual machine with Storage vMotion in a vSphere HA cluster, an orphaned virtual machine with the same name might remain in the vCenter Server inventory. This error can occur if vSphere HA attempts to restart the virtual machine that is being migrated, before the Storage vMotion workflow finishes. The attempt can be triggered in situations such as the following:

    • The master host detects a possible failure impacting the virtual machine, such as a network interruption.
    • In an environment without Virtual SAN, the master hosts regains access to the virtual machine datastore.
    • In an environment with Virtual SAN, the master host detects a change in Virtual SAN object accessibility. For example, the host has recently rejoined the Virtual SAN network after a network partition.

    Workaround: Delete the orphaned virtual machine.

VMware HA and Fault Tolerance Issues
  • When you enable admission control for a vSphere HA cluster, an error message is shown
    When you enable admission control on a vSphere HA cluster with powered-on virtual machines, the following error message appears: An internal error has occured - Unknown property: '-1.

    Workaround: The message has no functional impact, but you must reload the client to continue.

  • vSphere HA might fail to restart a virtual machine with a vSphere Flash Read Cache reservation
    When a virtual machine with a vSphere Flash Read Cache reservation is powered on, the host it resides on uses some normal (RAM) memory to manage this flash reservation. If sufficient memory is not available, then the virtual machine power on fails. vSphere HA retries such failed power on operations but only four more times. If the fifth power on attempt fails, vSphere HA issues an event reporting that the maximum number of restart attempts has been reached.
    Note: To list the vSphere HA issued events, you can search the event history for the phrase "vSphere HA".

    Workaround: If vSphere HA fails to restart a virtual machine and you observe a vSphere HA event reporting that the maximum number of attempts have been made to restart it, attempt to power on the virtual machine manually on one of the hosts. If the power on operation fails and a reason is given, address that issue.

    However, if this power on task fails for an unexplained reason or if the task error stack reports that the vSphere Flash Read Cache cannot be attached, either try another host or reduce the memory needs of the vSphere Flash Read Cache and try again. You can do this by either

    • configuring a larger vSphere Flash Read Cache block size for the virtual machine or another virtual machine running on the same host, or
    • significantly reducing the vSphere Flash Read Cache reservation of one or more of these virtual machines.

    If you follow the vSphere Flash Read Cache configuration recommendations documented in the vSphere Storage guide and the vSphere 5.5 Beta Release Notes, you can minimize the possibility of encountering this type of error.

  • vSphere HA does not reattempt the placement of virtual machines that failed due to anti-affinity constraints, after changes are made to the vm-vm anti-affinity rule
    If vSphere HA fails to restart a virtual machine due to an anti-affinity constraint, no re-attempt is made if you change the vm-vm anti-affinity rule or remove it.

    Workaround: The vSphere HA master host reattempts placing a virtual machine waiting for resources after the unreserved capacity in the cluster is increased. To increase this capacity, power off a virtual machine, migrate it to another cluster using vMotion, then

    • bring back on-line a failed host, or
    • add another host to the cluster, or
    • reduce the resources reserved by any of the powered-on virtual machines.

  • Under certain conditions, a virtual machine does not reset despite the appState being appStateNeedReset
    A virtual machine is not reset if the needReset appstate is issued using the Application Monitoring GuestSDK when the virtual machine is on a standalone host and the host is moved to a cluster which has VM and App Monitoring enabled. This could also occur if the FDM process restarts on the host while the needReset request is pending. For example this error can occur when reconfiguring vSphere HA or if the service crashes after a needReset state has been issued for a virtual machine using the Application Monitoring GuestSDK.

    Workaround: Trigger a blank Reconfigure cluster task for the vSphere HA cluster containing the hosts. The virtual machine's needReset state is picked up by the FDM on the host, which resets the virtual machine. In the vSphere Web Client go to the Edit Cluster Settings panel and click Edit. Press OK on the Cluster Settings panel without changing anything on the cluster. This triggers a blank Reconfigure cluster task.

Miscellaneous Issues
  • Error messages appear when you attempt to log in to the vSphere Web Client by using Google Chrome on Mac OS X 10.7.x in certain language and format locales
    You encounter Error 2007 and Error 1009 and cannot log in when you use Google Chrome 23 running on Mac OS X 10.7.x. The problem is present if the operating system language and format are set to French, German, Japanese, Korean, or Russian. For the problem to appear, Google Chrome must be installed before switching the operating system locale and the browser must use Flash Player 11.5.31.5 or 11.5.31.139.

    Workaround: Perform one of the following tasks:

    • Change the Flash Player version to 11.5.502.136 or 11.5.31.137.
    • Switch to English locale and restart the browser.
    • Switch to English locale, uninstall Chrome, switch back to the locale of choice, and reinstall Chrome.

  • You cannot access the vSphere Web Client by using some Firefox versions with certain operating systems in an IPv6 network environment
    In the Windows and Linux versions of Firefox 18.0.2, you cannot access URLs in an IPv6 environment. On some supported Linux distribution, such as SLES/SLED 11, you cannot use the bundled Firefox 10.x browser, because the browser does not accept SSL certificates for IPv6 addresses. For information about this third-party issue, see Mozilla bug 633001.

    Workaround: Use other supported browsers such as Google Chrome or Internet Explorer.

  • The vSphere Web Client displays error messages in zh, zh-hans, and zh-hant locales
    If the browser locale has been set to Simplified Chinese or Traditional Chinese, the vSphere Web Client might display errors when you perform some operations, such as managing objects, licensing, and datacenter creation. In the Recent Tasks pane, the following message might appear: Unable to create the managed object for <string>. Additional error messages appear as notifications. The problem occurs in Internet Explorer, Google Chrome, and Mozilla Firefox.

    Workaround: Change the browser locale and restart the browser.

  • The VMware vSphere Web Client service does not start on Turkish versions of Windows Server 2008 or Windows Server 2012
    When you install the server component of the vSphere Web Client on a Turkish version of Windows Server 2008 or Windows Server 2012, the service does not start after the installation finishes.

    Workaround: Install the vSphere Web Client on a version of Windows Server 2008 or Windows Server 2012 that is in another language.