First of all, some info:
- Windows Server 2008 Datacenter, 100% updated with Service Pack 2 and all the patches.
- I connect to it using "Remote Desktop Connection" (I don't now if this is relevant)
- I login using a user that is an administrator
The tasks in the Task Scheduler get triggered for a few days, then they don't do until I restart the operating system. Then they work again for a few days and stop, and so on.
When I open the Task Scheduler administrator, select any of the tasks, and the open the "history" tab below, I don't see any entries for the last events that should have happened, but didn't. I mean, no entries at all that would indicate that the task triggered or tried to trigger. In other words, as if the task had been totally ignored by the scheduler. All tasks seem to suffer the same.
When I open the Event Viewer, I don't see any useful information. No entries at all for all those events that never happened, no system error indications, nothing. I have checked all the relevant directories in the event viewer (the 5 windows logs and the "….\Microsoft\Windows\TaskScheduler" log. Nothing there that would explain what is wrong.
The "Task Scheduler" service started, thats for sure because the events happen for some time until they stop. Then, when they don't run anymore, I assume the service is still running but I'm not 100% sure because for some reason the stop/pause/restart/…./start commands in this service seem to be disabled (I don't know why), even though I have logged in as an administrator, so I can not try restarting the service so see of the events work again.
All other functions in the operating system seem to work fine, the RAM amount is fine, the server doesn't get unresponsive or any other bad symphtom.
Does anybody know what is the problem? I have been strugling with this failure for a long time, a year or more having to restart my server every few days.
Thanks in advance!
Best Answer
What stands out to me in your question is "...they work again for a few days and stop...". In my experience, these types of issues are usually related to security context.
Check to make sure the "Run whether user is logged on or not." radio button is checked. I would first suspect that you're logging in as the administrative user that the task runs under, and it's fine until your session is terminated.
If that is set properly, then check to make sure the task conditions (in Task Properties) are able to be met consistently.