I have the same issue, after upgrading from 7.0.2.00500 to 7.0.3.00500.
This is what I found at the end of /storage/log/vmware/vsphere-ui/vsphere_client_virgo.log:
[ERROR] http-nio-5090-exec-5
com.vmware.vsan.client.services.ProxygenController
(b8cc6080eb36) Service method encountered an error caused by:
`Cannot retrieve the health service instance.`com.vmware.vsan.client.services.VsanUiLocalizableException: null
at com.vmware.vsphere.client.vsan.health.VsanHealthPropertyProvider.getVcHealthHealthSummary(VsanHealthPropertyProvider.java:160)
Followed by hundreds of lines of debug. We aren't using vSAN.
The only thing I could find that was suspicious is that whenever I try to restart the VMware Analytics Service, I get an error immediately stating "Unable to execute request. Check internet connection and server status. Digging into this I found the following in the /storage/log/vmware/analytics/analytics.log:
pool-10-thread-304 WARN vmware.ph.upload.rest.PhRestClientImpl
Failed to execute request: https://vcsa.vmware.com:443/ph/api/v1/manifest?collectorId=vsphere.gcm.1_0_0&instanceId=OMITTED&v=3.0.535764
pool-10-thread-304 WARN vmware.ph.upload.rest.ProxyAwareHttpExecutor
Failed 3 of 3 attempts to get manifest from VMware server. The reason for the last failure was (enable 'debug' level logging to see the error of every failed attempt): com.vmware.ph.exceptions.resource.ResourceNotFoundException: Request failed: 404 Not Found; Reason:
-------->{"timestamp":1649409091935,"status":404,"error":"Not Found","message":"A manifest could not be found. Contact the PH team to create a manifest.","path":"/api/v1/manifest"}.
When I visit the link (I omitted the ID) in a browser on any machine, it gives me a page with the exact same info.
.png "GodfatherX64"){kind=avatar}