Solved

Scheduled Task ends "successfully" when it should not

Posted on 2013-11-04
3
191 Views
Last Modified: 2013-12-30
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
Comment
Question by:fmi_techsupport
  • 2
3 Comments
 
LVL 22

Expert Comment

by:yo_bee
ID: 39624039
What is the CMD supposed to do?
0
 

Author Comment

by:fmi_techsupport
ID: 39625171
Execute a python task which was meant to run for 18 hours and then terminate, and then be restarted at 05:00 again.
0
 
LVL 22

Accepted Solution

by:
yo_bee earned 500 total points
ID: 39625180
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

Backup Solution for AWS

Read about how CloudBerry Backup fully integrates your backups with Amazon S3 and Amazon Glacier to provide military-grade encryption and dramatically cut storage costs on any platform.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Windows Server Licensing - Home Server 6 74
How to host windows service on Windows Server 2008 3 75
Non-Destructive Way of Extending Volume 15 80
Rdp printing 5 26
Remote Desktop Protocol or RDP has become an essential tool in many offices. This article will show you how to set up an external IP to point directly to an RDP session. There are many reasons why this is beneficial but perhaps the top reason is con…
Problem Description: Actually I found the below issue with some customers after migration from SMS 2003 to SCCM 2007 and epically if they change site code, some clients may appear in the console with old site code, plus old sites still appearing …

679 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question