Known issues when installing or upgrading to vCenter Server 4.x and below
search cancel

Known issues when installing or upgrading to vCenter Server 4.x and below

book

Article ID: 320269

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

This article provides links to articles about known vCenter Server installation issues.

Symptoms:
  • vCenter Server installation may error before completion.
  • vCenter Server installation fails to complete.
  • Unable to complete vCenter Server installation.
  • vCenter Server Web Service fails to install.
  • Unable to connect to the vCenter Server remote database during the installation.
  • Cannot install VirtualCenter Server with MSDE as the database.
  • When upgrading the Oracle Database, an error message may indicate that database upgrade has failed.
  • Bulk-logged option for SQL Server database needs to be enabled before upgrading.
  • Database upgrade fails due to insufficient disk space.
  • When upgrading from VirtualCenter Server 1.x to 2.0.1, the database upgrades can fail if the 1.x system has both an MSDE database and a production database.
  • Administrative credentials are required for the Oracle and SQL database when installing or upgrading vCenter Server.
  • When you install Microsoft SQL Server Express Edition on a system where Microsoft SQL Native Client driver is present, the installation may fail with error.
  • VirtualCenter Server installation fails or results in error if your system does not have MDAC 2.8 SP1 or later installed.
  • Error message during installation: error 1603: error installing Windows installer engine.
  • For SQL Server 2000, do not grant or revoke the System Administrators role to satisfy the database permission requirements when upgrading to vCenter Server 2.5.
  • Upgrading VirtualCenter Server 1.4 using the unified installer with optional modules selected fails with an error.
  • vCenter Server database upgrade fails with an exception when a password that contains apostrophes or double quotes is used.
  • Upgrades of vCenter Server with Microsoft SQL Server 2005 database require the SQL Native Client ODBC driver.
  • vCenter Server install may fail with the following errors:
    • Error 25060. Setup failed to execute sqlcmd.exe
    • This installation package is not supported by this processor type. Contact your product vendor.
    • re-configure your DSN to use one of the supported drivers
    • An error occurred, please try again in another vSphere session.


Environment

VMware vCenter Server 4.0.x
VMware vCenter Server 4.1.x
VMware VirtualCenter 2.0.x
VMware VirtualCenter 2.5.x
VMware vCenter Server 5.0.x
VMware VirtualCenter 1.4.x

Resolution

vCenter Server 4.x

