"Could not execute Online health checks" in Skyline Health in vCenter 7.0/8.0

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• When you select "RETEST", to refresh the information using skyline health, it fails with the error message "Could not execute Online health checks": 

 

• CEIP is joined and the vCenter Server is internet connected.
• In /var/log/vmware/analytics/analytics.log you find the following error snippet:

<YYYY-MM-DD>T<time>pool-14-thread-1 [operationID=agw-0001364] WARN  phservice.cloud.health.vmomi.HealthSystemMo #queryClusterHealthSummary('ManagedObjectReference: type = Folder, value = group-d1, serverGuid = ####', false, NULL, en, 'VSPHERE.LOCAL\Administrator'): '(vim.cluster.VsanClusterHealthSummary) {
	-------->   dynamicType = null,
	-------->   dynamicProperty = null,
	-------->   clusterStatus = null,
	-------->   timestamp = java.util.GregorianCalendar[time=1707771104884,areFieldsSet=true,areAllFieldsSet=true,lenient=true,zone=sun.util.calendar.ZoneInfo[id="UTC",offset=0,dstSavings=0,useDaylight=false,transitions=0,lastRule=null],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2024,MONTH=1,WEEK_OF_YEAR=7,WEEK_OF_MONTH=3,DAY_OF_MONTH=12,DAY_OF_YEAR=43,DAY_OF_WEEK=2,DAY_OF_WEEK_IN_MONTH=2,AM_PM=1,HOUR=8,HOUR_OF_DAY=20,MINUTE=51,SECOND=44,MILLISECOND=884,ZONE_OFFSET=0,DST_OFFSET=0],  

 <YYYY-MM-DD>T<time>  pool-14-thread-1 [operationID=agw-0001364] WARN  phservice.cloud.health.vmomi.HealthSystemMo #queryClusterHealthSummary('ManagedObjectReference: type = Folder, value = group-d1, serverGuid = null', NULL, NULL, true, ['groups', 'timestamp', 'healthScore'], false, NULL, NULL, NULL, NULL, com.vmware.vim.vmomi.server.impl.ActivationQueueCompletion@7626f5cb): in 2.28min (too slow!)

Environment

VMware vCenter Server 8.0

VMware vCenter Server 7.0

Cause

Issue is due to the amount of time it takes for the information to be fetched, and/or due to a time discrepancy between the ESXi hosts and NTP server.

Resolution

Configure NTP on the vCenter Server to fetch time from the ESXi host it is residing on by changing the NTP setting of the vCenter Server from "External Server" to "Host" on the appliance management page/ VAMI page.

If the above step doesn't resolve the issue, try changing NTP server back to external server.