Uri,
See my notes in line below.
On Sun, Nov 1, 2009 at 4:50 PM, Uri Scheiner <
uri@...> wrote:
> Unfortunately, there is nothing in the logs.
> However, when I am logged as the original Administrator and trying to
> launch the services via the command line (running the exact command as
> written in the service), I get the following error:
>
> Calling StartServiceCtrlDispatcher...please wait.
>
> StartServiceControlDispatcher failed!
Most likely you did this: "wrapper.exe -s ..¥conf¥wrapper.conf"
Correct? The "-s" command tells the Wrapper to launch as a service.
This should only be done by the ServiceManager when installed as a
service and will do exactly what you saw when run from the command
line. This is normal as the -s command is not meant to be used by
users directly.
I'll add a little better error message to the output to avoid
confusion in the next release. (3.3.8 is already in code freeze)
> When I am logged as an Administrator I created and running the exact
> command, I get this error:
>
> FATAL | wrapper | Unable to access registry to obtain environment
> variables -
> The operation completed successfully. (0x0)
This is an error attempting to access the registry to load the
environment variables and is not a problem I have seen in the past.
Looking at the code, I just noticed that I was not using the correct
API to obtain the error message text in this case so the cause is not
being made available. I am working on getting this fixed for the
next release.
In the mean time, can you think of anything about your configuration
that might prefent your user from accessing the registry?
Cheers,
Leif
> -----Original Message-----
> From: Leif Mortenson [mailto:
leif.mortenson@...]
> Sent: Thursday, October 29, 2009 8:06 PM
> To:
wrapper-user@...
> Subject: Re: [Wrapper-user] Cannot launch service (using java service
> wrapper)
>
> Uri,
> I have not played with the EC2 machines personally. Could you please
> post your wrapper.log file? Most likely it will include some
> information that will help be suggest a solution.
>
> Cheers,
> Leif
>
> On Thu, Oct 29, 2009 at 4:08 PM, Uri Scheiner <
uri@...> wrote:
>>
>> Hi,
>>
>> I am using Java Service Wrapper and I have the following problem when
> using
>> it on Amazon EC2 machines.
>>
>> When I try to use an administrator user to launch the service, I get the
>> following error:
>>
>> wrapper | Unable to start the service - The service did not respond to
> the
>> start or control request in a timely fashion. (0x41d)
>>
>> I only happens if I try to use a user that I create myself. However, if
> I
>> use the predefined 'Administrator' user (that comes with the machine),
> it
>> works fine. I compared the parameters of the admin user I created and
> the
>> predefined one, and they look the same.
>>
>> Can you think what the problem may be? I tried it on several machines in
>> Amazon and got the same problem. When I am trying it on my own lab
> machines,
>> it doesn't happens.
>>
>>
>>
>> Thanks,
>> Uri
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Wrapper-user mailing list
Wrapper-user@...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
Some parts of this message have been removed.
Learn more about Nabble's security policy.
