Ding, ding, ding! Give the man a ceegaarr! That was it. I didn’t see the one
on the trigger properties, and it was in fact set to 8 hours.
THANK YOU!!
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: [email protected] [mailto:[email protected]] On
Behalf Of Charles F Sullivan
Sent: Monday, February 1, 2016 2:15 PM
To: [email protected]
Subject: RE: [NTSysADM] Scheduled task weirdness
This is a question as much as it is an answer.
Does anyone know why it is that in Task Scheduler you see a “stop task….” entry
in two places? There’s one in the properties of the trigger as well as on the
Settings tab for the task. Did you check both?
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Melvin Backus
Sent: Monday, February 1, 2016 12:26 PM
To: [email protected]<mailto:[email protected]>
Subject: [NTSysADM] Scheduled task weirdness
Hi folks,
I’ve been debugging a process we run via scheduled task every night. Since it
deals with a variable size data set it runs for different periods every night
which is expected. However I discovered while I was reviewing logs that it
doesn’t always finish. It appears that a good portion of the time it’s getting
killed after 8 hours by the system. This has happened about a dozen times
since mid-December. The stop time is exactly 8 hours after the task started,
but the task is configured to run for up to 3 days before being stopped.
Any ideas on what might be going on or pointers on where to look for additional
info? My google results have shown a couple of similar questions but no
resolutions.
For now I’ve disabled the “Stop the task” portion so that it should run
indefinitely if needed.
Thanks
--------------------
Melvin Backus | Sr. Systems Engineer | Byers Engineering Company | 404.497.1565
Service Desk | 404-497-1599 | http://servicedesk.byers.com
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
