BUG: ControlService API Fails with a GetLastError() of 1053

ID: Q202069


The information in this article applies to:


SYMPTOMS

If the ControlService() API is called simultaneously from different threads to stop running services, the function may fail and a call to GetLastError() may return 1053. This failure can occur even though the service reports its current status to the service control manager in a timely fashion.


STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.


MORE INFORMATION

When a service controller application decides to stop a running service, it calls ControlService() with SERVICE_CONTROL_STOP as the control code.

Some ControlService() calls may return successfully while others may fail. This error can occur, even if the threads calling ControlService() are in separate processes.

Additional query words: ControlService 1053 ERROR_SERVICE_REQUEST_TIMEOUT


Keywords          : kbKernBase kbNTOS400 kbSCM kbSDKPlatform kbService 
Version           : winnt:4.0
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: February 11, 1999