| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
If you use the Windows
...
service panel (services.msc) to start the JobScheduler service then please note:
- Windows only gives expects a service 30 seconds to startto be started within 30s.
- Normally, it this is enough time for the JobScheduler to start.
- It is possible that the Windows services dialog service panel displays the status paused when the JobScheduler needs requires more time to start.
- This could result in an error message such as:
Error 1053: The service did not respond to the start or control request in a timely fashion - Wait some seconds and refresh the Windows services dialog.
- In many cases after some more seconds the JobScheduler service moves to the status running.
- This could result in an error message such as:
- If the JobScheduler service is still continues to be paused then please look check the file ./logs/scheduler.log to find for the root cause.
- The most A common reason is that the JobScheduler has runs into problems when trying to establish the database connection.