Windows scheduled tasks fail with 0x1, don't log errors
I have three Python scripts running overnight as scheduled tasks on a Windows Server 2008 VM. I can run them manually with no problems. But when I look at the Task Scheduler each morning, the first has run successfully and the subsequent two returned 0x1. I added an exception handler to all three scripts to log the traceback, hoping to find the guilty operation. I tested the handler by manually raising an Exception which was working fine. However, when I checked the next day no log had been created, meaning the script either never ran or didn't actually throw an error. Can anyone shed any light on what exactly 0x1 means, or if there's a situation in which the script would run but still return that?
For what it's worth, this is the batch file that calls the script:
@echo off
"E:ScriptsBackupcreate_backup.py"
python windows-server-2008 windows-task-scheduler
edited May 26 at 1:25
fixer1234
17.7k144581
asked Mar 18 '13 at 18:08
Rob
1993413
add a comment |
I have three Python scripts running overnight as scheduled tasks on a Windows Server 2008 VM. I can run them manually with no problems. But when I look at the Task Scheduler each morning, the first has run successfully and the subsequent two returned 0x1. I added an exception handler to all three scripts to log the traceback, hoping to find the guilty operation. I tested the handler by manually raising an Exception which was working fine. However, when I checked the next day no log had been created, meaning the script either never ran or didn't actually throw an error. Can anyone shed any light on what exactly 0x1 means, or if there's a situation in which the script would run but still return that?
For what it's worth, this is the batch file that calls the script:
@echo off
"E:ScriptsBackupcreate_backup.py"
python windows-server-2008 windows-task-scheduler
edited May 26 at 1:25
fixer1234
17.7k144581
asked Mar 18 '13 at 18:08
Rob
1993413
4
A quick search seems to indicate that this can be caused by not specifying the correct working directory. When testing your setup, did you try to invoke the task execution through the task scheduler (there's a Run option for tasks in the library)?
– Der Hochstapler
Mar 18 '13 at 18:11
1
Oliver, thanks for the tip, that does sound exactly like what I'm experiencing. I updated the script path to exclude the current working directory, instead specifying it in "Start in". When I run the task nothing visibly happens in the scheduler (I would expect the status to be "Running..."), but eventually it completes. Thanks again!
– Rob
Mar 18 '13 at 19:33
add a comment |
I have three Python scripts running overnight as scheduled tasks on a Windows Server 2008 VM. I can run them manually with no problems. But when I look at the Task Scheduler each morning, the first has run successfully and the subsequent two returned 0x1. I added an exception handler to all three scripts to log the traceback, hoping to find the guilty operation. I tested the handler by manually raising an Exception which was working fine. However, when I checked the next day no log had been created, meaning the script either never ran or didn't actually throw an error. Can anyone shed any light on what exactly 0x1 means, or if there's a situation in which the script would run but still return that?
For what it's worth, this is the batch file that calls the script:
@echo off
"E:ScriptsBackupcreate_backup.py"
python windows-server-2008 windows-task-scheduler
edited May 26 at 1:25
fixer1234
17.7k144581
asked Mar 18 '13 at 18:08
Rob
1993413
I have three Python scripts running overnight as scheduled tasks on a Windows Server 2008 VM. I can run them manually with no problems. But when I look at the Task Scheduler each morning, the first has run successfully and the subsequent two returned 0x1. I added an exception handler to all three scripts to log the traceback, hoping to find the guilty operation. I tested the handler by manually raising an Exception which was working fine. However, when I checked the next day no log had been created, meaning the script either never ran or didn't actually throw an error. Can anyone shed any light on what exactly 0x1 means, or if there's a situation in which the script would run but still return that?
For what it's worth, this is the batch file that calls the script:
@echo off
"E:ScriptsBackupcreate_backup.py"
python windows-server-2008 windows-task-scheduler
python windows-server-2008 windows-task-scheduler
edited May 26 at 1:25
fixer1234
17.7k144581
asked Mar 18 '13 at 18:08
Rob
1993413
edited May 26 at 1:25
fixer1234
17.7k144581
asked Mar 18 '13 at 18:08
Rob
1993413
edited May 26 at 1:25
fixer1234
17.7k144581
edited May 26 at 1:25
fixer1234
17.7k144581
edited May 26 at 1:25
fixer1234
17.7k144581
17.7k144581
asked Mar 18 '13 at 18:08
Rob
1993413
asked Mar 18 '13 at 18:08
Rob
1993413
asked Mar 18 '13 at 18:08
Rob
1993413
1993413
4
A quick search seems to indicate that this can be caused by not specifying the correct working directory. When testing your setup, did you try to invoke the task execution through the task scheduler (there's a Run option for tasks in the library)?
– Der Hochstapler
Mar 18 '13 at 18:11
1
Oliver, thanks for the tip, that does sound exactly like what I'm experiencing. I updated the script path to exclude the current working directory, instead specifying it in "Start in". When I run the task nothing visibly happens in the scheduler (I would expect the status to be "Running..."), but eventually it completes. Thanks again!
– Rob
Mar 18 '13 at 19:33
add a comment |
4
A quick search seems to indicate that this can be caused by not specifying the correct working directory. When testing your setup, did you try to invoke the task execution through the task scheduler (there's a Run option for tasks in the library)?
– Der Hochstapler
Mar 18 '13 at 18:11
1
Oliver, thanks for the tip, that does sound exactly like what I'm experiencing. I updated the script path to exclude the current working directory, instead specifying it in "Start in". When I run the task nothing visibly happens in the scheduler (I would expect the status to be "Running..."), but eventually it completes. Thanks again!
– Rob
Mar 18 '13 at 19:33
4
4
A quick search seems to indicate that this can be caused by not specifying the correct working directory. When testing your setup, did you try to invoke the task execution through the task scheduler (there's a Run option for tasks in the library)?
– Der Hochstapler
Mar 18 '13 at 18:11
A quick search seems to indicate that this can be caused by not specifying the correct working directory. When testing your setup, did you try to invoke the task execution through the task scheduler (there's a Run option for tasks in the library)?
– Der Hochstapler
Mar 18 '13 at 18:11
1
1
Oliver, thanks for the tip, that does sound exactly like what I'm experiencing. I updated the script path to exclude the current working directory, instead specifying it in "Start in". When I run the task nothing visibly happens in the scheduler (I would expect the status to be "Running..."), but eventually it completes. Thanks again!
– Rob
Mar 18 '13 at 19:33
Oliver, thanks for the tip, that does sound exactly like what I'm experiencing. I updated the script path to exclude the current working directory, instead specifying it in "Start in". When I run the task nothing visibly happens in the scheduler (I would expect the status to be "Running..."), but eventually it completes. Thanks again!
– Rob
Mar 18 '13 at 19:33
add a comment |
1 Answer
1
active
oldest
votes
Look like this problem outside of python.
May be i wrong, but by default windows allow cmd.exe execution only for logged in user.
To check, add diagnostic output to cmd script
echo Run %DATE% %TIME% >> c:/tmp/file.log
answered Mar 18 '13 at 19:40
Mikhail Moskalev
1,4871112
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f567875%2fwindows-scheduled-tasks-fail-with-0x1-dont-log-errors%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Look like this problem outside of python.
May be i wrong, but by default windows allow cmd.exe execution only for logged in user.
To check, add diagnostic output to cmd script
echo Run %DATE% %TIME% >> c:/tmp/file.log
answered Mar 18 '13 at 19:40
Mikhail Moskalev
1,4871112
add a comment |
Look like this problem outside of python.
May be i wrong, but by default windows allow cmd.exe execution only for logged in user.
To check, add diagnostic output to cmd script
echo Run %DATE% %TIME% >> c:/tmp/file.log
answered Mar 18 '13 at 19:40
Mikhail Moskalev
1,4871112
add a comment |
Look like this problem outside of python.
May be i wrong, but by default windows allow cmd.exe execution only for logged in user.
To check, add diagnostic output to cmd script
echo Run %DATE% %TIME% >> c:/tmp/file.log
answered Mar 18 '13 at 19:40
Mikhail Moskalev
1,4871112
Look like this problem outside of python.
May be i wrong, but by default windows allow cmd.exe execution only for logged in user.
To check, add diagnostic output to cmd script
echo Run %DATE% %TIME% >> c:/tmp/file.log
answered Mar 18 '13 at 19:40
Mikhail Moskalev
1,4871112
answered Mar 18 '13 at 19:40
Mikhail Moskalev
1,4871112
answered Mar 18 '13 at 19:40
Mikhail Moskalev
1,4871112
answered Mar 18 '13 at 19:40
Mikhail Moskalev
1,4871112
1,4871112
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fsuperuser.com%2fquestions%2f567875%2fwindows-scheduled-tasks-fail-with-0x1-dont-log-errors%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
4
A quick search seems to indicate that this can be caused by not specifying the correct working directory. When testing your setup, did you try to invoke the task execution through the task scheduler (there's a Run option for tasks in the library)?
– Der Hochstapler
Mar 18 '13 at 18:11
1
Oliver, thanks for the tip, that does sound exactly like what I'm experiencing. I updated the script path to exclude the current working directory, instead specifying it in "Start in". When I run the task nothing visibly happens in the scheduler (I would expect the status to be "Running..."), but eventually it completes. Thanks again!
– Rob
Mar 18 '13 at 19:33