INFO vpxd #### [vc@#### sub="licenseClient" opID="HeartbeatStartHandler-########-########"] Assign license to host: '<HOSTNAME>'
WARNING vpxd #### [vc@#### sub="licenseClient" opID="HeartbeatStartHandler-########-########"] Failed request to VAPI service; Error:
--> com.vmware.vapi.std.errors.invalid_argument
--> Messages:
--> com.vmware.esx.licensing.entitlements.invalid_or_malformed_token<Invalid or malformed entitlement token.>
ERROR vpxd #### [vc@#### sub="licenseClient" opID="HeartbeatStartHandler-########-########"] License was unsuccessfully set on host: <HOSTNAME> with error: Error:
--> com.vmware.vapi.std.errors.invalid_argument
--> Messages:
--> com.vmware.esx.licensing.entitlements.invalid_or_malformed_token<Invalid or malformed entitlement token.>
During an ESXi host upgrade to version 9.1, a timing sequence mismatch occurs where vCenter Server initially attempts to push a legacy 9.0 formatted license payload to the host. The upgraded 9.1 host rejects the legacy token due to new cryptographic signature requirements enforced by the 9.1 License Server appliance.
This issue is targeted to be resolved in an upcoming release. To stay updated on the fix status, subscribe to this article.