Business article search

Apache Tomcat is not running (service could not start)—how do I fix this problem?

In cases where the ESET Remote Administrator Web Console (ERA Web Console) is not running, check whether the Apache Tomcat service is running (open a Run dialog, type services.msc, click OK, locate the Apache Tomcat service, and then verify that Running is listed in the Status column); if it is not, try to start the service manually by selecting it and clicking Start. 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 7 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, follow the step-by-step instructions below to resolve your issue:

  1. Navigate to your %TOMCAT_HOME%\bin directory (for example, C:\Program Files\Apache Tomcat\Tomcat7\bin) and double-click tomcat7w.exe.


Figure 1-1
Click the image to view larger in new window

  1. Click the Java tab, select the check box next to Use default, and then click OK.


Figure 1-2

  1. Start the Apache Tomcat service. The service should start without issue.

Rate this article:

We cannot respond to feedback from this form. Requests for assistance should be submitted through your normal support channel.