Re: NTSVC.OCX Help needed

From: Randy Birch (rgb_removethis_at_mvps.org)
Date: 10/22/04 

Date: Thu, 21 Oct 2004 23:52:38 -0400

<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>

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.

---------------

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) 

-- 
Randy Birch
MS MVP Visual Basic
http://vbnet.mvps.org/
"Paul Bobrowski" <nospam@msdiscussion.com> wrote in message
news:u4cVdBvtEHA.1272@TK2MSFTNGP12.phx.gbl...
: I'm currently running a precompiled version of ntsvc.ocx along with the
: sample application included in the archive.  These will install and run
fine
: as an NT service under Windows 2000.
:
: The problem I am having is that nothing I try to compile will start
: correctly.  All of the examples I have tried to create will compile,
install
: and uninstall just fine.  The issue is that when I try to run the service,
: it will start just fine; however, it will be closed about 30 seconds later
: stating that the service timed out.
:
: Here are two different error message I am getting:
:
: Run from the Services applet
:
: The <service display 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.
:
: and ran from NET START
:
: The service is not responding to the control function.
:
: More help is available by typing NET HELPMSG 2186.   -The help message
just
: says the the service control is responding.
:
:
: I am using VB6sp6 on Windows 2000, are there any known issues with this
: setup?  I also downloaded a sample app from planetsourcecode:
:
http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=14223&lngWId=1
: and it will install/uninstall, but it dies when I try to run it.
:
: This there something I'm missing?  The sample app used a Private Sub
: NTService1_Control(byVal Event as Long)  I know in VB6 that event is now
: reserved, but I can get it to compile.  All the sample app did was read a
: string along with the event variable into a statusbar control text display
: area.
:
: Can anyone offer some advice?  I've spent two days on this now, and I have
: yet to find a solution.
:
:
: Thanks in advance for any help.
:
:
: Paul Bobrowski
:
: