Task Scheduler repeat task not triggering
I am trying to set up a task that will start up an .exe every minute.
I have created a Trigger, that when triggered will run the .exe and repeat every minute indefinitely.
(I have also tried creating a daily task, the once triggered will repeat every minute for that 1 day).
When I run the task manually, it works as expected, but if I leave the task to reach the 'Next Run Time' instead of it running and updating the 'Last Run Time', the 'Next Run Time' is updated to run a minute later and the 'Last Run Time' remains the same.
I have checked the Task History and there are no new events. Also, I have logging within the specified .exe and it's not showing that it has been run.
windows windows-server-2008 task-scheduler windows-server
asked Jan 15 '15 at 11:10
Jack AllenJack Allen
151113
|
show 5 more comments
I am trying to set up a task that will start up an .exe every minute.
I have created a Trigger, that when triggered will run the .exe and repeat every minute indefinitely.
(I have also tried creating a daily task, the once triggered will repeat every minute for that 1 day).
When I run the task manually, it works as expected, but if I leave the task to reach the 'Next Run Time' instead of it running and updating the 'Last Run Time', the 'Next Run Time' is updated to run a minute later and the 'Last Run Time' remains the same.
I have checked the Task History and there are no new events. Also, I have logging within the specified .exe and it's not showing that it has been run.
windows windows-server-2008 task-scheduler windows-server
asked Jan 15 '15 at 11:10
Jack AllenJack Allen
151113
Check the event viewer in case it is crashing. It could be running in the background, so you do not start a new instance? Check Task Manager to make sure the exe isn't running
– Dave
Jan 15 '15 at 12:08
@Dave It doesn't appear to be running in the background and I can't see any logs in the Event Viewer for the Task Scheduler. Do you know if the .exe has to be in a specific location or something like that?
– Jack Allen
Jan 15 '15 at 14:14
No, the .exe can be any where. However, the exe could be crashing or similar so I thought to check event viewer. What is the application? One you wrote or 'other'?
– Dave
Jan 15 '15 at 14:17
The .exe is something I have written, although I have run it both on the server from its directory location and also I have manually run the Task in the Scheduler and the .exe runs successfully.
– Jack Allen
Jan 15 '15 at 14:20
Does this issue occur when you're logged onto the server?
– Dave
Jan 15 '15 at 14:21
|
show 5 more comments
I am trying to set up a task that will start up an .exe every minute.
I have created a Trigger, that when triggered will run the .exe and repeat every minute indefinitely.
(I have also tried creating a daily task, the once triggered will repeat every minute for that 1 day).
When I run the task manually, it works as expected, but if I leave the task to reach the 'Next Run Time' instead of it running and updating the 'Last Run Time', the 'Next Run Time' is updated to run a minute later and the 'Last Run Time' remains the same.
I have checked the Task History and there are no new events. Also, I have logging within the specified .exe and it's not showing that it has been run.
windows windows-server-2008 task-scheduler windows-server
asked Jan 15 '15 at 11:10
Jack AllenJack Allen
151113
I am trying to set up a task that will start up an .exe every minute.
I have created a Trigger, that when triggered will run the .exe and repeat every minute indefinitely.
(I have also tried creating a daily task, the once triggered will repeat every minute for that 1 day).
When I run the task manually, it works as expected, but if I leave the task to reach the 'Next Run Time' instead of it running and updating the 'Last Run Time', the 'Next Run Time' is updated to run a minute later and the 'Last Run Time' remains the same.
I have checked the Task History and there are no new events. Also, I have logging within the specified .exe and it's not showing that it has been run.
windows windows-server-2008 task-scheduler windows-server
windows windows-server-2008 task-scheduler windows-server
asked Jan 15 '15 at 11:10
Jack AllenJack Allen
151113
asked Jan 15 '15 at 11:10
Jack AllenJack Allen
151113
edited Jan 15 '15 at 11:43
Jack Allen
asked Jan 15 '15 at 11:10
Jack AllenJack Allen
151113
asked Jan 15 '15 at 11:10
Jack AllenJack Allen
151113
asked Jan 15 '15 at 11:10
Jack AllenJack Allen
151113
151113
Check the event viewer in case it is crashing. It could be running in the background, so you do not start a new instance? Check Task Manager to make sure the exe isn't running
– Dave
Jan 15 '15 at 12:08
@Dave It doesn't appear to be running in the background and I can't see any logs in the Event Viewer for the Task Scheduler. Do you know if the .exe has to be in a specific location or something like that?
– Jack Allen
Jan 15 '15 at 14:14
No, the .exe can be any where. However, the exe could be crashing or similar so I thought to check event viewer. What is the application? One you wrote or 'other'?
– Dave
Jan 15 '15 at 14:17
The .exe is something I have written, although I have run it both on the server from its directory location and also I have manually run the Task in the Scheduler and the .exe runs successfully.
– Jack Allen
Jan 15 '15 at 14:20
Does this issue occur when you're logged onto the server?
– Dave
Jan 15 '15 at 14:21
|
show 5 more comments
Check the event viewer in case it is crashing. It could be running in the background, so you do not start a new instance? Check Task Manager to make sure the exe isn't running
– Dave
Jan 15 '15 at 12:08
@Dave It doesn't appear to be running in the background and I can't see any logs in the Event Viewer for the Task Scheduler. Do you know if the .exe has to be in a specific location or something like that?
– Jack Allen
Jan 15 '15 at 14:14
No, the .exe can be any where. However, the exe could be crashing or similar so I thought to check event viewer. What is the application? One you wrote or 'other'?
– Dave
Jan 15 '15 at 14:17
The .exe is something I have written, although I have run it both on the server from its directory location and also I have manually run the Task in the Scheduler and the .exe runs successfully.
– Jack Allen
Jan 15 '15 at 14:20
Does this issue occur when you're logged onto the server?
– Dave
Jan 15 '15 at 14:21
Check the event viewer in case it is crashing. It could be running in the background, so you do not start a new instance? Check Task Manager to make sure the exe isn't running
– Dave
Jan 15 '15 at 12:08
Check the event viewer in case it is crashing. It could be running in the background, so you do not start a new instance? Check Task Manager to make sure the exe isn't running
– Dave
Jan 15 '15 at 12:08
@Dave It doesn't appear to be running in the background and I can't see any logs in the Event Viewer for the Task Scheduler. Do you know if the .exe has to be in a specific location or something like that?
– Jack Allen
Jan 15 '15 at 14:14
@Dave It doesn't appear to be running in the background and I can't see any logs in the Event Viewer for the Task Scheduler. Do you know if the .exe has to be in a specific location or something like that?
– Jack Allen
Jan 15 '15 at 14:14
No, the .exe can be any where. However, the exe could be crashing or similar so I thought to check event viewer. What is the application? One you wrote or 'other'?
– Dave
Jan 15 '15 at 14:17
No, the .exe can be any where. However, the exe could be crashing or similar so I thought to check event viewer. What is the application? One you wrote or 'other'?
– Dave
Jan 15 '15 at 14:17
The .exe is something I have written, although I have run it both on the server from its directory location and also I have manually run the Task in the Scheduler and the .exe runs successfully.
– Jack Allen
Jan 15 '15 at 14:20
The .exe is something I have written, although I have run it both on the server from its directory location and also I have manually run the Task in the Scheduler and the .exe runs successfully.
– Jack Allen
Jan 15 '15 at 14:20
Does this issue occur when you're logged onto the server?
– Dave
Jan 15 '15 at 14:21
Does this issue occur when you're logged onto the server?
– Dave
Jan 15 '15 at 14:21
|
show 5 more comments
4 Answers
4
active
oldest
votes
Just in case you trigger the task manually...
I have just come across this same problem on Window 7. I haven't tested it with any other version of Windows.
It seems that repeated tasks are not executed when run manually (right click on a task and then select "Run").
When run manually, the task will run only once and that's it!
This is a trip wire since it's natural that people simply run the task manually right after its creation to check whether it's working as expected.
What you could do, set the trigger to "At startup". After you rebooted the machine, the task should then be in the "Queued" status. This means it will run at the configured interval.
answered Mar 31 '15 at 21:29
quatquat
15116
A better solution via @user917170 is to check 'Run task as soon as possible after a scheduled start is missed' with whatever trigger you want (time based, etc). Then it should start running automatically on schedule as expected.
– drzaus
Feb 11 at 13:58
add a comment |
Manual triggering is for testing. You need a real trigger to start repetition.
I solved this by setting up a trigger for system start, as suggested, but if that session fails or you make edits, and you don't want to restart the machine, just set an additional trigger to perform the same sort of repetition on a daily basis, with a start time in a minute or two.
You can then leave both triggers running, and set them both to not start another instance if one is already running, with appropriate timeouts to kill the current instance if it runs too long. This way, you are assured of triggering, even if the instance that started when the computer was last rebooted dies.
edited Jan 31 '17 at 18:42
music2myear
31.2k858100
answered Jan 31 '17 at 18:05
Curtis GrayCurtis Gray
211
Creative solution. I am going to give this a try.
– Rod Hartzell
Aug 7 '17 at 15:47
Better: enable 'run as soon as scheduled start missed'. In general, be wary of multiple triggers for two reasons -- exporting a task w/ an end-date on a trigger, importing won't respect the end date and both will be active. Also, there was a hotfix for some Windows ([KB2461249|support.microsoft.com/en-us/help/2461249/…) because the scheduler would double-schedule a task if the start time coincided with the end of a window, so I could imagine some weird rounding causing multiple overlapping triggers to fire.
– drzaus
Feb 11 at 14:09
add a comment |
I ran into this problem me too, I was able to solve it by setting the start date and time one or two minutes ahead of the time of making the task to trigger the action and start repeating it as configured.
answered Jun 20 '17 at 12:48
MusuNajiMusuNaji
1396
add a comment |
The correct way to set this up is to set the start time any time in the past, then select "Run task as soon as possible after a scheduled start is missed" in the Settings tab.
answered Jan 24 at 6:00
user917170user917170
1112
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%2f865067%2ftask-scheduler-repeat-task-not-triggering%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Just in case you trigger the task manually...
I have just come across this same problem on Window 7. I haven't tested it with any other version of Windows.
It seems that repeated tasks are not executed when run manually (right click on a task and then select "Run").
When run manually, the task will run only once and that's it!
This is a trip wire since it's natural that people simply run the task manually right after its creation to check whether it's working as expected.
What you could do, set the trigger to "At startup". After you rebooted the machine, the task should then be in the "Queued" status. This means it will run at the configured interval.
answered Mar 31 '15 at 21:29
quatquat
15116
A better solution via @user917170 is to check 'Run task as soon as possible after a scheduled start is missed' with whatever trigger you want (time based, etc). Then it should start running automatically on schedule as expected.
– drzaus
Feb 11 at 13:58
add a comment |
Just in case you trigger the task manually...
I have just come across this same problem on Window 7. I haven't tested it with any other version of Windows.
It seems that repeated tasks are not executed when run manually (right click on a task and then select "Run").
When run manually, the task will run only once and that's it!
This is a trip wire since it's natural that people simply run the task manually right after its creation to check whether it's working as expected.
What you could do, set the trigger to "At startup". After you rebooted the machine, the task should then be in the "Queued" status. This means it will run at the configured interval.
answered Mar 31 '15 at 21:29
quatquat
15116
A better solution via @user917170 is to check 'Run task as soon as possible after a scheduled start is missed' with whatever trigger you want (time based, etc). Then it should start running automatically on schedule as expected.
– drzaus
Feb 11 at 13:58
add a comment |
Just in case you trigger the task manually...
I have just come across this same problem on Window 7. I haven't tested it with any other version of Windows.
It seems that repeated tasks are not executed when run manually (right click on a task and then select "Run").
When run manually, the task will run only once and that's it!
This is a trip wire since it's natural that people simply run the task manually right after its creation to check whether it's working as expected.
What you could do, set the trigger to "At startup". After you rebooted the machine, the task should then be in the "Queued" status. This means it will run at the configured interval.
answered Mar 31 '15 at 21:29
quatquat
15116
Just in case you trigger the task manually...
I have just come across this same problem on Window 7. I haven't tested it with any other version of Windows.
It seems that repeated tasks are not executed when run manually (right click on a task and then select "Run").
When run manually, the task will run only once and that's it!
This is a trip wire since it's natural that people simply run the task manually right after its creation to check whether it's working as expected.
What you could do, set the trigger to "At startup". After you rebooted the machine, the task should then be in the "Queued" status. This means it will run at the configured interval.
answered Mar 31 '15 at 21:29
quatquat
15116
answered Mar 31 '15 at 21:29
quatquat
15116
answered Mar 31 '15 at 21:29
quatquat
15116
answered Mar 31 '15 at 21:29
quatquat
15116
15116
A better solution via @user917170 is to check 'Run task as soon as possible after a scheduled start is missed' with whatever trigger you want (time based, etc). Then it should start running automatically on schedule as expected.
– drzaus
Feb 11 at 13:58
add a comment |
A better solution via @user917170 is to check 'Run task as soon as possible after a scheduled start is missed' with whatever trigger you want (time based, etc). Then it should start running automatically on schedule as expected.
– drzaus
Feb 11 at 13:58
A better solution via @user917170 is to check 'Run task as soon as possible after a scheduled start is missed' with whatever trigger you want (time based, etc). Then it should start running automatically on schedule as expected.
– drzaus
Feb 11 at 13:58
A better solution via @user917170 is to check 'Run task as soon as possible after a scheduled start is missed' with whatever trigger you want (time based, etc). Then it should start running automatically on schedule as expected.
– drzaus
Feb 11 at 13:58
add a comment |
Manual triggering is for testing. You need a real trigger to start repetition.
I solved this by setting up a trigger for system start, as suggested, but if that session fails or you make edits, and you don't want to restart the machine, just set an additional trigger to perform the same sort of repetition on a daily basis, with a start time in a minute or two.
You can then leave both triggers running, and set them both to not start another instance if one is already running, with appropriate timeouts to kill the current instance if it runs too long. This way, you are assured of triggering, even if the instance that started when the computer was last rebooted dies.
edited Jan 31 '17 at 18:42
music2myear
31.2k858100
answered Jan 31 '17 at 18:05
Curtis GrayCurtis Gray
211
Creative solution. I am going to give this a try.
– Rod Hartzell
Aug 7 '17 at 15:47
Better: enable 'run as soon as scheduled start missed'. In general, be wary of multiple triggers for two reasons -- exporting a task w/ an end-date on a trigger, importing won't respect the end date and both will be active. Also, there was a hotfix for some Windows ([KB2461249|support.microsoft.com/en-us/help/2461249/…) because the scheduler would double-schedule a task if the start time coincided with the end of a window, so I could imagine some weird rounding causing multiple overlapping triggers to fire.
– drzaus
Feb 11 at 14:09
add a comment |
Manual triggering is for testing. You need a real trigger to start repetition.
I solved this by setting up a trigger for system start, as suggested, but if that session fails or you make edits, and you don't want to restart the machine, just set an additional trigger to perform the same sort of repetition on a daily basis, with a start time in a minute or two.
You can then leave both triggers running, and set them both to not start another instance if one is already running, with appropriate timeouts to kill the current instance if it runs too long. This way, you are assured of triggering, even if the instance that started when the computer was last rebooted dies.
edited Jan 31 '17 at 18:42
music2myear
31.2k858100
answered Jan 31 '17 at 18:05
Curtis GrayCurtis Gray
211
Creative solution. I am going to give this a try.
– Rod Hartzell
Aug 7 '17 at 15:47
Better: enable 'run as soon as scheduled start missed'. In general, be wary of multiple triggers for two reasons -- exporting a task w/ an end-date on a trigger, importing won't respect the end date and both will be active. Also, there was a hotfix for some Windows ([KB2461249|support.microsoft.com/en-us/help/2461249/…) because the scheduler would double-schedule a task if the start time coincided with the end of a window, so I could imagine some weird rounding causing multiple overlapping triggers to fire.
– drzaus
Feb 11 at 14:09
add a comment |
Manual triggering is for testing. You need a real trigger to start repetition.
I solved this by setting up a trigger for system start, as suggested, but if that session fails or you make edits, and you don't want to restart the machine, just set an additional trigger to perform the same sort of repetition on a daily basis, with a start time in a minute or two.
You can then leave both triggers running, and set them both to not start another instance if one is already running, with appropriate timeouts to kill the current instance if it runs too long. This way, you are assured of triggering, even if the instance that started when the computer was last rebooted dies.
edited Jan 31 '17 at 18:42
music2myear
31.2k858100
answered Jan 31 '17 at 18:05
Curtis GrayCurtis Gray
211
Manual triggering is for testing. You need a real trigger to start repetition.
I solved this by setting up a trigger for system start, as suggested, but if that session fails or you make edits, and you don't want to restart the machine, just set an additional trigger to perform the same sort of repetition on a daily basis, with a start time in a minute or two.
You can then leave both triggers running, and set them both to not start another instance if one is already running, with appropriate timeouts to kill the current instance if it runs too long. This way, you are assured of triggering, even if the instance that started when the computer was last rebooted dies.
edited Jan 31 '17 at 18:42
music2myear
31.2k858100
answered Jan 31 '17 at 18:05
Curtis GrayCurtis Gray
211
edited Jan 31 '17 at 18:42
music2myear
31.2k858100
edited Jan 31 '17 at 18:42
music2myear
31.2k858100
edited Jan 31 '17 at 18:42
music2myear
31.2k858100
31.2k858100
answered Jan 31 '17 at 18:05
Curtis GrayCurtis Gray
211
answered Jan 31 '17 at 18:05
Curtis GrayCurtis Gray
211
answered Jan 31 '17 at 18:05
Curtis GrayCurtis Gray
211
211
Creative solution. I am going to give this a try.
– Rod Hartzell
Aug 7 '17 at 15:47
Better: enable 'run as soon as scheduled start missed'. In general, be wary of multiple triggers for two reasons -- exporting a task w/ an end-date on a trigger, importing won't respect the end date and both will be active. Also, there was a hotfix for some Windows ([KB2461249|support.microsoft.com/en-us/help/2461249/…) because the scheduler would double-schedule a task if the start time coincided with the end of a window, so I could imagine some weird rounding causing multiple overlapping triggers to fire.
– drzaus
Feb 11 at 14:09
add a comment |
Creative solution. I am going to give this a try.
– Rod Hartzell
Aug 7 '17 at 15:47
Better: enable 'run as soon as scheduled start missed'. In general, be wary of multiple triggers for two reasons -- exporting a task w/ an end-date on a trigger, importing won't respect the end date and both will be active. Also, there was a hotfix for some Windows ([KB2461249|support.microsoft.com/en-us/help/2461249/…) because the scheduler would double-schedule a task if the start time coincided with the end of a window, so I could imagine some weird rounding causing multiple overlapping triggers to fire.
– drzaus
Feb 11 at 14:09
Creative solution. I am going to give this a try.
– Rod Hartzell
Aug 7 '17 at 15:47
Creative solution. I am going to give this a try.
– Rod Hartzell
Aug 7 '17 at 15:47
Better: enable 'run as soon as scheduled start missed'. In general, be wary of multiple triggers for two reasons -- exporting a task w/ an end-date on a trigger, importing won't respect the end date and both will be active. Also, there was a hotfix for some Windows ([KB2461249|support.microsoft.com/en-us/help/2461249/…) because the scheduler would double-schedule a task if the start time coincided with the end of a window, so I could imagine some weird rounding causing multiple overlapping triggers to fire.
– drzaus
Feb 11 at 14:09
Better: enable 'run as soon as scheduled start missed'. In general, be wary of multiple triggers for two reasons -- exporting a task w/ an end-date on a trigger, importing won't respect the end date and both will be active. Also, there was a hotfix for some Windows ([KB2461249|support.microsoft.com/en-us/help/2461249/…) because the scheduler would double-schedule a task if the start time coincided with the end of a window, so I could imagine some weird rounding causing multiple overlapping triggers to fire.
– drzaus
Feb 11 at 14:09
add a comment |
I ran into this problem me too, I was able to solve it by setting the start date and time one or two minutes ahead of the time of making the task to trigger the action and start repeating it as configured.
answered Jun 20 '17 at 12:48
MusuNajiMusuNaji
1396
add a comment |
I ran into this problem me too, I was able to solve it by setting the start date and time one or two minutes ahead of the time of making the task to trigger the action and start repeating it as configured.
answered Jun 20 '17 at 12:48
MusuNajiMusuNaji
1396
add a comment |
I ran into this problem me too, I was able to solve it by setting the start date and time one or two minutes ahead of the time of making the task to trigger the action and start repeating it as configured.
answered Jun 20 '17 at 12:48
MusuNajiMusuNaji
1396
I ran into this problem me too, I was able to solve it by setting the start date and time one or two minutes ahead of the time of making the task to trigger the action and start repeating it as configured.
answered Jun 20 '17 at 12:48
MusuNajiMusuNaji
1396
answered Jun 20 '17 at 12:48
MusuNajiMusuNaji
1396
answered Jun 20 '17 at 12:48
MusuNajiMusuNaji
1396
answered Jun 20 '17 at 12:48
MusuNajiMusuNaji
1396
1396
add a comment |
add a comment |
The correct way to set this up is to set the start time any time in the past, then select "Run task as soon as possible after a scheduled start is missed" in the Settings tab.
answered Jan 24 at 6:00
user917170user917170
1112
add a comment |
The correct way to set this up is to set the start time any time in the past, then select "Run task as soon as possible after a scheduled start is missed" in the Settings tab.
answered Jan 24 at 6:00
user917170user917170
1112
add a comment |
The correct way to set this up is to set the start time any time in the past, then select "Run task as soon as possible after a scheduled start is missed" in the Settings tab.
answered Jan 24 at 6:00
user917170user917170
1112
The correct way to set this up is to set the start time any time in the past, then select "Run task as soon as possible after a scheduled start is missed" in the Settings tab.
answered Jan 24 at 6:00
user917170user917170
1112
answered Jan 24 at 6:00
user917170user917170
1112
answered Jan 24 at 6:00
user917170user917170
1112
answered Jan 24 at 6:00
user917170user917170
1112
1112
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.
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%2f865067%2ftask-scheduler-repeat-task-not-triggering%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
Check the event viewer in case it is crashing. It could be running in the background, so you do not start a new instance? Check Task Manager to make sure the exe isn't running
– Dave
Jan 15 '15 at 12:08
@Dave It doesn't appear to be running in the background and I can't see any logs in the Event Viewer for the Task Scheduler. Do you know if the .exe has to be in a specific location or something like that?
– Jack Allen
Jan 15 '15 at 14:14
No, the .exe can be any where. However, the exe could be crashing or similar so I thought to check event viewer. What is the application? One you wrote or 'other'?
– Dave
Jan 15 '15 at 14:17
The .exe is something I have written, although I have run it both on the server from its directory location and also I have manually run the Task in the Scheduler and the .exe runs successfully.
– Jack Allen
Jan 15 '15 at 14:20
Does this issue occur when you're logged onto the server?
– Dave
Jan 15 '15 at 14:21