ControlService Fails with 1053 (ERROR_SERVICE_REQUEST_TIMEOUT)

This article was previously published under Q215376
This article has been archived. It is offered "as is" and will no longer be updated.
If the ControlService() API is called simultaneously from different threads to stop multiple services, some services are stopped successfully while others eventually time out with an error 1053 (ERROR_SERVICE_REQUEST_TIMEOUT).
This problem occurs because a race condition in Services.exe causes a deadlock. This causes the stop request to time out.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
  • 152734 how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
Microsoft has confirmed that this is a problem in Windows NT 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.
4.00 mscs cluster group resources

Article ID: 215376 - Last Review: 12/05/2015 12:39:09 - Revision: 3.0

Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB215376