START SERVICE AUTO

thierry sxm · Joined: 27 Dec 2005 Posts: 4 Location: saint martin

Everything work great but if I try to start service patronsoft dispatcher automatically , it never start , If I start it manually or by command line it is ok ! Please I need help to start firstspot auto after pwer shutdown.
Thank you
_________________
kiosknet@kiosknet.net

danielillu · Joined: 08 Dec 2005 Posts: 32 Location: Barcelona, Spain

just go to:
Start -> run... -> services.msc -> firstspot dispacher service [double click] -> and select "Start type" -> Automatic.
then dispatcher service will run automatically at startup.

alan · **Forum facilitator** Joined: 26 Sep 2003 Posts: 4435

thierry, have you used the instruction specified in readme.rtf (same as the one mentioned by danielillu)?
_________________
~ Patronsoft Limited ~

thierry sxm · Joined: 27 Dec 2005 Posts: 4 Location: saint martin

IT does not work even if I put automatic start ! Now it work only because I made batch file with sleep command like this :

sleep 300
net start "patronsoft service dispatcher"

If I don't do that the service try to stay but stay in starting mode and bug appear on 2 network (private and public ) connection .
_________________
kiosknet@kiosknet.net

alan · **Forum facilitator** Joined: 26 Sep 2003 Posts: 4435

We are still trying to reproduce your problem. BTW, what OS (and SP level) are you using?
_________________
~ Patronsoft Limited ~

thierry sxm · Joined: 27 Dec 2005 Posts: 4 Location: saint martin

Yhe os is windows 2000 server with last update from microsoft (I don't remenber now the Service pack number because I am writing this message from another computer) but I made all last updates from microsoft last week .
thank you
thierry
_________________
kiosknet@kiosknet.net

hans · **Forum facilitator** Joined: 14 May 2004 Posts: 63

If you have service timeout problem.

You can try the solution in this link:

http://groups.google.com/group/microsoft.public.win32.programmer.kernel/browse_frm/thread/b59cb01532def1ee/e6cf06107e498bd1?tvc=1#e6cf06107e498bd1

"From the posted content"
......
On Windows 2000, after 30 seconds, the SCM checks to see if the Service
Control Handler thread has returned from its SERVICE_CONTROL_STOP
processing. If the service control handler thread has not returned, the SCM
waits another 30 seconds. If the thread still has not returned, the SCM
assumes it is hung. In that case, you should see the following error in
the "System" event log.

Timeout (30000 milliseconds) waiting for a transaction response from the
<ServiceName> service.

with Event ID 7011 and Source "Service Control Manager".

This timeout can be configured on Windows 2000 globally by creating a
REG_DWORD registry value named "ServicesPipeTimeout" in milliseconds, under
the following registry key.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control

If this value is not present, the system assumes a default value of 30000
(30 seconds). This value is read from the registry at system startup, so
you will need to add/modify the value when you install your service and
then it should be honored the next time you reboot.
......
_________________
~ Patronsoft Limited ~

thierry sxm · Joined: 27 Dec 2005 Posts: 4 Location: saint martin

Work great thank you
_________________
kiosknet@kiosknet.net