On Windows Server 2003, we have an occasional condition where an application service fails to start immediately, and the service stays in the “Starting” state for 20 minutes, after which it times out and shuts down. If this happens on a reboot, then it is not possible to login to the server (even from the console) until the 20 minute timeout has elapsed. This service does not have any dependencies.
Is this normal behaviour, i.e. is it always the case that you cannot login until all automatic services have started or timed out?
Or is this likely to be a peculiarity of this particular application service?