[KB7795] Apache Tomcat is not running – troubleshooting for ESET PROTECT On-Prem (Windows)

Issue

Solution

Apache Tomcat requires Java:
  • Make sure that Java, ESET PROTECT On-Prem, and Apache Tomcat are 64-bit.
  • If you have multiple Java versions installed on your system, we recommend that you uninstall earlier Java versions and only keep the latest version.
  • As of January 2019, Oracle JAVA SE 8 public updates for business, commercial or production-use require a commercial license. If you do not purchase a JAVA SE subscription, you can use the Install ESET PROTECT Web Console using JDK guide to transition to a no-cost alternative.

Check the Apache Tomcat service

In cases where the ESET PROTECT Web Console is not running, verify if the Apache Tomcat service is running:

  1. Press the Windows key + R, type services.msc and press the Enter key.

  2. Locate the Apache Tomcat service and verify that Running is listed in the Status column. If it is not running, click Apache Tomcat Start


Error message from a Java update is received (error code 1)

While trying to start the service, you might receive the following error message, which may result from a Java update: "Windows could not start the Apache Tomcat on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to the service-specific error code 1."

If you receive this error while attempting to start the Apache Tomcat service, refer to the instructions below to resolve your issue:

  1. Navigate to your %TOMCAT_HOME%\bin directory (for example, C:\Program Files\Apache Software Foundation\apache-tomcat-9.0.40\bin) and double-click tomcat9w.exe.

    Examples

    Tomcat_folder and tomcat9w.exe are examples – use the actual names on your system.

    Figure 1-1
  2. Click Java, deselect the Use default check box and select the Java virtual machine file path (C:\[Java folder path]\bin\server\jvm.dll or C:\[Java folder path]\bin\client\jvm.dll) and click OK.

    Figure 1-2
  3. Start the Apache Tomcat service. The service should start without issue.

For more information, see the ESET PROTECT On-Prem Troubleshooting.