Task Execution is Aborted -No scheduled tasks run afterwards
Posted: Mon May 16, 2016 4:42 pm
Hi
I have a handful of processes that is scheduled to run each morning.
Occassionally, there is a problem, and Robotask just stops.
I: 5/12/2016 4:35:19 AM: Begin MedComToSQL
W: 5/12/2016 4:35:19 AM: Step "Run command-line utility: netsh winsock reset " is skipped
I: 5/12/2016 4:35:19 AM: Executing "14.Run "medComToSQLUI.exe ""
E: 5/12/2016 4:35:19 AM: An error occurred. Step #14 (Run "medComToSQLUI.exe ").
E: 5/12/2016 4:35:19 AM: Task execution is aborted
This happened over the weekend, and nothing has run since then.
To be clear, there are multiple processes that should run each morning.
NOTHING has run since the 12th.
I have an email that emails me if there are problems, but it is scheduled as well, and it didnt run.
The email doesnt get sent if there are no problems, so not getting an email is supposed to be good news.
Until i can get this fixed, I am going to send the email regardless, but that's not really solving the issue.
What I really want to do is figure out why robotask just stops. Any ideas?
This task is a DOS program. But if it failed to launch, and robotask knows enough to put that message in the log, should it not continue to run tasks.
I have a handful of processes that is scheduled to run each morning.
Occassionally, there is a problem, and Robotask just stops.
I: 5/12/2016 4:35:19 AM: Begin MedComToSQL
W: 5/12/2016 4:35:19 AM: Step "Run command-line utility: netsh winsock reset " is skipped
I: 5/12/2016 4:35:19 AM: Executing "14.Run "medComToSQLUI.exe ""
E: 5/12/2016 4:35:19 AM: An error occurred. Step #14 (Run "medComToSQLUI.exe ").
E: 5/12/2016 4:35:19 AM: Task execution is aborted
This happened over the weekend, and nothing has run since then.
To be clear, there are multiple processes that should run each morning.
NOTHING has run since the 12th.
I have an email that emails me if there are problems, but it is scheduled as well, and it didnt run.
The email doesnt get sent if there are no problems, so not getting an email is supposed to be good news.
Until i can get this fixed, I am going to send the email regardless, but that's not really solving the issue.
What I really want to do is figure out why robotask just stops. Any ideas?
This task is a DOS program. But if it failed to launch, and robotask knows enough to put that message in the log, should it not continue to run tasks.