BUG: ControlService API Fails with a GetLastError() of 1053
Article ID: 202069
Article Last Modified on 11/21/2006
APPLIES TO
- Microsoft Win32 Application Programming Interface, when used with:
This article was previously published under Q202069
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. This problem has been fixed on Microsoft Windows 2000 and later versions
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: kbbug kbkernbase kbpending kbscm kbservice KB202069