"Insufficient License Capacity" licensing error for vCenter in VMware Cloud Foundation (VCF) Operations
search cancel

"Insufficient License Capacity" licensing error for vCenter in VMware Cloud Foundation (VCF) Operations

book

Article ID: 446090

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • In VCF Operations, a licensing mismatch may occur where a vCenter Server reports insufficient capacity for ESX hosts despite the global license server recognizing the correct hardware footprint. This prevents managed hosts from being fully licensed.

Symptoms

  • Under Manage > Licensing > Licenses & Registration, the Issues column for vCenter displays:
    An asset added to [vCenter_FQDN] could not be licensed due to insufficient license capacity. Allocate more capacity to the license assigned to [vCenter_FQDN].
  • The vCenter Systems view shows only ## cores used (licensing only one host), while Primary Unlicensed Used Capacity shows a significantly higher count.
  • The global VMware Cloud Foundation (cores) for vCenter Server view correctly displays the total core count.

Environment

VMware Cloud Foundation (VCF) 9.x

Cause

This issue is caused by a synchronization stall within the VCF Operations licensing database, creating a "split-brain" state where the system detects the hardware footprint globally but fails to map those cores to the specific vCenter integration cache.

Resolution

  1. Reclaim Used Capacity
    1. Log in to the VCF Operations UI.
    2. Navigate to Manage > Licensing > Licenses & Registrations > Manage > License Servers.
    3. Click on the relevant License Server.
    4. Scroll down to Licensed Assets, select the affected vCenter Server, and click Reclaim Used Capacity.

  2. Clear and Reset the Integration Cache
    1. Navigate to Operate > Administration > Integrations.
    2. Expand the VCF adapter and locate the specific vCenter Domain.
    3. Click the three dots (ellipsis) icon next to the domain and select Delete all to remove the stale data connection.
    4. Wait about 15 minutes for the backend database to fully purge the stale licensing data.

  3. Reconnect and Reassign the License
    1. Under the Integrations page, select Add > vCenter Adapter and click Start Collecting to re-initialize the connection.
    2. Navigate back to the License & Registrations page and verify the vCenter Server is now correctly visible under vCenter Systems.
    3. Manually assign the primary license to the vCenter Server to cover the full core count.

Additional Information

Note: Mixed-version environments (ESXi 8.x managed by vCenter 9.1) draw core capacity directly from your Version 9+ subscription. As a result, this error can still occur even if your 8.x hosts are assigned legacy license keys. Please refer: Error: An asset added to vCenter could not be licensed due to insufficient license capacity in VCF 9.1.

Mixed-Version Environments