| Re: Error 1053: The service did not respond to the start or control request in a timely fashion. [message #69117] |
Thu, 01 November 2001 15:06  |
joe luu
Messages: 1
Registered: November 2001
|
Junior Member |
|
|
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.
CAUSE
This 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.
RESOLUTION
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.
For more information about troubleshooting Service Control Manager errors, please refer to the Microsoft Knowledge Base.
----------------------------------------------------------------------
|
|
|
|
| Re: Error 1053: The service did not respond to the start or control request in a timely fashion. [message #69242 is a reply to message #69117] |
Wed, 28 November 2001 04:41  |
Joshua Orvis
Messages: 1
Registered: November 2001
|
Junior Member |
|
|
When it doesn't start here's how you can still set the service from automatic to manual. If it times out while starting hit CNTRL+ALT+DEL and open the task manager. Click on the Processes tab and look for ORACLE.EXE. It's mem usage should be above 60MB if it is started properly but yours will probably be less than 10MB. Highlight it and then end the process. Now go back to you services list in windows and refresh it if necessary (Action --> Refresh). This should take away the status of "Starting" on the OracleService. Now you can right click on it and set it as manual.
Hope this helps...
----------------------------------------------------------------------
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
