• Summary tab in vSphere Client shows "VMware vAPI Endpoint Service Health Alarm" in vCenter Server 7.0.
• vCenter is not in Enhanced Linked Mode configuration. For more information, see vCenter Enhanced Linked Mode.
• You see a warning in /var/log/vmware/vapi/endpoint/endpoint.log , similar to :

2022-01-24T00:22:17.815+09:00 | WARN | state-manager1      | ApiConnectionsStateBuilder   | Duplicate service URLs detected for URL http://localhost:10095/trustmanagement and serviceIds 204c27a6-17b8-4249-a689-34794704eaff\com.vmware.trustmanagement.vapi and 03f85a86-ffd8-424f-afce-70080d9afecd\com.vmware.trustmanagement.vapi. Service 204c27a6-17b8-4249-a689-34794704eaff\com.vmware.trustmanagement.vapi will not be registered.
2022-01-24T00:22:17.815+09:00 | INFO | state-manager1      | StatusInfoFactory       | HEALTH YELLOW Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:10095/trustmanagement.

To fix this issue, you will need to remove the duplicate service(s) endpoints.

Note: Please make sure to have a valid backup or offline (VCSA VM powered off) snapshot before applying the below steps.

1. Log in to the vCenter Server Appliance through SSH.

2. Remove the duplicate service with lstook.py. The service to remove is the one that endpoint.log mentions "will not be registered". It is "204c27a6-17b8-4249-a689-34794704eaff" on the above case.

   # /usr/lib/vmware-lookupsvc/tools/lstool.py unregister --url https://localhost/lookupservice/sdk --id 204c27a6-17b8-4249-a689-34794704eaff --user '[email protected]' --password 'PASSWORD' --no-check-cert 

3. Reboot the VCSA, or restart all services.
   
   #service-control --stop --all; service-control --start --all

For more information about Duplicate vCenter Service Registration, see Find a duplicate registered vCenter Server instance .