Re: start service with parameters on restart

i've rebooted the server with the registry hack in place.

the service is still coming up listening on the default port and ignoring
the passed parameter.

"so why spend so much time on this minor point" you ask.

well, for a start your suggested solution does not work.

in addition, your explanation of why it didn't work was a load of rubbish.
if i change the value of ImagePath to a path that doesn't exist the service
manager applies the new value immediately and complains loudly.

which leaves me exactly where i started, except with fourteen levels of
nested comments going nowhere.

moving on, since i can start the service using sc.exe, is there a way to run
sc.exe at boot time without having to connect?


"Pegasus (MVP)" wrote:

See below.

"exotericist" <nospamthanks@xxxxxxxxxxx> wrote in message
news:2808178F-0750-43BA-B95E-4EDA7CD0D836@xxxxxxxxxxxxxxxx
but that's not true.

opening the properties dialog displays the new values. it must have got
them
by reading the registry.
*** Correct.

or are you saying that there are two entirely separate processes at work,
one of which reads the registry in real time to display the values to the
user, and the other that applies the values it got when the application
started?
*** Correct.

if so, that's beyond bad design and into wilful ineptitude.
*** Maybe, but I consider it risky to make such a statement
*** without being fully aware of the underlying design constraints.
*** Keep in mind Microsoft's advice on registry hacks:
*** a) You make them at your own risk, and
*** b) You must reboot the machine to make them effective.
*** Anyway, I gave you an easy way to deal with the issue,
*** so why spend so much time on this minor point?

"Pegasus (MVP)" wrote:

Many applications and many Windows components read the
registry at startup time only. When you hack the registry directly
then you need to make them aware of the change. This is by
design.


"exotericist" <nospamthanks@xxxxxxxxxxx> wrote in message
news:5A785C40-0E95-4010-BE0C-BC8AAC886283@xxxxxxxxxxxxxxxx
[quote]service start process won't recognise any changes made directly
to
the
registry[/quote]

why, then, does the displayed "path to executable" change?

is this a bug?


"Pegasus (MVP)" wrote:

It appears that the service start process won't recognise any changes
made directly to the registry. You can probably get around the problem
by following this sequence:
1. Use sc.exe to disable the service.
2. Make the registry change.
3. Use sc.exe to enable the service.
4. Start the service.
The syntax for sc.exe is as follows:
sc config NameOfService start= disabled
sc config NameOfService start= manual

The service name must be the short name, not the "DisplayName".
Note the space after the "=".


"exotericist" <nospamthanks@xxxxxxxxxxx> wrote in message
news:8BBC9468-CFDC-4A51-9848-890E10CC4B2B@xxxxxxxxxxxxxxxx
sorry, i was leaving the office, i should have put more detail in.

the parameter is a port number, to which the client connects.

(a small complication is that if two services come up with the same
port
number both are broken and the machine needs to be restarted)

if a service is started with no parameters, either automatically or
by
clicking start in the service manager, it uses the default port
1526.

starting the service with a parameter of "-nIS1527" tells the
service
to
use
port 1527 instead.

i applied your suggested change, adding the parameter to the image
path
and
starting the service.

when i tried to communicate with the service on the non-default port
it
wouldn't.

i could communicate over port 1526, though, suggesting that the
parameter
was not being passed.

thus "no joy."


"Pegasus (MVP)" wrote:

"No joy" sounds great but you need to be just a little more
specific, perhaps by posting
- What exactly you did with your parameters;
- How you checked what you did with your parameters;
- What you did with your service;
- How you determined that it did not work.


"exotericist" <nospamthanks@xxxxxxxxxxx> wrote in message
news:D90B5E32-8EA2-4ECC-B8CC-7230EAB4991D@xxxxxxxxxxxxxxxx
tried it, no joy.

e.

"Pegasus (MVP)" wrote:

Plug the parameter into ImagePath field via regedit, then start
the
service.
Example:

ImagePath="C:\Program Files\RealVNC\WinVNC\winvnc.exe" -nIS1527


"exotericist" <nospamthanks@xxxxxxxxxxx> wrote in message
news:45F80102-91F7-4E59-8D44-CBE77170142F@xxxxxxxxxxxxxxxx
specifically, i need to start the service as if i'd typed
"-nIS1527"
in
the
"Start Parameters" textbox.

i can't see how that relates to the W32Time registry keys.

many thanks,
e.

"Pegasus (MVP)" wrote:


"exotericist" <nospamthanks@xxxxxxxxxxx> wrote in message
news:4210AAC2-EAF6-4D94-B5E3-2F4E95D9852D@xxxxxxxxxxxxxxxx
i'm charged with maintaining an application which has
multiple
listener
services.

the first service can be set to auto.

subsequent services need to be passed a parameter to start.

in 2003 i've used sc.exe to pass a parameter to a service
on
startup
and
this works fine. i could set it so that the services were
started
by
the
act
of logging in.

however, i'd like the services to come up automatically on
restart
without
the need for user intervention, since that's what services
are
supposed
to
do.

my question is, therefore, the one in the title:

how can i start a service in windows server 2003 on machine
restart
and
pass
it a parameter?

many thanks,
e.

Have a look at the Windows Time service. It starts
automatically
at
boot
time and it uses parameters.
HKLM\SYSTEM\CurrentControlSet\Services\W32Time


















.

Relevant Pages

  • Re: start service with parameters on restart
    ... Make the registry change. ... the parameter is a port number, ... "Pegasus (MVP)" wrote: ...
    (microsoft.public.windows.server.general)
  • Re: Serial Port Application
    ... Can the registry be viewed from a Windows CE image? ... drivers which are actually active. ... >> Although the serial com port I use is defined under. ... I have created a new serial test program ...
    (microsoft.public.windowsce.app.development)
  • Re: Cannot Remote Desktop to home PC after installing XP SP3
    ... Remote Desktop unless a registry tweak is made. ... Are you connecting from a client which runs rdp 6.x? ... machine or port). ...
    (microsoft.public.windows.terminal_services)
  • Re: Using environment variables in roaming profiles....
    ... then write your own variable into the registry! ... "Pegasus (MVP)" wrote: ... When I amend the key and log out, it does create a profile directory ...
    (microsoft.public.windowsxp.general)
  • Re: users cant change password
    ... be set in the registry somewhere? ... Pegasus (MVP) wrote: ... the same information by typing this command at a Command ...
    (microsoft.public.win2000.general)
Loading