When installing vCenter Server 4.x, be aware of these issues:<?xml:namespace prefix = o />

    When upgrading to vCenter Server 4.x, be aware of these issues:

      These and other known issues can be found in the release notes . Read the release notes in full before attempting to install or upgrade to vCenter Server 4.x.
       
      In addition, see these articles for best practices:
         

        vCenter Server 2.5.x

        When installing vCenter 2.5.x, be aware of these issues:

          When upgrading to VirtualCenter 2.5, be aware of these issues:

            These and other known issues that can be found in the release notes . Read the release notes in full before attempting to install or upgrade to vCenter Server 2.5.x.

             
            VirtualCenter 2.0.x

            When installing VirtualCenter 2.0.x, be aware of these issues:

              When upgrading to VirtualCenter 2.0, be aware of these issues:

                • VirtualCenter Server 2.0.x uses TCP/IP Ports 80 and 443. Previous releases allow you to run VirtualCenter Server on the same machine as a web server using TCP/IP port 80 (http) and port 443. This configuration is no longer allowed because it causes a port conflict. VirtualCenter Server uses TCP/IP ports 80 and 443 for the Virtual Infrastructure Web Client.
                • VirtualCenter Server 2 cannot run on a GSX Server host.
                • VirtualCenter database must be upgraded. Instructions for updating the database can be found in the Install and Upgrade Guide.
                • Install MDAC 2.6 or Higher on Windows 2000 Server SP4. Download the latest version of MDAC from http://msdn.microsoft.com/data/ref/mdac/downloads/.
                These and other known issues can be found in the release notes . Read the release notes in full before attempting to install or upgrade to VirtualCenter 2.0.
                 
                When upgrading to VirtualCenter 2.0.1, be aware of these issues:

                  These and other known issues can be found in the release notes . Read the release notes in full before attempting to install or upgrade to VirtualCenter 2.0.1

                   
                  In addition, read the Installation and Upgrade guide before continuing to install or upgrade to VirtualCenter 2.0.1 or VirtualCenter 2.0.2.
                   

                  When installing or upgrading to VirtualCenter 2.0.2, be aware of these issues:

                  Note: These issues are described further in the release notes.

                    • Oracle Database Server Pre-installation Tasks
                      The schema used to manage the VirtualCenter objects must be able to use Oracle's DBMS_LOCK built-in package, which means it requires execute privileges on the package.
                    • Microsoft SQL Server Pre-installation Tasks
                      The primary database can not be used for a VirtualCenter 2.0.2 installation.
                    • Pre-Installation Tasks For Upgrading From VirtualCenter 1.x to 2.x
                      If you are upgrading a SQL database, you must first enable bulk logging in the database.
                    • Pre-Installation Tasks For Upgrade Using ISO Image or CD-ROM
                      If you are upgrading an existing VirtualCenter 2.0.1 instance using an ISO image or a CD-ROM disc, perform the instructions given in Please insert the Disk:1" Alert Dialog Box Appears when Upgrading VirtualCenter 2.0.x & VirtualCenter 2.5.x to the latest version (1001900                      ) before you run the upgrade installer.

                    Further notes on installing VirtualCenter 2.0.2 can be found in the release notes.

                    VirtualCenter 1.4.x

                    When installing VirtualCenter 1.4.x, be aware of these issues:

                      • VirtualCenter Web Service fails to install (2017)
                      • Because changes have been made to both the VirtualCenter Server and the VirtualCenter Client, you must upgrade all machines with either component. For example, VirtualCenter 1.3.x or lower version clients cannot connect to VirtualCenter 1.4.x servers and VirtualCenter 1.4.x clients cannot connect to VirtualCenter 1.3.x or lower version servers.
                      • Ensure that the Workstation service (lanmanworkstation) is up and running if you are unable to connect to the VirtualCenter remote database during the installation. Also, verify that the VirtualCenter database server is up and running and that it is connected to the network.

                      When upgrading to VirtualCenter 1.4.x, be aware of these issues:

                        • Always backup your database before you proceed with an upgrade process.
                        • Prior to upgrading ensure that the shared_pool_size parameter is set to no less than 100 MB if you are using an Oracle database. The shared_pool_size parameter is in the init.ora file. Have your Oracle database administrator check and set this parameter.
                        • Upgrading a large database may take a significant amount of time, from several minutes to more than an hour, depending upon the size of your database.

                        These and other known issues can be found in the release notes . Read the release notes in full before attempting to install or upgrade to VirtualCenter 1.4.x.


                        Additional Information

                        Minimum system requirements for installing VMware vCenter Server
                        vCenter Server installation fails with ODBC and DSN errors
                        Unable to start the VMware VirtualCenter Management Webservices after upgrading to vCenter Server 4.x or later
                        Installing vCenter Server does not complete with Windows Server 2008
                        Upgrading VMware vCenter Server MSSQL DB from version 4.x to 5.x fails with multiple errors
                        Upgrading to vCenter Server 5.x fails with the error: The DB user entered does not have the required permissions needed to install and configure vCenter Server with the selected DB.
                        Upgrading to vCenter Server 5.0 fails with the error: Could not connect to DataBase with specified JDBC URL
                        Installing VMware vCenter Server 5.0 fails with the error: Error 28023. Setup failed to setup VMwareVCMSDS directory service instance
                        Upgrading from vCenter Server 4.1 to 5.0 fails with the error: Could not write value Version to key "\SOFTWARE\VMware, Inc.\VMware Infrastructure\JRE"
                        Upgrade to vCenter Server 5.x fails with datastore error or insufficient memory problems
                        Port already in use when installing VMware vCenter Server

                        Powered by Wolken Software