Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Troubleshooting vCenter Server database configuration issues
Symptoms
-
vCenter Server installation fails
-
vCenter Server displays installation errors before completion
-
vCenter Server displays upgrade errors before completion
-
vCenter Server upgrade fails to complete
- You see one of these errors:
- Error 25003.Setup Failed to create the vCenter Server repository.
-
Error: Sequence VPX_INVENTORY_SEQ is not defined on the database.
-
Error: Failed to execute command: drop procedure vpx_rollup_sample_group.
-
Error 25003.Setup Failed to create database tables.
-
Error 25036.VMware VirtualCenter Server could not be installed.
-
These errors occur if the regional setting is different from US or native English.
Purpose
Resolution
A vCenter Server installation may fail due to minor database configuration issues.
These are the most common errors:
-
Error 25003.Setup Failed to create the vCenter Server repository.
You may see this error when installing vCenter Server. Your vpxdlogs (located at C:\Documents and Settings\All Users\Application Data\VMware\VirtualCenter\logs) may show a message similar to:
"'App' 3868 error] "ODBC error: (42S02) - [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'vpx_entity'." is returned when executing SQL statement "create view VPXV_PERF_HOST_COUNTERS as
select distinct s.ENTITY_ID as HOSTID, s.STAT_ID as COUNTERID,
s.DEVICE_ID as NAME, null as INSTANCE,
d.NAME as DESCRIPTION
from VPX_HIST_STAT s, vpx_entity e, vpx_stat_def d
where s.ENTITY_ID = e.ID
and e.TYPE_ID = 1
and d.ID = s.STAT_ID"To resolve this error, ensure that your database is installed in Case Insensitive mode. Contact your Database Administrator (DBA) for assistance.
Note: If your database is remote, ensure that the Database client version matches the Database version.
You also may encounter this error in vCenter Server 4.x if you are using SQL 2000 compatibility mode. vCenter Server 4.x is not compatible with SQL 2000. When using vCenter Server 4.x, the database must be set to SQL 2005 or later. You can change this setting using Properties within SQL Management Studio. Engage your DBA for assistance in changing this parameter.
-
Error: Sequence VPX_INVENTORY_SEQ is not defined on the database
Failed to initialize VMware vCenter Server. Shutting down...
If you are installing a fresh installation vCenter Server and pointing to a database created by a previous vCenter Server release, vCenter Server may fail to start. For more information, see After Installing vCenter Server 2.0.2, vCenter Server may fail to start (1001680).
-
Error: Failed to execute command: drop procedure vpx_rollup_sample_group
If you try to upgrade from vCenter Server 2.x to vCenter Server 2.5.x with a SQL 2005 remote database, the upgrade fails. You see the error:
Error: Failed to execute SQL procedure. Got exception: ERROR [42S02] [Microsoft][SQL Native Client][SQL Server]Cannot drop the procedure 'vpx_rollup_sample_group', because it does not exist or you do not have permission.
Error: Failed to execute command: drop procedure vpx_rollup_sample_groupThe Upgrade wizard looks for the stored procedure vpx_rollup_sample_group. Because the stored procedure does not exist, the upgrade fails. To resolve this error, create two dummy stored procedures in SQL Enterprise Manager.
To create a dummy stored procedure:
- Right-click the stored procedure under vCenter Server Database.
- Click New Storage Procedure.
- Replace CREATE PROCEDURE [OWNER].[PROCEDURE NAME] AS with CREATE PROCEDURE dbo.vpx_rollup_sample_group AS .
- Right-click the stored procedure under vCenter Server Database.
- Click New Storage Procedure.
- Replace CREATE PROCEDURE [OWNER].[PROCEDURE NAME] AS with CREATE PROCEDURE dbo. vpx_stats_rollup AS.
- Retry the upgrade.\
- Error 25003.Setup Failed to create database tables
To resolve this error, check if the password length given for the ODBC/DSN connection for Update Manager is more than 32 characters. If it is, specify a shorter password length, then retry the installation.
Additional Information
These errors maybe encountered when trying to install with an Oracle Database. The issue can resolved by increasing the process limit in the Oracle Database to 200, which is an optimal setting for a medium sized environment.
Note: This issue may also be seen on non-US English localized installations. Ensure that the default ODBC language being used is English. For more information, see Installing or upgrading to vCenter Server 4.1 fails on a non-US English MSSQL with the error: ODBC error 22007 (1024737).
Tags
See Also
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
- KB Article:
- Updated:
- Categories:
- Product Family:
- Products:
- Product Versions:

