WARNING vpxd #### [vc@#### sub="licenseClient" opID="LicenseUtilRunOnTimer-#######"] VAPI provider failed; </hgw/host-##>, /api, Error:
--> system_error
--> Messages:
--> vapi.invalid.result.code<Recv of frame failed with code: 503 Service Unavailable>
--> , bt:
--> [context]################################################################################################################################[/context]
WARNING vpxd #### [vc@#### sub="licenseClient" opID="LicenseUtilRunOnTimer-#######"] Failed request to VAPI service; Error:
--> system_error
--> Messages:
--> vapi.invalid.result.code<Recv of frame failed with code: 503 Service Unavailable>
--> , bt:
--> [context]################################################################################################################################[/context]
ERROR vpxd #### [vc@#### sub="licenseClient" opID="LicenseUtilRunOnTimer-#######"] Failed to list the entitlements from host: host-##, N4Vpxd7Clients19ErrorValueExceptionE(Error:
--> system_error
--> Messages:
--> vapi.invalid.result.code<Recv of frame failed with code: 503 Service Unavailable>
--> )
--> [context]################################################################################################################################[/context]
INFO vpxd #### [vc@#### sub="licenseClient" opID="LicenseUtilRunOnTimer-#######"] Schedule com.vmware.license.HostRejectedLicenseEvent for: vim.HostSystem:host-##
ERROR vpxd #### [vc@#### sub="licenseClient" opID="LicenseUtilRunOnTimer-#######"] License was unsuccessfully set on host: host-## with error: Error:
--> system_error
--> Messages:
--> vapi.invalid.result.code<Recv of frame failed with code: 503 Service Unavailable>
-->
VCF 9.1
VMware vCenter Server 9.1
VMware ESXi 9.1
This is a known defect in the vCenter license polling logic.
While a host is rebooting, its services are temporarily unavailable. vCenter continues to poll the host for license entitlements during this window.
If the host takes longer than expected to initialize its services, vCenter fails to receive a valid response and incorrectly triggers the "License assignment failed" alarm.
This issue is specifically prevalent in environments with extended boot times (e.g., heavy hardware initialization or firmware checks).
This alarm is a false positive and does not impact the actual licensing state or functionality of the host once it has fully booted and reconnected to vCenter.
Engineering is aware of this issue. A permanent fix is scheduled for the future release.