Re: [Wrapper-user] Fw: Regarding Windows NT problem

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

Ravi,
    I just retested this and your assertion does not appear to be true.
I did the following:

rename Wrapper.exe TestService.exe
TestService -i ..\conf\wrapper.conf
net start TestWrapper
<verified that it was running>
net stop TestWrapper
TestService -r ..\conf\wrapper.conf

    Everything worked perfectly.   Did he rename the Wrapper.exe
after having installed the service?  If so then that is nothing to do with
the Wrapper?  When any service is installed, it places an entry into
the system registry.  You should be able to find it by running "regedit"
and then looking at the following key:
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<your service name>

    If I rename the Wrapper binary AFTER having installed it and then
attempt to start the service, I get the following message from the
service manager:
--
The service name is invalid.
More help is available by typing NET HELPMSG 2185.
--
    Attempting to start from the service control panel also gives the
same error.

    Can you verify that you are not seeing a different problem.   You
should not have any problems renaming the Wrapper binary.   You
can not rename the Wrapper.DLL file currently.  That is because of
the way the Java code loads the native library.   But if the Java code
can not locate the native library the program should still work but it
will lose the ability to prevent a JVM restart when the user logs out.

Cheers,
Leif


Ravi Shankar wrote:

> Hi Leif,
>  
> I understood the mistake, it is a mistake from our side.
>  
> To make the filenames generic and compatible with our application, 
> somebody changed the name of Wrapper.exe as ServerStart.exe!. And 
> somewhere in the dll reference is made in your code to Wrapper.exe 
> only. When I changed it back, I got it working!!!
>  
> Thanks anyway.
>  
> Regards,
> Ravi
>