Knowledge Base

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

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

• Always backup your database before you proceed with an upgrade process.
• For SQL Server 2000, Do Not Grant or Revoke the System Administrators Role to Satisfy the Database Permission Requirements When Upgrading to VirtualCenter 2.5 (1003346)
• Upgrading VirtualCenter 1.4 Using the Unified Installer with Optional Modules Selected Fails with an Error (1003078)
• VirtualCenter Database Upgrade Fails with an Exception When a Password that Contains Apostrophes or Double Quotes Is Use (1003049)
• Upgrades of VirtualCenter Server With Microsoft SQL Server 2005 Database Require SQL Native Client ODBC Driver (1003391)
• Permissions previously set in VirtualCenter may be lost after upgrading to VirtualCenter 2.5. These permissions need to be fixed manually.

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.

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

• Windows 2000 must be updated with Rollup 1 for Service Pack 4. Download this Rollup from http://www.microsoft.com/windows2000/server/evaluation/news/bulletins/rollup.mspx. Refer to http://support.microsoft.com/kb/816542/ for details. This fix is essential for VirtualCenter Server to operate correctly.
  This link is valid April 4/08. If you find the link is broke, provide feedback on the article and a VMware employee will update the link accordingly.
• Cannot install VirtualCenter Server with MSDE as the database (2153)

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/.

• When upgrading Oracle database an error message may indicate that the database upgrade failed (2040533)
• Bulk-Logged Option for SQL Server Database Needs to Be Enabled Before Upgrading (2603739)
• Database Upgrade Fails Due to Insufficient Disk Space (7434572)
• When Upgrading from VirtualCenter 1.x to 2.0.1, Database Upgrades Can Fail if the 1.x System Has Both an MSDE Database and a Production Database (3438229)

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

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 master 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.  

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.