Service start timeout at reboot but works when system is totally up
Posted on 2004-08-26
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?