| Re: Error 1053: The service did not respond to the start or control request in a timely fashion. [message #71836] |
Sat, 18 January 2003 01:41 |
Raj
Messages: 411
Registered: November 1998
|
Senior Member |
|
|
This article was previously published under Q278712
SYMPTOMS 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.
CAUSEThis behavior may occur because the error message is displayed when the service takes more than three minutes to respond. 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.
RESOLUTIONTo 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.
For more information about troubleshooting Service Control Manager errors, please refer to the Microsoft Knowledge Base.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
