I was working with the task scheduler on one of our virtualized win2008 servers. I started a scheduled task (in this case it was a batch file) and the scheduler which was initially in the READY state didn't go to RUNNING, so I pressed the run button again, this time the scheduler changed it's state to RUNNING. When I look at the detailed log, I see that it created a new process TWO times. (I also had set the job properties to prevent launching two processes) If I look using TASKLIST, I can see that I have two jobs running. With two processes running the same program, the two instances of the program step on each other's toes and I get errors. This problem has happened several times, so it's not just a fluke. Is there a fixpack to address this problem? The other problem is even though I have the Process ID's from the Scheduler log, and I can see the process using TASKLIST, I can't seem to kill the first job which means I may have to reboot to clear up the problem.... (Not Cool) TASKKILL PID 1234 /T

Hi, Whether there are conflicts with other scheduled tasks. Please create a separate scheduled tasks to see if the same issue still exists. At the same time, you can also check the Event Viewer if is there a special error log. Technology changes life