This is a known issue with versions 3.2.1.x and older. The best way to resolve this issue is to update to the latest release of EventSentry (v3.4 or v3.3) which resolve this issue and ensures that updates are checked security via https. If you cannot update to at least v220.127.116.11 then you can:
- Update to the latest build of the major release you are running (v18.104.22.168 or v22.214.171.124 respectively)
- Turn off the automatic version check under Tools-Options in the management console
I would definitely suggest updating to v3.4, the update process is usually very straightforward. Please let me know if you have any additional questions.