Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 200
  • Last Modified:

Scheduled Task ends "successfully" when it should not

The machine in question was rebooted on 11/1 @14:12 and relaunched a scheduled task with no specified end date or max hours of run time.  On 11/4 @ 13:07 it terminated with the message

Task Scheduler successfully completed task "\FMI\Client_CamelBakTo" , instance "{10e0905f-3f6b-4106-be1b-8e8fd5ecfc0f}" , action "C:\Windows\SYSTEM32\cmd.exe" with return code 0.

which indicates everything was a-OK.  The Event ID is 201, the Task Category is "Action completed".  The OpCode is 2.   The locale id is 1033.

Any insights as to why the task terminated?
0
fmi_techsupport
Asked:
fmi_techsupport
  • 2
1 Solution
 
yo_beeDirector of ITCommented:
What is the CMD supposed to do?
0
 
fmi_techsupportAuthor Commented:
Execute a python task which was meant to run for 18 hours and then terminate, and then be restarted at 05:00 again.
0
 
yo_beeDirector of ITCommented:
Do you see the task that is trigger in your Process list after the Trigger is initiated?
If so it seems to me that it is working correctly.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now