Error "Licenses could not be assigned to vCenter" during license assignment on VVF 9.x
search cancel

Error "Licenses could not be assigned to vCenter" during license assignment on VVF 9.x

book

Article ID: 441499

calendar_today

Updated On:

Products

VMware vSphere Foundation

Issue/Introduction

  • In VMware vSphere Foundation (VVF), the license renewal or assignment process fails.
    This issue occurs specifically after the vCenter Server administrator@vsphere.local password has been manually updated. The system displays the error message: "Licenses could not be assigned to the selected vCenter systems".
  • Viewing the /storage/log/vcops/log/collector.log in the VCF Operations appliance may show the following error:
    ERROR collector 6458 [ops@4413 threadId="3749" threadName="vcf-licensing-assign-4"] [(54) com.vmware.adapter.management.components.licensing.vcf.collector.VCenterLicenseUsageCollector.getVcManagedStatus] - Failed to perform managed check on License Manager for VC <VC ID> at <VC FQDN> com.vmware.vim.binding.vim.fault.InvalidLogin: Cannot complete login due to an incorrect user name or password.

  • Alert shown for "Adapter instance Object is down" as seen in Operate > Alerts:

Environment

  • VMware vSphere Foundation 9.1
  • VMware vSphere Foundation 9.0
  • VCF Operations 9.1
  • VCF Operations 9.0

Cause

The password for the vCenter Server administrator@vsphere.local account was manually changed, but the integration credentials within VCF Operations were not updated to reflect this change. This credential mismatch causes the integration to fail, which in turn blocks the license assignment and renewal workflows.

Resolution

1. Update the password for the integration of vCenter and then restart collection on the object.

  1. Log in to the VCF Operations administration UI.
  2. Navigate to Operate > Administration > Integrations.
  3. Click the Credentials button. 
  4. Click the 3 dots next to the VC-Credential-1 for <FQDN>, which has a credential kind of "Principal Credential", and select Edit.
  5. In the Manage Credential screen, enter the correct/updated password for the administrator@vsphere.local user.
  6. Click OK to save the credential change.

2. Restart collecting for vCenter object.

  1. Go back to Integrations (Operate > Administration > Integrations)
  2. Expand vCenter Object
  3. Click 3 dots, and select Stop collecting All.  Wait for it to stop collecting, it can take a few minutes.
  4. Click 3 dots and select Start Collecting All.  Wait for it to finish start collecting.  It should now show green status.

3. Assign the license to vCenter.

  1. In VCF Operations, navigate to Manage > Licensing > Licenses & Registration.
  2. Scroll to vCenter Systems section at bottom and click checkbox next to vCenter FQDN/Name, then click Assign Primary License button.
  3. Wait for the process to complete, license should now be assigned.