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

My Subscriptions

Loading

Knowledge Base

VMware vCenter Service 4.x/5.x status reports the error: "Cannot store license usage in the vCenter Server database" (1029495)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 25983Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

VMware vCenter Service Status reports this error:

License accounting module health monitor Alarm
Message: "Cannot store license usage in the vCenter Server database"

Clicking Download report for a licensing report in the Licensing Reporting Manager, you see this error:

Cannot export license usage. License data integrity problem detected in the database

Cause

This issue may occur if there is missing data in the VPX_LIC_METADATA table due to an incomplete installation/upgrade process. For more information on an incomplete installation/upgrade process in a non-US English localized installation, see Installing or upgrading to vCenter Server 4.1 fails on a non-US English MSSQL with the error: ODBC error 22007 (1024737).

This issue occurs when you retry the upgrade after a failed upgrade/installation. Though the database upgrade fails the first time, it changes the vCenter Server version in the database. When you retry the database upgrade, vCenter Server incorrectly assumes that the database is up-to-date and fails to complete the upgrade process.

Impact / Risks

Caution: Before performing any database operations, take a complete backup of the database. VMware recommends that you consult a Database Administrator (DBA) before implementing any changes to the database configuration.

Resolution

To resolve this issue:

Important:

These steps should not be run on a vCenter Server 6.0 environment or a vCenter Server 5.5 environment connected to 6.0 Platform Service Controllers.

Before performing any database operations, take complete backup of the database. VMware recommends that you consult a Database Administrator (DBA) before implementing any changes to the database configuration.

Because the vCenter Server upgrade was not successful in the first attempt, there may be issues with other vCenter Server features (CIM-Hardware health status, SMS, query search).

Performing this procedure results in loss of licensing history data.

Verify that the user account being used to access the vCenter Server database has db_owner permissions.

For vCenter Server 5.x:

Stop the VMware VirtualCenter Management Webservices service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Ensure that the VPX_LIC_* tables are empty. If not, delete their contents.

To delete the contents from the VPX_LIC_* tables:

Launch SQL Management Studio (SQL Server) or SQL*Plus (Oracle).

Run these SQL statements:

DELETE FROM VPX_LIC_SNAPSHOT;
DELETE FROM VPX_LIC_SNAPSHOT_VC_GROUP;
DELETE FROM VPX_LIC_USAGE;
DELETE FROM VPX_LIC_CONTEXT;
DELETE FROM VPX_LIC_ASSET_PROPERTIES;
DELETE FROM VPX_LIC_ASSETS;
DELETE FROM VPX_LIC_LICENSES;
DELETE FROM VPX_LIC_VC_GROUP_MEMBERS;
DELETE FROM VPX_LIC_VC_GROUPS;
DELETE FROM VPX_LIC_METADATA;
DELETE FROM VPX_LIC_SETTINGS;

Note: For vCenter Server 5.5.x run these additional statements:

DELETE FROM VPX_LIC_TPS_ASSETS;
DELETE FROM VPX_LIC_AUTO_KEYS;
DELETE FROM VPX_LICENSE;

Run these INSERT statements to initialize the licensing metadata in the VPX_LIC_METADATA table:

For Microsoft SQL:

INSERT INTO VPX_LIC_METADATA (DATA_TYPE, LAST_SAMPLE_ID, LAST_SAMPLE_TIMESTAMP, RETAINED_SAMPLE_ID, RETAINED_SAMPLE_TIMESTAMP, GLOBAL_DIGEST, IS_STATE_VALID, WEEK_KEEP_COUNT)
VALUES('MAC', 0, CONVERT(datetime, '1900-12-31 00:00:00', 120), 0, CONVERT(datetime, '1900-12-31 00:00:00', 120), NULL, 1, -1);

INSERT INTO VPX_LIC_METADATA (DATA_TYPE, LAST_SAMPLE_ID, LAST_SAMPLE_TIMESTAMP, RETAINED_SAMPLE_ID, RETAINED_SAMPLE_TIMESTAMP, GLOBAL_DIGEST, IS_STATE_VALID, WEEK_KEEP_COUNT)
VALUES('UHD', 0, CONVERT(datetime, '1900-12-31 00:00:00', 120), 0, CONVERT(datetime, '1900-12-31 00:00:00', 120), NULL, 1, 208);

Note: For vCenter 5.5, run these additional statements:

INSERT INTO VPX_LIC_METADATA(DATA_TYPE, LAST_SAMPLE_ID, LAST_SAMPLE_TIMESTAMP, RETAINED_SAMPLE_ID, RETAINED_SAMPLE_TIMESTAMP, GLOBAL_DIGEST, IS_STATE_VALID, WEEK_KEEP_COUNT)
VALUES('ABT', 0, CONVERT(datetime, '1900-12-31 00:00:00', 120), 0, CONVERT(datetime, '1900-12-31 00:00:00', 120), NULL, 1, -1);

