-1
I have multiple scheduled tasks set up on Windows 2008 Server. They are all running the same executable with different arguments (pointing to different config files). They (mostly) all have different start times. They have been running without issues for a couple years. About 3 weeks ago they began starting at their scheduled times and then ending 1 second later. The weird thing is that they are scheduled to run Mon thru Friday and are only exhibiting this behavior on Wednesday, Thursday and Friday. They run fine on Monday and Tuesday.
Also, it is not the same tasks failing each day. Some are starting and failing one day, and the next day they will start successfully. I should point out that the task is not failing with an error. It is starting on time and then completing during the same second (see screen shot of task history).
I have checked for any server updates that would have affected the task scheduler functionality, but none were applied. There were no code changes to the executable that would have caused the issue. I've also tried running these tasks using a different scheduler called Visual Cron. The same behavior occurred.
So it doesn't seem to a scheduler issue, but I'm out of ideas for what could be causing this issue. Anyone ever dealt with something similar? task history
So run the EXE from command line, etc. from the same server and from the same security context as the Task Scheduler scheduled task does. Look here for some clues as well although it sounds like whatever the process does logic wise is within the EXE but the same general rules would still apply: http://superuser.com/questions/1005192/problems-scheduling-a-task-on-windows7/1005216#1005216... Like a security issue, a working directory issue (maybe due to DLL, etc. being needed), a security context issue once the logic runs as this answer talks about, etc.
– Pimp Juice IT – 2016-09-28T21:08:21.497People are more likely to read your question if you format it so it is not a wall of text. Please read Markdown help and [edit] your question to add paragraphs and bullet points ...
– DavidPostill – 2016-09-29T11:13:43.310Yes, the jobs run fine from a command prompt and always work when manually ran from the task scheduler after the initial scheduled run/completion. – windwill – 2016-09-30T14:12:07.940
You could probably put some logging functions in the script. That way you know how far the script gets before it fails. It's possible that you script is being executing but just failing an instruction. – IronWilliamCash – 2016-09-30T15:04:00.193