The VCHA option is not visible under Configuration in HTML.
Flex/Flash is visible.
PNID was in uppercase.
All service registrations were in uppercase.
Please engage/consult an Escalation Engineer before performing the steps.
VMware vCenter Server Appliance 6.7.x
The service registration with type com.vmware.vapi.vcenter (under vcenterserver) was missing, and another one was that the hostname in the registrations was in uppercase letters.
In /var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log you see messages similar to:
YYYY-MM-DDTHH:MM:SS [ERROR] data-service-pool-783 70000536 100025 200003 com.vmware.vsphere.client.h5.vcha.VchaPropertyProviderAdapter Connection to VCHA vapi service for vcenter 'VCSA.EXAMPLE.COM' failed.
YYYY-MM-DDTHH:MM:SS [ERROR] data-service-pool-509 70000542 100025 200003 com.vmware.vsphere.client.h5.vcha.VchaPropertyProviderAdapter Connection to VCHA vapi service for vcenter 'VCSA.EXAMPLE.COM' failed.
Below are the detailed steps to re-register the vCenter Server registration using a lowercase hostname and include the missing endpoint com.vmware.vapi.vcenter
.
Note: Please ensure all PSC/VCSA nodes are powered off and snapshotted before proceeding.
Steps:
Transfer the Utility:
Use WinSCP to upload the file rebuild67.tgz
to the affected vCenter appliance under the /tmp
directory.
Extract the Utility:
Run the BuildSpecs Script:
Identify the Affected vCenter Node ID:
Example output: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa
Modify the Specification Files:
Open each spec file under cd /tmp/rebuild67
and replace all uppercase hostnames (e.g., VCSA.EXAMPLE.COM
) with lowercase (e.g., vcsa.example.com
).
Use a text editor like Notepad++ for easy find/replace.
Unregister Old Service Registrations: Replace the value <node-ID>
with the value from Step 4
Register New Service Registrations: Ensure all hostnames are lowercase in the specs: