Licenses could not be assigned to the vCenter System. Please try again or check the error logs. If the issue persists, contact support.
search cancel

Licenses could not be assigned to the vCenter System. Please try again or check the error logs. If the issue persists, contact support.

book

Article ID: 444624

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

Failed to apply License to vCenter server. 

  • Errors observed in the VCF Operations UI: 

 

The following can be seen in the relevent log files:

  • In vcf-licensing-plugin.log

  • YYYY-MM-DDTHH:MM:HH.000Z NOTICE vcf-licensing-plugin 29783 [ops@4413 threadId="1087642" threadName="ServerConnection on port 10000 Thread 253" operationId="#########################"] [com.vmware.vrops.licensing.vcf.task.AssignEntitlementTaskExecutor.executeAssignEntitlementTask] - Executing executeAssignEntitlementTask task ########################## with [VcAssignEntitlementsSpec(vCenterSpec=VcfLicenseVcSpec(vcId=8#########################, vcAssetUri=869c3476-d5aa-4b90-95e4-92747cd55c95, vcHostname=vcenter.local, vcAdapterName=vcenter.local, vcfAdapterName=null, vcVersion=9.0), allocationId=########################)] for user ##########################

  • On the vCenter: var/log/vmware/cis-license/license.log:

  • YYYY-MM-DDTHH:MM:HH.000Z ERROR CISLicense 34 [vc@4413 threadName="http-nio-0.0.0.0-12080-exec-1" logger="server.vapi.impl.util.VapiTaskUtil"] entitlement update task completed with error: com.vmware.vapi.std.errors.InvalidArgument: InvalidArgument (com.vmware.vapi.std.errors.invalid_argument) => {     messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {     id = unused.id,     defaultMessage = Missing Entitlement Allocation Id.,     args = [],     params = <null>,     localized = Missing Entitlement Allocation Id. }],     data = <null>,     errorType = INVALID_ARGUMENT }

 

Environment

VMware Cloud Foundation 9.1

Cause

Stale entries for 9.0 in the VCF Operations database

Resolution

  • IMPORTANT:  Take a snapshot of the VCF Operations VM before proceeding with resolution
  • Check if there are stale 9.0 records, verify this by executing this command in VCF Ops ssh console

su - postgres -c "/opt/vmware/vpostgres/current/bin/psql -d vcopsdb -p 5433 -c \"select vc_id, vc_host, product_family, product_family_version, component_product_family, component_product_family_version from vcf_entitlement_vcenter_raw_usage where vc_id='########################'\""

  • Delete stale records: 

su - postgres -c "/opt/vmware/vpostgres/current/bin/psql -d vcopsdb -p 5433 -c \"delete from vcf_entitlement_vcenter_raw_usage where product_family_version like'9.0%' and vc_id='###########################'\""