Support > Knowledge Base
Knowledge Base

Search the Knowledge Base: |
Search the Knowledge Base: |
Troubleshooting VirtualCenter Database Configuration Issues
Symptoms
-
VirtualCenter installation fails
-
VirtualCenter displays installation errors before completion
-
VirtualCenter displays upgrade errors before completion
-
VirtualCenter upgrade fails to complete
-
You see one of these errors:
-
Error 25003.Setup Failed to create the VirtualCenter 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.
-
Resolution
A VirtualCenter installation may fail due to minor database configuration issues.
These are the most common errors:
-
Error 25003.Setup Failed to create the VirtualCenter repository.
You may see this error when installing VirtualCenter 2.0.x. Your VPXD 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. C ontact your Database Administrator (DBA) for assistance.
Note: If your database is remote, ensure that the Database client version matches the Database version.
-
Error: Sequence VPX_INVENTORY_SEQ is not defined on the database
Failed to initialize VMware VirtualCenter. Shutting down...
If you are installing a fresh installation VirtualCenter 2.0.2 and pointing to a database created by a previous VirtualCenter release, VirtualCenter may fail to start. For more information, see After Installing VirtualCenter 2.0.2, VirtualCenter may fail to start (1001680).
-
Error: Failed to execute command: drop procedure vpx_rollup_sample_group
If you try to upgrade from VirtualCenter 2.0.2 Build 50618 to VirtualCenter 2.5 Build 64201 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_group
The 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 VirtualCenter 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 VirtualCenter 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.
Feedback
Actions
- KB Article: 1003960
- Updated: Aug 14, 2009
- Products:
VMware VirtualCenter - Product Versions:
VMware VirtualCenter 1.4.x
VMware VirtualCenter 2.0.x
VMware VirtualCenter 2.5.x

