- If you use the Windows services dialog (services.msc) to start the JobScheduler service then please note:
- Windows only gives a service 30 seconds to start.
- Normally, it is enough time for the JobScheduler to start.
- It is possible that the Windows services dialog displays the status paused when the JobScheduler needs more time to start.
- Wait some seconds and refresh the Windows services dialog.
- In most cases after some more seconds the JobScheduler service moves to the status running.
- If the JobScheduler service is still paused then please look check ./logs/scheduler.log to find the root cause.
- The most common reason is that the JobScheduler has problems to establish the database connection.
Overview
Content Tools