Re: NTSVC.OCX Help needed

From: Paul Bobrowski (nospam_at_msdiscussion.com)
Date: 10/22/04 

Date: Fri, 22 Oct 2004 15:14:29 -0400

----- Original Message -----
From: "Randy Birch" <rgb_removethis@mvps.org>

> <wild shot> See if the Logical Disk Manager Administrative service is set
to
> startup automatically, and if so, set it back to the default setting of
> Manual. (Q307309) </wild shot>

Nope, even crossed by fingers while I check and it was set to Manual and
wasn't started.

> Different approach ...
>
> How are you testing the startup of the service ... by rebooting or via the
> mmc services snap-in? The latter has an issue, albeit takes longer than
you
> are claiming for the problem to appear ...
>
> Q278712
>
> "When you use the Services snap-in to start a local service on a Microsoft
> Windows 2000-based computer, a Progress dialog box is displayed. If the
> service does not start in the three-minute time period set for this
Progress
> dialog box, the snap-in may cause your system to display the following
error
> message: Error 1053: The service did not respond to the start or control
> request in a timely fashion."
>
> The "cause" is stated as "This arbitrary time limit had been set with the
> intention that the user or administrator should be advised of the service
> status when this time limit is reached. However, the wording of the
message
> may give the impression to the user that the service is unable to start,
> when in fact the service may simply be taking a very long time to start.
The
> preceding error message is misleading because the service may still be in
a
> Start Pending state."
>
> The workaround given is: "To work around this behavior, you must clear the
> error message and continue to check for the service to start. If the
service
> does not start, you must check the System event log for Service Control
> Manager errors related to the service that is being monitored. If no error
> is posted to the event log, the service should eventually start."
>
> --------------------
>
> Another MSDN page gives the timeout as 125 seconds.
>
> Q307806
>
> The Microsoft Management Console (MMC) Services snap-in will wait up to
125
> seconds for a service control operation to finish. If the operation has
not
> completed within this time limit, the following error message will appear:
> Error 1053: The service did not respond to the start or control request in
a
> timely fashion.
> NOTE: This error message does not indicate that an error has actually
> occurred within the service. It simply means that the Services snap-in has
> timed out. The service process will continue to run until the operation
has
> completed.
>
> This behavior is by design.
>
> The MMC Services snap-in can be used to control services. This snap-in
> allows a system administrator to start, stop, pause, resume, or restart a
> service.
>
> When any control operation is initiated, the Services snap-in displays a
> progress dialog box with the title "Service Control". If a service
requires
> a significant amount of time to process an operation, the progress bar
will
> slowly increment as the Services snap-in waits for the operation to
finish.
> After 125 seconds, the progress bar will be full and the Services snap-in
> will display the error 1053 (ERROR_SERVICE_REQUEST_TIMEOUT) message. The
> service process itself will continue its operation as usual even after the
> error message has appeared.
>
> The 125-second timeout within the Services snap-in is a hard-coded limit
and
> cannot be changed through the registry.
>
> The Service Control dialog box contains a Close button. If the dialog box
is
> closed before the wait limit has expired, the error message will not be
> displayed.
>
> ---------------

I was using the MMC Service Snap-in; however, after reading your message I
went back and tested the services by setting them to automatic startup and
rebooting. Both my server and SimpleService (code in another branch of this
thread) started up and ran like they were supposed to. I was even able to
connect to the server with the client from a different PC. However, both
applications were shutdown and the same two error message are appearing in
the System Section of the Event log. The first is the Error 1053, and the
second isn't listed in the articles you posted but it says the service was
terminated after 30000 milliseconds because it didn't respond to a startup
or control request.

Startup from the MMC Service Snap-in will bring up the progressbar box. If
I close that window using the standard "X" button on the form, I won't get a
prompt with a startup error; however, the application is still terminated
along with the same two error entries in the system event log. It still
seems to me that the NTService_Control Event is never firing as my
SimpleService never has the label which displays the control codes display
them. I'll have to keep playing with this, but it looks like this is the
cause from as far as I can tell. I just can't figure out why is isn't
firing.

> Event 7000 (The Service name service failed to start due to the following
> error: The service did not respond to the start or control request in a
> timely fashion) will also occur if the machine has a redirected "Documents
> and Settings" folder (Q315194)

Unfortuately the Documents and Settings folder is located on the only drive
and partition in the system, in the standard C:\Documents and Settings. I
also testing the services on a Windows 2000 Server, which I control and use
for development and testing and it is experiencing the same behavior as the
Windows 2000 Professional Laptop.