Re: Service on Windows Server 2003

2007-10-26 Thread Dan Armbrust
Finally - I understand most of what is wrong! I finally got access to the system again, and after pulling off the debug log from the service launcher, things became clear. It turns out that on this system, the command that was actually being run to register the service was: %TOMCAT_HOME%\bin\tom

Re: Service on Windows Server 2003

2007-10-25 Thread Dan Armbrust
jvm.cfg contains the following: -client KNOWN -server KNOWN -hotspot ALIASED_TO -client -classic WARN -native ERROR -green ERROR I don't think that there is a JAVA_OPTS variable set, but I will verify that on the problem machine. Thanks, Dan On 10/26/00, [EMAIL PROTECTED] <[EMAIL PROTECTED]>

Re: Service on Windows Server 2003

2007-10-25 Thread Dan Armbrust
I am using this version of java: C:\NetProvision\jre\bin>java -version java version "1.5.0_07" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03) Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode) The jvm.dll version that I am using reports File version: 5.0.70.3 Full

Re: Service on Windows Server 2003

2007-10-24 Thread Gabe Wong
if using jdk6, make sure msvcr71.dll is in the path of jvm.dll. The easiest thing to do is to copy msvcr71.dll to the jre directory from the jdk directory like so: copy %JDK_HOME%\bin\msvcr71.dll %JDK_HOME%\jre\bin\server\ Dan Armbrust wrote: I have a difficult but severe problem with the tomca