tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pid <>
Subject Re: Unable to start Tomcat 6 on Windows Server 2003
Date Sat, 26 Jun 2010 16:05:00 GMT
On 26/06/2010 15:48, wrote:
>> On 26/06/2010 09:00, wrote:
>>> Hi,
>>> I have a problem starting a TomCat on a Windows 2003 Server:
>>> Java Version installed: 1.6.0_11   JRE & JDK
>>> Tomcat Version used for tests: 6.0.16 & 6.0.26
>>> First i installed the Tomcat.exe on the server -> Tomcat do not start
>> Where did you get "Tomcat.exe" and how did you do the install?
> Of course from:
> exact name: apache-tomcat-6.0.16.exe   

Is there a reason not to use a current version instead of an old one?

>>> Failure in Log:
>>> [error] FindClass org/apache/catalina/startup/Bootstrap failed [error]
>> Failed loading main org/apache/catalina/startup/Bootstrap class C:\Program
>> Files\Apache Software Foundation\Tomcat 6.0\bin\bootstrap.jar [error]
>> ServiceStart returned 3
>>> Then i downloaded the and made tests through a command box:
>>> The Tomcat do not start with „catalina.bat run“ in the box is
>> written that he can not find "Class org/apache/juli/logging/LogFactory"...
>>> The file is definitely there...
>> What happens if you run startup.bat?
> A second dos box shortly appear and is closing immediately...

Start a command prompt first, then manually type the startup.bat command
- don't double click the file to run it.

What does the error message say exactly?


>>> I installed a Test VM and adapt the configuration 100% with double check
>> from a colleague: Tomcat is running.
>> What did you do differently when you installed it in the VM rather in
>> the main OS?
> Nothing. I installed Java & Tomcat totally in the same way! Same downloaded files
as well.
> The difference is that the main OS is part of a domain and i think with specific group
policies, but currently i do not know which can be causing this... the vm is a standalone
w2k3 with no gpo´s.
> As written before: I think it is one of the domain policies that is causing this but
i really have no clue which policy can cause this behavior... Any suggestions?
> see also below description
>> p
>>> The server on which it is not running is in a domain. The Test VM is a
>> standalone server.
>>> -> Suggestion: There are policies that are preventing the Tomcat to
>> start... Question now: Which one can this be?
>>> Do any one of you any Policies in a windows domain that prevent a Tomcat
>> to start with such errors?
> thanks, destroyer

View raw message