Knowledge Base - Technical Articles
Problem: Jakarta Tomcat service fails to start due to an internal error
|Software:||ArcIMS 3.0, 3.1, 4.0|
|Platforms:||Windows NT 4.0, 2000|
From Control Panel Services:
"Could not start the Jakarta service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, contact your system administrator."
From the command prompt using "net start Jakarta":
"The Jakarta service is starting. The Jakarta service could not be started. The service did not report an error."
In the Windows Application Event Log there will be the following entry:
"The RegQueryValueEx function failed for the following reason: The operation completed successfully."
Solution or Workaround
Caution: Do not attempt to edit the registry value as it will not fix the problem. However, you can use the Registry Editor to determine if this entry exceeds the 256 character limit.
ESRI cannot guarantee results from incorrect modifications while following these instructions. Therefore, use caution and proceed at your own risk.
1. Remove the Jakarta service. For example,
C:\jakarta-tomcat-3.2.3\bin>TomcatService -uninstall Jakarta
- or -
C:\jakarta-tomcat-3.2.3\bin>JavaService -uninstall Jakarta
2. If your Jakarta Tomcat directory is located somewhere other than the root directory, (for example - C:\Program Files\), use Windows Explorer to move the folder to a root directory, such as C:\ or D:\.
3. Rename the Jakarta Tomcat installation directory to simply "tomcat", placing all Jakarta files in a single location, for example D:\tomcat.
4. In the system Environment Variables, change the value of TOMCAT_HOME to correspond with the above changes.
Likewise, if using the IIS web server, make the corresponding changes to the registry entries at HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0
5. Reinstall the Jakarta service by running the Tomcat321Service.bat file.
6. Start the Jakarta service and confirm that the error messages no longer occur.
Last Modified: 11/20/2003