3

Windows Server 2008 Task Scheduler: Task Started (Task=100) but did task did not complete (Task=102) when the result code is 2

view full story
linux-howto

http://serverfault.com – Can someone give me a use case for setting up a Windows Server 2008 Task Scheduler task (we'll call this "test") that completes (action completed is task=201) with an error (result code=2)? This is event trigger code for another task (called "notification" that sends out an email based on the event history of the "test" task. I've got use cases for tasks that opens a program successfully and when a program fails to find the program. I'm just trying to think of how I can test a scenario when it finds the program, but something fails with warnings or errors. /* Failed - task started but had (HowTos)

dayu's picture
Submitted by dayu on 06/20/2012 – Made popular on 06/20/2012

Stories similar to Windows Server 2008 Task Scheduler: Task Started (Task=100) but did task did not complete (Task=102) when the result code is 2

Is there a way to know the source and legitimacy of the tasks in the task scheduler in windows server 2008 and 2003? Can I check if the task was added by Microsoft (ie: from sccm) or by a 3rd party application?

For each task in the task scheduler, I want to verify that the task has not been created by a third party application.

I am looking at consolidating all of our scheduled tasks that run on various servers (Win 2008 R2) within our domain on to one "Task Scheduling Server". I am a developer so I'm not even sure if this is a good idea or just a maintenance headache. One of our Network guys copied some of the tasks I monitor over to the new server and asked me to test them.

I wrote a PowerShell script that check the executable in the < action > tag for each task in the Task directory and mark the < enabled >TRUEorFALSE< / enabled > tag as false/true depending on the validity of the digital signature of the executable.

Task 1: Stick The Landing Task 2: Chop Stack Task 3: The Nutstacker Task 4: Johnny Applestack Task 5: Back Flip Task 6: Cantagious Task 7: Stack Attack Task 8: Face The Cookie Task 9: A Bit Dicey Task 10: Double Trouble <-- You all love it

Total time: 235 seconds

youtube link: http://youtu.be/At26nbMJk2s

Thanks for watching!

Task 1: Stick The Landing Task 2: Chop Stack Task 3: The Nutstacker Task 4: Johnny Applestack Task 5: Back Flip Task 6: Cantagious Task 7: Stack Attack Task 8: Face The Cookie Task 9: A Bit Dicey Task 10: Double Trouble <-- You all love it

Total time: 235 seconds

youtube link: http://youtu.be/At26nbMJk2s

Thanks for watching!

I get the following error in the Scheduled Task history when I try to run a task:

Task Scheduler successfully completed task "\Restart Tomcat" , instance "{264b4620-5f3b-6c5f-a6cb-1625a7fa57de}" , action "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.EXE" with return code 1.

The scheduled task is configured as follows:

Name: Restart Tomcat User: DOMAIN\tomcat.restarter Triggers: Daily

I want Fiddler and some other programs to run on startup, so it's there and running every time I bring up an instance of my test server on EC2. There's a few questions about running scripts on Startup with Task Scheduler, but this needs to work slightly differently.

System is Windows 2008 R2

I have a task scheduler task with a trigger to run at system startup, and have set the Delay to 20 minutes, however the task runs immediatley on system startup and ignores the 20 minute delay. There are other triggers, but it is the boot trigger which is at fault by ignoring the delay.

Triggers section of the exported task follows.

<Triggers> <CalendarTrigge

I'm getting an error "data area passed to a system call is too small" when trying to add a task to the Windows Scheduler. We currently have about 20 tasks in it.

Googling the issue, we found to stop/start the task service, wait, and some kind of clean-up would be run. We've done this multiple times and it's not fixing anything.