RE: [Wrapper-user] Wrapper configuration problems

[Max S. <MSt...@li...>]

Leif,

  Sorry of all the confusion I caused with this e-mail thread. After careful
testing yesterday and review of my code, I determined that was an error in
my coding and nothing to do with the wrapper. What happened, is I modified
the bat file that shipped with wrapper to automatically start the service
after it is installed, but when I modified the service name in the wrapper
Config file I forgot to update the service name in the installation bat file
where I tried to start the service with a 'net start' command. That was the
reason why any time I tried to start the service it would give me an error,
service name is invalid.... Sorry again. Thanks for all of your time and
great explanations.

Max

-----Original Message-----
From: Leif Mortenson [mailto:le...@ta...] 
Sent: Friday, September 05, 2003 3:50 AM
To: wra...@li...
Subject: Re: [Wrapper-user] Wrapper configuration problems

Max,
Could you be more specific about what properties you modified and what
registry entries you had to manually delete? Also can you verify that you
are using the batch files shipped with the Wrapper to install and remove the
service?
Also what is the exact "problem" that you are having installing the
application as a service. Is it that your service name is invalid? If so
what
is the service name that you are trying to set?

I went back and retested the Wrapper's handling of the registry. When
you install the Wrapper, it adds an entry at the following location:
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\{servicename}

Then when you remove the service, the above entry is removed completely.
No garbage is left behind in the Registry. Rare for a "Windows program :-)

One exception is if you are logging to the Event Log. If and only if you
have the wrapper.syslog.loglevel property set to a level other than NONE,
a registry entry is added at the following location:
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\{
servicename}
This registry entry is created even if the application is run only as a
console
app. The registry entry is never deleted by the Wrapper as doing so would
cause the EventLog application to popup errors when attempting to view the
logged entries.

I am trying to get version 3.0.5 out the door and want to make sure that
I don't have an outstanding bug here.

Cheers,
Leif

Max Stolyarov wrote:

>Leif,
>
>    Thanks for the reply. I understand what you are saying and after more
>testing that I did yesterday, I am starting to feel that the configuration
>file is not an issue here. At this stage of testing I feel that the problem
>that I am experiencing has something to do with deployment and removal of
NT
>services. This is what I have done:
>
>1. I modified my wrapper Config properties (NT service properties).
>2. Ran your bat file to deploy the wrapper and install the service.
>3. Ran another bat file to stop and remove the service.
>4. Modified NT properties again in the wrapper configuration file
>5. Ran a bat file to deploy a service. At this point, I get an exception in
>the command windows that informs me that the service name is invalid.
>6. I poked around in the registry, and I feel that the bat file that I use
>to stop and remove the NT service is not doing a good job in removing the
>service entries from the registry. Am saying this because, when I removed
>couple of the registry entries related to the first service, I was able to
>deploy the new service. I will let you know, with more testing what
registry
>key remain and needs to be removed. If you have some idea what I need to
try
>please let me know. Thanks
>
>Thanks
>
>Max
>  
>




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user