This is a side effect of some other problem that causes the scheduler to hang or crash. Please ensure the following 1. "Show job status display" option is turned on - this could be used in development only but not in production 2. Al jobs are set to run synchronous and detached. For these that cannot run synchronous in a shared queue because they take a long time to run, place them into a separate queue so they do not block other jobs. 3. Jobs for different applications are assigned to different job queues. 4. If needed schedule periodic restart of 24x7 service using the following 2 commands in a batch fikle NET stop "24x7 Scheduler" NET start "24x7 Scheduler" : Some times the 24x7 don't work. The service is active but the job was not : executed and the schedule.log file is "freezed". : The only solutions to the problem is to restart the 24x7 Service. : Is this a know problem? Is there a solution? Have you some suggetions? : Tnx
|