This issue occurs due to one of the following reasons:
- Time Drift: A significant time difference exists between the VCF Operations VM and the License Server appliance, preventing successful token validation and registration.
- DNS Resolution: VCF Operations does not return its FQDN correctly, or proper forward and reverse lookup entries are missing for the VCF Operations FQDN and short name.
- Uppercase Hostnames/DNS: VCF 9.1 components fail to communicate if DNS records or hostnames contain uppercase characters
- Incorrect Deployment Method: Deploying the OVA via standalone ESXi UI instead of vCenter Server UI prevents vApp/OVF property injection
- Proxy Configuration: The License Server fails to connect if a proxy is configured but not required for internal traffic