Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 7/17/2020Categories: InformationalTotal Views: 16087Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

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.

Purpose

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

Resolution

vCenter Server 4.x

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

vCenter Server 4.1 fails to install or upgrade with the error: This installation package is not supported by this processor type (1019144)

Installing vCenter Server using the MS SQL Express database option fails with Error 25060 (1020780)

vCenter Server installation fails with ODBC and DNS errors (1003928)

Installing vCenter Server 4.x does not complete with Windows Server 2008 (1013822)

Installing or upgrading to vCenter Server 4.1 fails on a non-US English MSSQL with the error: ODBC error 22007 (1024737)

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

vCenter Server 4.1 Data Migration Tool fails with the error: HResult 0x2, Level 16, State 1 (1024490)

Using the Data Migration Tool to upgrade from vCenter Server 4.0 to vCenter Server 4.1 fails (1024380)

ESX/ESXi 4.0 Update 1, 4.0 Update 2 and 4.1 fail with a purple diagnostic screen on AMD Opteron 6100-series processor based systems (1030509)

Upgrading to vCenter Server 4.1 or later fails when the installer upgrades the database (1024449)

Upgrading vCenter Server 4.0 to 4.1 fails with the error: Exception Thrown while executing SQL script (1025139)

Unable to start the VMware VirtualCenter Management Webservices after upgrading to vCenter Server 4.x or later (1011648)

Plugins, extensions, and applications experience errors after upgrading to vCenter Server 4.0 from VirtualCenter 2.5.x (1018203)

Search function does not work after upgrading to vCenter Server 4.1 (1026092)

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:

vSphere 4.1 upgrade pre-installation requirements and considerations (1022137)

Migrating an existing vCenter Server database to 4.1 using the Data Migration Tool (1021635)

Upgrading ESX 4.0 to ESX 4.1 (1022140)

Installing ESX 4.1 and vCenter Server 4.1 best practices (1022101)

Upgrading to ESX 4.1 and vCenter Server 4.1 best practices (1022104)

Upgrading vCenter Server, Update Manager, and ESX/ESXi to vSphere 4.1 Update 1 (1034497)

vCenter Server 2.5.x

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

Administrative Credentials Are Required for Oracle and SQL Database When Installing or Upgrading VirtualCenter (1003052)

Installing Microsoft SQL Server Express Edition, when Microsoft SQL Native Client Driver already exists, fails (1003076)

VirtualCenter Server Installation Fails or Results in Error if Your System Does Not Have MDAC 2.8 SP1 or Later Installer (1003160)

Error Message During Installation: error 1603: error installing Windows installer engine (1003036)

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.

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

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:

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

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.

Related 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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
在 ESX 上启用 syslog (1005030)

KB
•
vCenter Server 上にフォルダが見つからないため VirtualCenter Server サービスが起動しない (1005882)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware VirtualCenter 2.0.x

VMware VirtualCenter 1.4.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant