Jump to content

ESET- ERA Web Console doesn't load


mc6576897987
 Share

Recommended Posts

We have a situation that we can't load the remote webpage of ESET ERA.

What I did and not worked:

-Tomcat7w.exe On the Startup and Shutdown tabs, change the Mode: to use Java pictured below.

-ServicesPipeTimeout solution.

- Tomcat7w.exe | Click the Java tab, select the check box next to Use default and then click OK

- Restart ESET remote server service - Tried to start Apache Tomcat 7 but not starting

These all did not worked at all.

What can be a real solution that you can show me?

eset era.JPG

 

OS: windows server 2016 standart 

Edited by mc6576897987
Link to comment
Share on other sites

  • ESET Staff

Could you please check (or attach) Apache Tomcat logs located in C:\Program Files\Apache Software Foundation\Tomcat 7.0\Logs ? Have you made some system configuration changes? Most common issue preventing tomcat to start are:

  • invalid TLS certificate configuration. This would be case in case you made configuration changes
  • invalid JAVA configuration. Problem might happen in case Java was updated on this system (beware of automatic updates). In such case, helper tool Tomcat7w.exe could be used to configure Apache Tomcat to use proper Java version = the one currently installed
  • port that is supposed to be used by Apache Tomcat is already taken, i.e. another application might be using the same TCP port.
  • Incompatible Java and Apache Tomcat: there are known issues with Apache Tomcat 7.0.x distributed with ERA 6.5 in combination with Java 10. In such case, upgrade of Apache Tomcat to latest 7.0.* version is recommended.
Link to comment
Share on other sites

11 hours ago, MartinK said:

Could you please check (or attach) Apache Tomcat logs located in C:\Program Files\Apache Software Foundation\Tomcat 7.0\Logs ? Have you made some system configuration changes? Most common issue preventing tomcat to start are:

  • invalid TLS certificate configuration. This would be case in case you made configuration changes
  • invalid JAVA configuration. Problem might happen in case Java was updated on this system (beware of automatic updates). In such case, helper tool Tomcat7w.exe could be used to configure Apache Tomcat to use proper Java version = the one currently installed
  • port that is supposed to be used by Apache Tomcat is already taken, i.e. another application might be using the same TCP port.
  • Incompatible Java and Apache Tomcat: there are known issues with Apache Tomcat 7.0.x distributed with ERA 6.5 in combination with Java 10. In such case, upgrade of Apache Tomcat to latest 7.0.* version is recommended.

My folder location on the server is :   C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\Logs

No we didn't configure the JAVA at all. I just update it manual last week (as a Junior System Specialist). Should I check the new updates for Apache? It is already 7.0 version. And its not about ports.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...