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

[Leif M. <lei...@ta...>]

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
>