Health check fails to retrieve data about service <Cluster_name> on 'vSphere ESX Agent Manager'. Verify that the service <Cluster_name> is running and try again.

Products

• VMware vCenter Server

Issue/Introduction

• When configuring the cluster with an image base, the pre-check fails with the following error:

Health check fails to retrieve data about service <Cluster_name> on 'vSphere ESX Agent Manager'. Verify that the service <Cluster_name> is running and try again.

• EAM (ESX Agent Manager) is a service in vCenter Server, the following log file might show related errors:

YYYY-MM-DDThh:mm:ss |  INFO | vim-monitor | VcListener.java | 131 | Retrying in 10 sec.
YYYY-MM-DDThh:mm:ss | ERROR | vlsi | DispatcherImpl.java | 468 | Internal server error during dispatch
com.vmware.vim.binding.eam.fault.EamServiceNotInitialized: EAM is still loading from database. Please try again later.
        at com.vmware.eam.vmomi.EAMInitRequestFilter.handleBody(EAMInitRequestFilter.java:57) ~[eam-server.jar:?]
        at com.vmware.vim.vmomi.server.impl.DispatcherImpl$SingleRequestDispatcher.handleBody(DispatcherImpl.java:373) [vlsi-server.jar:?]
YYYY-MM-DDThh:mm:ss | ERROR | vim-monitor | VcListener.java | 124 | An unexpected error in the changes polling loop
com.vmware.eam.EamRemoteSystemException: Unexpected error communicating with the vCenter server.
        at com.vmware.eam.vim.server.impl.VimRoot.rootOperation(VimRoot.java:106) ~[eam-server.jar:?]
        at com.vmware.eam.vim.server.impl.VimRoot.currentTime(VimRoot.java:78) ~[eam-server.jar:?]
        at java.lang.Thread.run(Thread.java:750) [?:1.8.0_402]
Caused by: com.vmware.vim.binding.vim.fault.NotAuthenticated: The session is not authenticated.
        at sun.reflect.GeneratedConstructorAccessor56.newInstance(Unknown Source) ~[?:?]
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_402]
        at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_402]
        at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_402]

Cause

The issue occurs due to a mismatch between the vpxd-extension certificate stored in VECS (vCenter Server Certificate Store) and the certificate information stored in the vCenter Server Database for the EAM extension.

Resolution

To resolve the issue, update the vpxd-extension certificate of vCenter Server by following the procedure outlined in the following KB article:

EAM "Failed to login to vCenter as extension, Cannot complete login due to an incorrect user name or password" after replacing the vCenter Server certificates