Re: [Wrapper-user] App runs as console but not service

[William P. <wp...@be...>]

You were absolutely right: the service ran as a different user with
different permissions than when wrapper.exe launched the application
using the console, and that was, in the end, the culprit.

Thanks, everybody, for chiming in.  I really appreciate the help.

- Bill

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Leif
Mortenson
Sent: Tuesday, June 13, 2006 8:34 PM
To: wra...@li...
Subject: Re: [Wrapper-user] App runs as console but not service

William,
The "Unable to start the service" message is coming from the Wrapper=20
when it attempts
to launch your service via the ServiceManager. The rest of the message=20
is coming from
the ServiceManager.

Could you bring up your Services Control Panel window and look at the=20
service that
you installed?
Are you able to start the service from the control panel?
If you bring up the properties of the service, what is the full command=20
that is shown?
For example:
D:\SourceForge\wrapper\bin\wrapper.exe -s=20
D:\SourceForge\wrapper\conf\wrapper.conf

If that looks correct, my guess would be that you have installed some=20
permissions on the
directory where the wrapper.exe is located which are preventing the=20
system account from
even seeing that file.

Unless you have specified an account in your wrapper.conf file, the=20
Wrapper will
normally run as the SYSTEM account when running as a service. This is=20
different from
the account you are logged in as and thus run as when in console mode.

Cheers,
Leif

William Press wrote:
>
> Greetings,
>
> I'm using Tanuki 3.1.2 to install a service with Tomcat 5.0.28 and JRE

> 1.4.2 on Windows Server 2003.
>
> When I install the service using
>
> wrapper.exe -i C:\foo\bar\wrapper.conf
>
> it successfully installs the service in my Service Manager. However,=20
> when I try to start the service, either using the service manager=20
> (which uses the -s flag) or from the console with
>
> wrapper.exe -t C:\foo\bar\wrapper.conf
>
> I get the message
>
> [exec] wrapper | Unable to start the service - The system cannot find=20
> the path specified. (0x3)
>
> and not much else.
>
> Now the interesting part: when I run the service from the console,
using
>
> wrapper.exe -c C:\foo\bar\wrapper.conf
>
> it runs without problem.
>
> The platform, library paths, etc, are all set properly in wrapper.conf

> (confirmed by its running successfully with -c). Also, my shell has=20
> the same environment variables as my system.
>
> Enabling the debug flag in wrapper.conf doesn't give any more output=20
> when it errors out, though the successful -c run is more chatty, so I=20
> know it picks up the flag. Tracking the filesystem activity with=20
> FileMon doesn't show anything untoward, and RegMon is too chatty to=20
> make anything of, but I've scrubbed my registry of "tomcat" and=20
> "catalina" in case any previous installations of Tomcat (since=20
> removed) might be bunging up the works.
>
> Any thoughts as to what might be going on and how I might fix it would

> be greatly appreciated.
>
> Thanks,
>
> Bill
>



_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.