From systems@work Limited

Infrastructure
Why Does The Task Scheduler Service Stop?
By systems@work SupportI have spoken to the Developers re the Task Scheduler Service issues you are having.
Mar 5, 2008 - 3:15:13 PM

In certain situations The Scheduler Service stops without warning.

This can happen whenever an error occurs which would (in an application environment) cause a Windows message box to pop-up (e.g. when a connection to the SMTP server drops out).

Our programmers strive to make the Task Scheduler Service as robust as possible, however if the Task Scheduler runs as a service, the pop-up messages are suppressed and therefore you can not see them on the Desktop. It should be noted that in most cases the cause of the Service stopping is not because of an error in time@work or expense@work.

If your Task Scheduler stops then we recommend that you kill the Scheduler Service.exe process in Windows Task Manager and restart the Task Scheduler service. This should be your first course of action in the event of an infrequent stoppage of the service.
 
If the Service continues to stop then in the short term we would recommend that you run the Task Scheduler as an Application so you can monitor the reason it is stopping. This is because if Task Scheduler runs in application mode, a pop-up message will appear if there are any problems and when you respond to it (interaction is still needed), the Task Scheduler will continue.

Once you experience or identify any pop up messages then you should
send screenshots to your support organisation for further advice.


© Copyright 2008 by systems@work Limited