Re: AW: [Wrapper-user] FATAL | wrapper | 2004/10/16 21:35:32 | Unable to execute Java command. Zugriff verweigert (0x5) [Access denied]

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

Frank,
    I doubt very much that the "\..\" in the path is the cause of the 
problem.   That is set in the
batch file used to install the Wrapper and has been used by all Wrapper 
users for a few years
now.
    If you want you can play with the batch file to use a direct path, 
but I doubt that is the
problem.

    I don't have any other specific ideas other than to keep looking 
along the lines of a security
issue with one or more of your directories.   Try installing a JVM in a 
directory with full access
to all users and see how that works.   I don't think so, but it may be 
possible that you are
running into problems loading one or more of the jars as well..  I would 
expect that failure to
come from the JVM as it was launching however.

Leif

Frank Fischer wrote:

>Hi Leif
>
>Thanks a lot for your answer.
>I tried both ways, granting "all rights" to the System account for the Java
>installation dir and creating a new account (with admin privilegdes) and
>running the Wrapper under this account.
>
>Both didn't worked, means the error stays the same. 
>
>One thing that surprised me a little bit (althought this doesn't mean it's
>an error) is the "path to exe" in the "common" tab of the service
>properties. This looks like:
>
>"D:\JavaNTServiceWrapper\bin\wrapper.exe -s
>D:\JavaNTServiceWrapper\bin\..\conf\wrapper.conf"
>
>Could the "\..\" in the path be a problem? If so, where do i change it (it's
>read-only field in the tab)?
>
>Greetings
>Frank
>
>  
>
>>-----Ursprüngliche Nachricht-----
>>Von: wra...@li... 
>>[mailto:wra...@li...] Im Auftrag 
>>von Leif Mortenson
>>Gesendet: Sonntag, 17. Oktober 2004 02:20
>>An: wra...@li...
>>Betreff: Re: [Wrapper-user] FATAL | wrapper | 2004/10/16 
>>21:35:32 | Unable to execute Java command. Zugriff verweigert 
>>(0x5) [Access denied]
>>
>>Frank,
>>    When you run as a console application, the Wrapper and 
>>its JVM are 
>>run as the user you
>>are logged in as at the time.   When run as a service 
>>however, they are 
>>both run as the
>>SYSTEM user by default.
>>    My guess is that you have your JVM installed in a directory which 
>>the SYSTEM user does
>>not have access to.   The SYSTEM user is able to launch the Wrapper 
>>process without any
>>problems, but it is having problems launching the JVM.   This came up 
>>once before, so I will
>>add a more descriptive message to the logs for the next release.
>>
>>    The are two ways to resolve this.
>>1) Add the SYSTEM user to the list of applications that have 
>>access to 
>>the JVM install
>>directory.  This would work, but it may loosed up security 
>>more than you 
>>want.
>>
>>2) Run the Wrapper as a user whic has the required access.    You can 
>>configure the
>>Wrapper to run as a specifc user using the 
>>wrapper.ntservice.account and 
>>..password
>>properties.  Whenever you change these values, you must uninstall and 
>>then reinstall
>>the app as a service or the service configuration will not be updated.
>>http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-a
>>ccount.html
>>
>>Let me know if you have problems getting it working.
>>
>>Cheers,
>>Leif
>>    
>>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
>Use IT products in your business? Tell us what you think of them. Give us
>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>  
>