Windows 2012R2
It starts at 9:54 PM. When it gets terminated it stops at 5:54 AM
The task is running 4 separate cmd scripts in succession. The first three
always trigger and run. The fourth is just a stats task but it doesn’t run
with things terminate, presumably because the 3 script is still running. I’m
not sure what particular parameters you’re looking for. The whole thing runs
as System since it only deals with local resources. If it would help I could
export the task and try posting it.
I haven’t tried adjusting the time yet. It’s fairly time sensitive because I’m
trying to run it to avoid a usage window. I can shift it a few minutes though,
I hadn’t thought about that. I also did run it via a manual trigger yesterday
and it completed. It doesn’t look like it exceeded the 8 hour run time however.
The history says it’s event 329, “Task stopping due to timeout reached”. Based
on time stamps, that particular script started at approximately 5 hours into
the task.
--
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 Andrew S. Baker
Sent: Monday, February 1, 2016 1:31 PM
To: ntsysadm <[email protected]>
Subject: Re: [NTSysADM] Scheduled task weirdness
Some questions:
What version of Windows?
What time does the task start, and what time does the task end?
What are the parameters of the task?
Does the same thing happen if you alter the start time of the task by a few
minutes in either direction?
What do the Scheduled Task Jobs say?
Regards,
ASB
http://XeeMe.com/AndrewBaker<http://xeeme.com/AndrewBaker>
Providing Expert Technology Consulting Services for the SMB market…
GPG: 1AF3 EEC3 7C3C E88E B0EF 4319 8F28 A483 A182 EF3A
On Mon, Feb 1, 2016 at 12:26 PM, Melvin Backus
<[email protected]<mailto:[email protected]>> wrote:
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<tel:404.497.1565>
Service Desk | 404-497-1599<tel: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.
