My task is abruptly closed and i get an error with code 2147750687 in task scheduler?

New Contributor

I have a task set to run every 10 mins daily in a prod environment. The machine is Windows Server 2008 R2 Standard 64 bit system. The task basically runs an exe that process some XML files, transform them and put it in a different folder.  Recently I saw that some XML files failed, the log file just ended abruptly. We tried to replicate and most of the common exception was caught. So we knew it was not an exception because the application would have caught it, logged it and ended gracefully. This seemed more like when you end the application in task manager and the log just stopped.

As part of the analysis I found that whenever the file failed, there was a warning and an error entry in task scheduler log.


The warning states:
Task Scheduler did not launch task "Task name"  because instance "{41a1167e-2092-434f-80e4-ef83e03fc7e1}"  of the same task is already running.

The error states:
Task Scheduler failed to start "Task name" task for user "domain\account". Additional Data: Error Value: 2147750687.

The task is getting triggered at intervals of 10 minutes. So at the 10th minute, it gets triggered and instead of waiting for the running instance to get over, it crashes that thread even though we had set 'Do not start new instance' in the settings.  An online search led me to this hotfix:


The symptom described is exactly what I am facing but the symptom says that this occurs when 2305420 is installed. I checked the updates installed in the system and it doesn't hdoesn't05420 installed. Can this issue occur even though KB2305420 is not installed? Can I run the hotfix to solve this issue? Is there any way to verify that this is indeed the issue? Is there a workaround for this? I read we can try creating a new task and delete the old one

2 Replies

Haven't you set up scheduler to launch task every day at 00:00 and repeat it every 10 minutes? Does this schedule expire on daily basis? (checkbox below the one where you set up repeatition). You may have set up schedule that generates 6 launches/hour on first day, 12 launches/hour on second day, 18 on third, 24... looks like this task logs more events than expected to (but ain't sure cause your screenshot is really narrow :)

The thing is, whenever a new trigger warning and error occurs as seen in the screenshot, my application stops writing any log. So we are guessing the thread is getting crashed. We were thinking the windows bug if duplicate triggers happening is somehow causing the application to crash or it seems from the log file as it just ends abruptly at that point of time.