To troubleshoot the problematic component, you can trace the communication process as follows:
Start with step 1 and continue to the next step until your issue is resolved. After completing each step, refresh the ERA Web Console and then try to log in again.
The listening ports may already be in use (443, 2222, 2223 or 8443) and prevent ERA services from running properly. See part II here: Check for any possible port conflicts.
C:\Program Files\Apache Software Foundation\Tomcat 7.0\Logs\
If you are still unable to log in to the ERA Web Console, continue to part II below.
The following instructions will take between ten and twenty (10 – 20) minutes to complete depending on your network connection.
%TOMCAT_HOME%\bindirectory (for example,
C:\Program Files\Apache Tomcat\Tomcat7\bin
) and double-click tomcat7w.exe.
%systemdrive%\Program Files\Apache Software Foundation\Tomcat7\Webapps\erato era.old.
Program Files\Apache Software Foundation\Tomcat7\Webapps\
%systemdrive%\to its original location.
Program Files\Apache Software Foundation\Tomcat7\Webapps\era.old\WEB-INF\classes\sk\eset\era\g2webconsole\server\modules\config\EraWebServerConfig.properties
If you are still unable to resolve this issue, include the above ERA Server and Apache Tomcat log files and email ESET technical support.