We have a windows service that (sometimes) takes longer than 30 seconds to start. Is there a way to signal the the SCM to hold on, and not time out after 30 seconds in an automatic start? (we see this on a reboot only. After reboot, it usually takes 15-20 seconds to start)
If this isnt possible, i think we could spin off this functionality to a separate thread and have the service start quickly. Not sure this is the best idea, because our customers think that once it's started, it's immediately ready to go.
Thanks! :)
Edited bySteve1999Tuesday, June 10, 2008 6:44 PMreword