Re: [Wrapper-user] Antw: service not starting on Windows 2008R1 64b

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Javier,
When you run with the 32-bit JVM, is that also with the 32-bit
Wrapper?  Or is it using the same 64-bit Wrapper?

If you place the 32-bit Wrapper in the same location as the 64-bit
Wrapper, it is strange that one would work while the other would not.
I am not aware of anything in the system which would restrict the use
of a 64-bit Wrapper vs the 32-bit Wrapper.

If a wrapper.log file is never being created, then the problem is
happening well before the JVM is ever launched, so the configured JVM
should not matter.  The lack of the wrapper.log indicates that the
wrapper.exe is never being launched or that it is failing before
reading in the wrapper.conf file.  In the later case, it would attempt
to write a wrapper.log into the current directory which would be the
location of the wrapper.exe.

You had said earlier that you get an error in the Event Log, but that
it was not useful.  Could I see exactly what that message is?  It
might give me a clue.

Windows 2003 was a lot more loose with security.  2008 and Vista both
introduced much stricter restrictions, including making it impossible
for the System user to write to the windows directory.

You had confirmed earlier that you could run the 64-bit Wrapper in a
console correct?  So that would rule out any problem with the binary
other than a permissions issue.

One thing to try as a test, is to try installing and running the
service as the same user as you are logged in as.  Please read over
the following page on how to do this:
http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-account.html
While this is not a permanent solution, it working or not would give
clues as to the problem with the SYSTEM user.

Cheers,
Leif

On Thu, Jun 10, 2010 at 10:09 PM, Javier Muguruza
<jav...@at...> wrote:
> A further info I got from a colleague, he tested the exact environment in a  windows 2003 enterprise x64 R2 SP2 and it worked fine, so the problem is in Windows 2008 64b
>
>> -----Original Message-----
>> From: Javier Muguruza [mailto:jav...@at...]
>> Sent: jueves, 10 de junio de 2010 11:02
>> To: wra...@li...
>> Subject: Re: [Wrapper-user] Antw: service not starting on Windows
>> 2008R1 64b
>>
>> Leif,
>>
>> Yes we have verified all these, all are ok for SYSTEM. I agree with you
>> that it looks like a permission issue cause it runs fine with
>> Administrator. But OTOH this exact setup works if we change to a 32b
>> jdk and we use 32b wrapper...maybe the issue is permission in some file
>> only involved in 64b jdk...
>>
>> Thanks,
>> javier
>>
>> > -----Original Message-----
>> > From: Leif Mortenson [mailto:lei...@ta...]
>> > Sent: jueves, 10 de junio de 2010 10:38
>> > To: wra...@li...
>> > Subject: Re: [Wrapper-user] Antw: service not starting on Windows
>> > 2008R1 64b
>> >
>> > Javier,
>> > Thank you for that information.   If the wrapper.log is never being
>> > written then that most likely means that the Windows Service Manager
>> > is failing to ever launch the wrapper.exe binary as a service.   This
>> > can happen if the SYSTEM user does not have access to the directory
>> > where the Wrapper.exe binary is located.   Could you please check the
>> > file permissions on all of the parent directories as well and make
>> > sure that they have at least read access for the SYSTEM user?  The
>> > logs directory will also need to have write access.
>> >
>> > Cheers,
>> > Leif
>> >
>> > On Thu, Jun 10, 2010 at 5:30 PM, Javier Muguruza
>> > <jav...@at...> wrote:
>> > > Replays to both of you guys inline, thanks:
>> > >
>> > >
>> > >
>> > > Hi,
>> > >
>> > > How does it fail, on what point does it fail? Windows Service
>> cannot
>> > be
>> > > started, it is working on the same environment with a x86 jdk (and
>> > > wrapper-windows-x86-32-3.3.0) using the same config, and Path to
>> > executable
>> > >  Path to executable: C:\ADAM\adam\wrapper-bin\wrapper.exe -s
>> > > C:\ADAM\adam\wrapper-conf\ManagerProcess.conf
>> > >
>> > > If launched directly through a command line like
>> > > C:\ADAM\adam\wrapper-bin\wrapper.exe
>> > > C:\ADAM\adam\wrapper-conf\ManagerProcess.conf it starts properly
>> > >
>> > > Do you have Wrapper Debug Settings enabled to generate verbose
>> > output?
>> > >
>> > > Do you use network resources like mapped drives or unc path? No,
>> > everything
>> > > is on local drive, no mapped drive
>> > >
>> > > Do you use any resource that is only available to "regular" windows
>> > >
>> > > users like printers? No
>> > >
>> > > Do you try access a regular windows users environment? We try to
>> > access a
>> > > few environment variables, but they are all available globally.
>> > >
>> > > Hubert
>> > >
>> > >
>> > >
>> > > Christian.
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > you can send support requests over this mailing list as well as
>> > >
>> > > directly sending to su...@ta...
>> > >
>> > >
>> > >
>> > > Hubert already pointed you to possible problems when starting as a
>> > service.
>> > >
>> > >
>> > >
>> > > Let me add some additional questions:
>> > >
>> > > If the wrapper fails to start as service with the local system
>> user,
>> > >
>> > > could you check if there is a log file "wrapper.log" in the folder
>> > the
>> > >
>> > > wrapper binary is located?
>> > >
>> > > No wrapper.log file is left on the bin folder.
>> > >
>> > >
>> > >
>> > > Could you also try to start the service from Console (you need to
>> > >
>> > > start the console as admin) and run the Start<App>.bat file? What
>> > >
>> > > output message from the wrapper can you see there?
>> > >
>> > > It also fails,
>> > >
>> > > C:\ADAM\adam\wrapper-bin>StartTestWrapper-NT.bat
>> > > ..\wrapper-conf\ManagerProcess.
>> > >
>> > > conf
>> > >
>> > > wrapper  | Working directory set to: C:\ADAM\adam\mig-master
>> > >
>> > > wrapper  | Starting the adam-ManagerProcess service...
>> > >
>> > > wrapper  | Waiting to start...
>> > >
>> > > wrapper  | The adam-ManagerProcess service was launched, but failed
>> > to
>> > > start.
>> > >
>> > > Press any key to continue . . .
>> > >
>> > >
>> > >
>> > > Launching directly the wrapper.exe it works
>> > >
>> > > C:\ADAM\adam\wrapper-bin>wrapper.exe ..\wrapper-
>> > conf\ManagerProcess.conf
>> > >
>> > > wrapper  | Working directory set to: C:\ADAM\adam\mig-master
>> > >
>> > > wrapper  | --> Wrapper Started as Console
>> > >
>> > > wrapper  | Java Service Wrapper Standard Edition 3.3.0
>> > >
>> > > wrapper  |   Copyright (C) 1999-2008 Tanuki Software, Inc.  All
>> > Rights
>> > > Reserved.
>> > >
>> > >
>> > >
>> > > wrapper  |     http://wrapper.tanukisoftware.org
>> > >
>> > > wrapper  |   Licensed to Atempo Java Service Wrapper for ADAM
>> Manager
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > Sincerely,
>> > >
>> > > Christian