This happens when the user account the heartbeat service is running under does not have privileges to query the EventSentry service status on the remote host(s). This is due to enhanced operating system security for all Windows versions, starting with Windows Server 2003 SP1 and Windows Vista.
You can solve this problem by
A) Running the EventSentry Heartbeat Monitor under a user account with elevated permissions (e.g. an account that is a member of the Domain Admins group)
B) Configuring authentication in the EventSentry console, and providing administrator credentials at the global, group, or computer level. Please see: https://www.eventsentry.com/documentation/help/html/?remoteupdateauthentication.htm
C) By changing the ACL permissions of the EventSentry service on each remote host.
Option A: Changing the account the EventSentry Heartbeat Monitor service is running under:
Once you change this setting and restart the EventSentry heartbeat agent.
Option C: Changing the ACL entries of the EventSentry service on all monitored hosts
*If you are running EventSentry v18.104.22.168 or newer then execute the following command:
subinacl.exe /service \COMPUTER1\EventSentry /GRANT=MYDOMAIN\ESHOST$=QS
subinacl.exe /service \COMPUTER1\EventSentry /GRANT=MYDOMAIN\ESHOST$=R
Where COMPUTER1 is a computer running the EventSentry agent and DOMAIN is the domain that ESHOST is part of (you may be able to substitute the domain name with the computer name). Repeat this for every computer that is affected by the "Access Denied" error message.