For Oracle:

INSERT INTO VPX_LIC_METADATA(DATA_TYPE, LAST_SAMPLE_ID, LAST_SAMPLE_TIMESTAMP, RETAINED_SAMPLE_ID, RETAINED_SAMPLE_TIMESTAMP, GLOBAL_DIGEST, IS_STATE_VALID, WEEK_KEEP_COUNT)
VALUES('UHD',0, TO_DATE('1900-12-31 00:00:00','YYYY-MM-DD HH24:MI:SS'), 0, TO_DATE('1900-12-31 00:00:00','YYYY-MM-DD HH24:MI:SS'), NULL, 1, 208);

INSERT INTO VPX_LIC_METADATA(DATA_TYPE, LAST_SAMPLE_ID, LAST_SAMPLE_TIMESTAMP, RETAINED_SAMPLE_ID, RETAINED_SAMPLE_TIMESTAMP, GLOBAL_DIGEST, IS_STATE_VALID, WEEK_KEEP_COUNT)
VALUES('MAC', 0, TO_DATE('1900-12-31 00:00:00','YYYY-MM-DD HH24:MI:SS'), 0, TO_DATE('1900-12-31 00:00:00','YYYY-MM-DD HH24:MI:SS'), NULL, 1, -1);

You must run this statement when running vCenter Server 5.5:

INSERT INTO VPX_LIC_METADATA(DATA_TYPE, LAST_SAMPLE_ID, LAST_SAMPLE_TIMESTAMP, RETAINED_SAMPLE_ID, RETAINED_SAMPLE_TIMESTAMP, GLOBAL_DIGEST, IS_STATE_VALID, WEEK_KEEP_COUNT)
VALUES('ABT', 0, TO_DATE('1900-12-31 00:00:00','YYYY-MM-DD HH24:MI:SS'), 0, TO_DATE('1900-12-31 00:00:00','YYYY-MM-DD HH24:MI:SS'), NULL, 1, -1)

Start the VMware VirtualCenter Management Webservices service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

For vCenter Server 4.1

Stop the VMware VirtualCenter Management Webservices service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Ensure that the VPX_LIC_* tables are empty. If not, delete their contents.

To delete the contents from the VPX_LIC_* tables:

Launch SQL Management Studio (SQL Server) or SQL*Plus (Oracle).

Run these SQL statements:

DELETE FROM VPX_LIC_SNAPSHOT;
DELETE FROM VPX_LIC_SNAPSHOT_VC_GROUP;
DELETE FROM VPX_LIC_USAGE;
DELETE FROM VPX_LIC_CONTEXT;
DELETE FROM VPX_LIC_ASSETS;
DELETE FROM VPX_LIC_LICENSES;
DELETE FROM VPX_LIC_VC_GROUP_MEMBERS;
DELETE FROM VPX_LIC_VC_GROUPS;
DELETE FROM VPX_LIC_METADATA;
DELETE FROM VPX_LIC_SETTINGS;

Run this INSERT statement to initialize the licensing metadata in the VPX_LIC_METADATA table:

For SQL Server:

INSERT INTO VPX_LIC_METADATA (LAST_SAMPLE_ID, LAST_SAMPLE_TIMESTAMP, RETAINED_SAMPLE_ID, RETAINED_SAMPLE_TIMESTAMP, GLOBAL_DIGEST, IS_STATE_VALID, WEEK_KEEP_COUNT)
VALUES(0, CONVERT(datetime, '1900-12-31 00:00:00', 120), 0, CONVERT(datetime, '1900-12-31 00:00:00', 120), NULL, 1, 208);

For Oracle:

INSERT INTO vpx_lic_metadata(last_sample_id, last_sample_timestamp, retained_sample_id, retained_sample_timestamp, global_digest, is_state_valid, week_keep_count)
VALUES(0, TO_DATE('1900-12-31 00:00:00','YYYY-MM-DD HH24:MI:SS'), 0, TO_DATE('1900-12-31 00:00:00','YYYY-MM-DD HH24:MI:SS'), NULL, 1, 208);

Start the VMware VirtualCenter Management Webservices service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Note: If these steps do not resolve the issue, you may have to recreate the stored procedures and/or rollup jobs. For more information, see Verifying vCenter Server 4.1 jobs and stored procedures (1029824).

Related Information

For more information, see vCenter Server service status reports the error: Could not find stored procedure 'process_license_snapshot_proc' (2004647).

How to stop, start, or restart vCenter Server services
vCenter Server service status reports the error: Could not find stored procedure 'process_license_snapshot_proc'
VMware vCenter Service 4.x/5.x のステータスで次のエラーが報告される： Cannot store license usage in the vCenter Server database

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

KB
•
从 VMware VirtualCenter 2.5.x 浏览数据存储失败：无法登录到 NFC 服务器 (1017196)

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 vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 5.1.x

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

Take Our Survey

Support Assistant