Windows Server 2008 Task Scheduler taskeng.exe lingeringcan server 2008's task scheduler run a php file?Task Scheduler not able to execute .vbs scripts successfullyTask Scheduler on EC2 Windows Server 2008 R2Windows Server 2008 Task Scheduler Tasks Not ExecutingTask Scheduler Library Windows Server 2008Windows Server 2008 - Task Scheduler and Running Scripts every minute.cmd in Windows Server 2008 task scheduler w/o highest privilegesWindows 2003 Task Scheduler Not running in foregroundWindows Server 2008 R2 Task Scheduler Powershell issueWindows Server 2008 R2 Task Scheduler Not Executing
Syntax Error with 'if'
If my Scout rogue has used his full movement on his turn, can he later use the reaction from the Skirmisher feature to move again?
Why does the A-4 Skyhawk sit nose-up when on ground?
Pull-up sequence accumulator counter
Is there a short way to compare many values mutually at same time without using multiple 'and's?
What happens when your group is victim of a surprise attack but you can't be surprised?
Architecture of networked game engine
Procedurally generate regions on island
Are Finite Automata Turing Complete?
First-year PhD giving a talk among well-established researchers in the field
Alternatives to arc
Alphabet completion rate
"It will become the talk of Paris" - translation into French
Are there any vegetarian astronauts?
Going to get married soon, should I do it on Dec 31 or Jan 1?
Why is Madam Hooch not a professor?
Why is the Turkish president's surname spelt in Russian as Эрдоган, with г?
What are the penalties for overstaying in USA?
C-152 carb heat on before landing in hot weather?
How to append a matrix element by element?
Does the posterior necessarily follow the same conditional dependence structure as the prior?
What is this blowing instrument used in the acoustic cover of "Taekwondo" by "Walk off the Earth"?
Does squid ink pasta bleed?
What do you call the action of someone tackling a stronger person?
Windows Server 2008 Task Scheduler taskeng.exe lingering
can server 2008's task scheduler run a php file?Task Scheduler not able to execute .vbs scripts successfullyTask Scheduler on EC2 Windows Server 2008 R2Windows Server 2008 Task Scheduler Tasks Not ExecutingTask Scheduler Library Windows Server 2008Windows Server 2008 - Task Scheduler and Running Scripts every minute.cmd in Windows Server 2008 task scheduler w/o highest privilegesWindows 2003 Task Scheduler Not running in foregroundWindows Server 2008 R2 Task Scheduler Powershell issueWindows Server 2008 R2 Task Scheduler Not Executing
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
We run several simple python scripts periodically on our servers using Windows Task Scheduler. The scripts are extremely simple, and grab statistics like the Disk Space and the CPU Percentage and log them.
Occasionally we notice we cannot edit, rename or delete the script. When we look in the task manager we see that the script has finished successfully, but there are one or two instances of taskeng.exe still lingering.
We have searched high and low trying to see if there is a way we should be exiting our python script to prevent this, but it only seems to happen 1 in 100 runs of the script, which makes us think it's a Task Scheduler issue.
Someone has suggested that we just kill taskeng.exe when our script is done, but this seems like a sledgehammer solution ( and we sometimes have two scripts run at the same time. )
Hopefully someone here has come across this issue before!
Lingering taskeng.exe Example
windows-server-2008 task-scheduler
edited Oct 20 '15 at 9:18
MadHatter
71k11 gold badges150 silver badges207 bronze badges
asked Oct 19 '15 at 16:38
David GannonDavid Gannon
11 bronze badge
add a comment |
We run several simple python scripts periodically on our servers using Windows Task Scheduler. The scripts are extremely simple, and grab statistics like the Disk Space and the CPU Percentage and log them.
Occasionally we notice we cannot edit, rename or delete the script. When we look in the task manager we see that the script has finished successfully, but there are one or two instances of taskeng.exe still lingering.
We have searched high and low trying to see if there is a way we should be exiting our python script to prevent this, but it only seems to happen 1 in 100 runs of the script, which makes us think it's a Task Scheduler issue.
Someone has suggested that we just kill taskeng.exe when our script is done, but this seems like a sledgehammer solution ( and we sometimes have two scripts run at the same time. )
Hopefully someone here has come across this issue before!
Lingering taskeng.exe Example
windows-server-2008 task-scheduler
edited Oct 20 '15 at 9:18
MadHatter
71k11 gold badges150 silver badges207 bronze badges
asked Oct 19 '15 at 16:38
David GannonDavid Gannon
11 bronze badge
add a comment |
We run several simple python scripts periodically on our servers using Windows Task Scheduler. The scripts are extremely simple, and grab statistics like the Disk Space and the CPU Percentage and log them.
Occasionally we notice we cannot edit, rename or delete the script. When we look in the task manager we see that the script has finished successfully, but there are one or two instances of taskeng.exe still lingering.
We have searched high and low trying to see if there is a way we should be exiting our python script to prevent this, but it only seems to happen 1 in 100 runs of the script, which makes us think it's a Task Scheduler issue.
Someone has suggested that we just kill taskeng.exe when our script is done, but this seems like a sledgehammer solution ( and we sometimes have two scripts run at the same time. )
Hopefully someone here has come across this issue before!
Lingering taskeng.exe Example
windows-server-2008 task-scheduler
edited Oct 20 '15 at 9:18
MadHatter
71k11 gold badges150 silver badges207 bronze badges
asked Oct 19 '15 at 16:38
David GannonDavid Gannon
11 bronze badge
We run several simple python scripts periodically on our servers using Windows Task Scheduler. The scripts are extremely simple, and grab statistics like the Disk Space and the CPU Percentage and log them.
Occasionally we notice we cannot edit, rename or delete the script. When we look in the task manager we see that the script has finished successfully, but there are one or two instances of taskeng.exe still lingering.
We have searched high and low trying to see if there is a way we should be exiting our python script to prevent this, but it only seems to happen 1 in 100 runs of the script, which makes us think it's a Task Scheduler issue.
Someone has suggested that we just kill taskeng.exe when our script is done, but this seems like a sledgehammer solution ( and we sometimes have two scripts run at the same time. )
Hopefully someone here has come across this issue before!
Lingering taskeng.exe Example
windows-server-2008 task-scheduler
windows-server-2008 task-scheduler
edited Oct 20 '15 at 9:18
MadHatter
71k11 gold badges150 silver badges207 bronze badges
asked Oct 19 '15 at 16:38
David GannonDavid Gannon
11 bronze badge
edited Oct 20 '15 at 9:18
MadHatter
71k11 gold badges150 silver badges207 bronze badges
asked Oct 19 '15 at 16:38
David GannonDavid Gannon
11 bronze badge
edited Oct 20 '15 at 9:18
MadHatter
71k11 gold badges150 silver badges207 bronze badges
edited Oct 20 '15 at 9:18
MadHatter
71k11 gold badges150 silver badges207 bronze badges
edited Oct 20 '15 at 9:18
MadHatter
71k11 gold badges150 silver badges207 bronze badges
71k11 gold badges150 silver badges207 bronze badges
asked Oct 19 '15 at 16:38
David GannonDavid Gannon
11 bronze badge
asked Oct 19 '15 at 16:38
David GannonDavid Gannon
11 bronze badge
asked Oct 19 '15 at 16:38
David GannonDavid Gannon
11 bronze badge
11 bronze badge
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I hate to agree with the sledgehammer solution but unless you want to debug out the script to see if something isn't exiting properly (a drive dismount, or network resource failure, assuming you accounted for failures in the functions), I would start the script off with killing any existing scheduler processes.
It is a sledgehammer solution but I've had to do it with known good vendor products that sometimes would call a resource that didn't respond properly, thus hanging up a backup job. To prevent the jobs from overlapping, this was the only solution and honestly, even when they came out with a fix, we didn't bother, because it's a legit workaround that so far has had no negative impacts.
Else, what's the script doing that maybe isn't completing?
-Chase
p.s. I've had MSFT Premier support even accept this solution for SharePoint scheduled import/export batch processes where they'd hang and we had to kill scheduler.
answered Oct 19 '15 at 16:53
ChaseChase
3891 silver badge8 bronze badges
Hi Chase, Thank you for the speedy reply! If it were just one script having the problem, I probably would have called it a day and just killed that task. However it is several different scripts, which range in function. One for instance calls a python library method "ctypes.windll.kernel32.GetDiskFreeSpaceExW" and then logs it to disk. The other calls "wmic cpu get loadpercentage" from the command line and logs its response to disk. My worry is that killing taskeng.exe means that I could accidentally kill a properly running windows task instead of a lingering one. Regards, David
– David Gannon
Oct 19 '15 at 17:05
add a comment |
Putting the answer from our dedicated server support here in case it helps anyone else out in the future.
Chase's answer is extremely helpful, it just sadly wouldn't work in our case, as we sometimes have multiple tasks running at the same time, and we could end up killing the wrong instance of taskeng.exe.
It was suggested within Task Scheduler that we enable the option "Stop the existing Instance" in the Settings tab under the properties of the task.
So far this has seemed to solve the problem.
Regards,
David
answered Oct 20 '15 at 9:02
David GannonDavid Gannon
11 bronze badge
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f729997%2fwindows-server-2008-task-scheduler-taskeng-exe-lingering%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I hate to agree with the sledgehammer solution but unless you want to debug out the script to see if something isn't exiting properly (a drive dismount, or network resource failure, assuming you accounted for failures in the functions), I would start the script off with killing any existing scheduler processes.
It is a sledgehammer solution but I've had to do it with known good vendor products that sometimes would call a resource that didn't respond properly, thus hanging up a backup job. To prevent the jobs from overlapping, this was the only solution and honestly, even when they came out with a fix, we didn't bother, because it's a legit workaround that so far has had no negative impacts.
Else, what's the script doing that maybe isn't completing?
-Chase
p.s. I've had MSFT Premier support even accept this solution for SharePoint scheduled import/export batch processes where they'd hang and we had to kill scheduler.
answered Oct 19 '15 at 16:53
ChaseChase
3891 silver badge8 bronze badges
Hi Chase, Thank you for the speedy reply! If it were just one script having the problem, I probably would have called it a day and just killed that task. However it is several different scripts, which range in function. One for instance calls a python library method "ctypes.windll.kernel32.GetDiskFreeSpaceExW" and then logs it to disk. The other calls "wmic cpu get loadpercentage" from the command line and logs its response to disk. My worry is that killing taskeng.exe means that I could accidentally kill a properly running windows task instead of a lingering one. Regards, David
– David Gannon
Oct 19 '15 at 17:05
add a comment |
I hate to agree with the sledgehammer solution but unless you want to debug out the script to see if something isn't exiting properly (a drive dismount, or network resource failure, assuming you accounted for failures in the functions), I would start the script off with killing any existing scheduler processes.
It is a sledgehammer solution but I've had to do it with known good vendor products that sometimes would call a resource that didn't respond properly, thus hanging up a backup job. To prevent the jobs from overlapping, this was the only solution and honestly, even when they came out with a fix, we didn't bother, because it's a legit workaround that so far has had no negative impacts.
Else, what's the script doing that maybe isn't completing?
-Chase
p.s. I've had MSFT Premier support even accept this solution for SharePoint scheduled import/export batch processes where they'd hang and we had to kill scheduler.
answered Oct 19 '15 at 16:53
ChaseChase
3891 silver badge8 bronze badges
Hi Chase, Thank you for the speedy reply! If it were just one script having the problem, I probably would have called it a day and just killed that task. However it is several different scripts, which range in function. One for instance calls a python library method "ctypes.windll.kernel32.GetDiskFreeSpaceExW" and then logs it to disk. The other calls "wmic cpu get loadpercentage" from the command line and logs its response to disk. My worry is that killing taskeng.exe means that I could accidentally kill a properly running windows task instead of a lingering one. Regards, David
– David Gannon
Oct 19 '15 at 17:05
add a comment |
I hate to agree with the sledgehammer solution but unless you want to debug out the script to see if something isn't exiting properly (a drive dismount, or network resource failure, assuming you accounted for failures in the functions), I would start the script off with killing any existing scheduler processes.
It is a sledgehammer solution but I've had to do it with known good vendor products that sometimes would call a resource that didn't respond properly, thus hanging up a backup job. To prevent the jobs from overlapping, this was the only solution and honestly, even when they came out with a fix, we didn't bother, because it's a legit workaround that so far has had no negative impacts.
Else, what's the script doing that maybe isn't completing?
-Chase
p.s. I've had MSFT Premier support even accept this solution for SharePoint scheduled import/export batch processes where they'd hang and we had to kill scheduler.
answered Oct 19 '15 at 16:53
ChaseChase
3891 silver badge8 bronze badges
I hate to agree with the sledgehammer solution but unless you want to debug out the script to see if something isn't exiting properly (a drive dismount, or network resource failure, assuming you accounted for failures in the functions), I would start the script off with killing any existing scheduler processes.
It is a sledgehammer solution but I've had to do it with known good vendor products that sometimes would call a resource that didn't respond properly, thus hanging up a backup job. To prevent the jobs from overlapping, this was the only solution and honestly, even when they came out with a fix, we didn't bother, because it's a legit workaround that so far has had no negative impacts.
Else, what's the script doing that maybe isn't completing?
-Chase
p.s. I've had MSFT Premier support even accept this solution for SharePoint scheduled import/export batch processes where they'd hang and we had to kill scheduler.
answered Oct 19 '15 at 16:53
ChaseChase
3891 silver badge8 bronze badges
answered Oct 19 '15 at 16:53
ChaseChase
3891 silver badge8 bronze badges
answered Oct 19 '15 at 16:53
ChaseChase
3891 silver badge8 bronze badges
answered Oct 19 '15 at 16:53
ChaseChase
3891 silver badge8 bronze badges
3891 silver badge8 bronze badges
Hi Chase, Thank you for the speedy reply! If it were just one script having the problem, I probably would have called it a day and just killed that task. However it is several different scripts, which range in function. One for instance calls a python library method "ctypes.windll.kernel32.GetDiskFreeSpaceExW" and then logs it to disk. The other calls "wmic cpu get loadpercentage" from the command line and logs its response to disk. My worry is that killing taskeng.exe means that I could accidentally kill a properly running windows task instead of a lingering one. Regards, David
– David Gannon
Oct 19 '15 at 17:05
add a comment |
Hi Chase, Thank you for the speedy reply! If it were just one script having the problem, I probably would have called it a day and just killed that task. However it is several different scripts, which range in function. One for instance calls a python library method "ctypes.windll.kernel32.GetDiskFreeSpaceExW" and then logs it to disk. The other calls "wmic cpu get loadpercentage" from the command line and logs its response to disk. My worry is that killing taskeng.exe means that I could accidentally kill a properly running windows task instead of a lingering one. Regards, David
– David Gannon
Oct 19 '15 at 17:05
Hi Chase, Thank you for the speedy reply! If it were just one script having the problem, I probably would have called it a day and just killed that task. However it is several different scripts, which range in function. One for instance calls a python library method "ctypes.windll.kernel32.GetDiskFreeSpaceExW" and then logs it to disk. The other calls "wmic cpu get loadpercentage" from the command line and logs its response to disk. My worry is that killing taskeng.exe means that I could accidentally kill a properly running windows task instead of a lingering one. Regards, David
– David Gannon
Oct 19 '15 at 17:05
Hi Chase, Thank you for the speedy reply! If it were just one script having the problem, I probably would have called it a day and just killed that task. However it is several different scripts, which range in function. One for instance calls a python library method "ctypes.windll.kernel32.GetDiskFreeSpaceExW" and then logs it to disk. The other calls "wmic cpu get loadpercentage" from the command line and logs its response to disk. My worry is that killing taskeng.exe means that I could accidentally kill a properly running windows task instead of a lingering one. Regards, David
– David Gannon
Oct 19 '15 at 17:05
add a comment |
Putting the answer from our dedicated server support here in case it helps anyone else out in the future.
Chase's answer is extremely helpful, it just sadly wouldn't work in our case, as we sometimes have multiple tasks running at the same time, and we could end up killing the wrong instance of taskeng.exe.
It was suggested within Task Scheduler that we enable the option "Stop the existing Instance" in the Settings tab under the properties of the task.
So far this has seemed to solve the problem.
Regards,
David
answered Oct 20 '15 at 9:02
David GannonDavid Gannon
11 bronze badge
add a comment |
Putting the answer from our dedicated server support here in case it helps anyone else out in the future.
Chase's answer is extremely helpful, it just sadly wouldn't work in our case, as we sometimes have multiple tasks running at the same time, and we could end up killing the wrong instance of taskeng.exe.
It was suggested within Task Scheduler that we enable the option "Stop the existing Instance" in the Settings tab under the properties of the task.
So far this has seemed to solve the problem.
Regards,
David
answered Oct 20 '15 at 9:02
David GannonDavid Gannon
11 bronze badge
add a comment |
Putting the answer from our dedicated server support here in case it helps anyone else out in the future.
Chase's answer is extremely helpful, it just sadly wouldn't work in our case, as we sometimes have multiple tasks running at the same time, and we could end up killing the wrong instance of taskeng.exe.
It was suggested within Task Scheduler that we enable the option "Stop the existing Instance" in the Settings tab under the properties of the task.
So far this has seemed to solve the problem.
Regards,
David
answered Oct 20 '15 at 9:02
David GannonDavid Gannon
11 bronze badge
Putting the answer from our dedicated server support here in case it helps anyone else out in the future.
Chase's answer is extremely helpful, it just sadly wouldn't work in our case, as we sometimes have multiple tasks running at the same time, and we could end up killing the wrong instance of taskeng.exe.
It was suggested within Task Scheduler that we enable the option "Stop the existing Instance" in the Settings tab under the properties of the task.
So far this has seemed to solve the problem.
Regards,
David
answered Oct 20 '15 at 9:02
David GannonDavid Gannon
11 bronze badge
answered Oct 20 '15 at 9:02
David GannonDavid Gannon
11 bronze badge
answered Oct 20 '15 at 9:02
David GannonDavid Gannon
11 bronze badge
answered Oct 20 '15 at 9:02
David GannonDavid Gannon
11 bronze badge
11 bronze badge
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f729997%2fwindows-server-2008-task-scheduler-taskeng-exe-lingering%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
