Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 971
  • Last Modified:

Service start timeout at reboot but works when system is totally up

Experts,

I have a program that runs as a service at startup.  On most machines, the program starts normally and everything is OK.  On a few machines though (Windows 2000), we have seen this effect:  When the program tries to start in service mode during system startup, a 7009 event error occurs saying that there was a connection timeout.  After the system is started, you can start the service with no problems.  My thought is that there is not a certain resource available at the time the service is starting, or it is conflicting with some other operating system service that is starting, but it is impossible to isolate.  My main questions is that has anyone seen this before, and is it possible to tell the system the sequence of the services starting so I can make this one the last one?  One thought was to use a command line service start, but will the execution of that happen after all the system has gone though most of its reboot?

Thanks

onemorecoke
0
onemorecoke
Asked:
onemorecoke
2 Solutions
 
adonis1976Commented:
r u using WINS server?
0
 
adonis1976Commented:
ok.. if there is any static entries in ur WINS db, this happens sometimes.. here is a link that might help u

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q177140

one more from jsi

http://www.jsiinc.com/SUBJ/tip4900/rh4935.htm
0
 
SyncubusCommented:
You could create a .BAT file to start the service and add a key to fire the .BAT to the HKLM/Software/Microsoft/Windows/Current Version/Run part of the registry.  This would let that service start last.

Set the service to be started manually.

StartServ.bat:
@Echo off
echo Starting ServiceName as service
net start ServiceName

Alternatively, you could just add the "net start servicename" to the registry and avoid the CMD window.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
Lee W, MVPTechnology and Business Process AdvisorCommented:
As something to think about - I had issues with network logins some time ago.  Could it be that the machines you are having this problem on all have the same Network Card?  Or perhaps are all Windows XP machines that boot up and don't wait for the network to fully start?  This could be related to your issue, especially if the service/program is network related.
0
 
mikeleebrlaCommented:
this will not get to the root of your problem but it will get the service started for you.

go to the services MMC
find the service in question,,
go to properties
go to the recovery tab
change first, second, and subsequent failure action to restart the service.
0
 
rogerfbCommented:
you can make the service depend on the last service to start.  http://support.microsoft.com/default.aspx?scid=kb;EN-US;193888
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now