In the last week I have notice that on our Windows 7 Pro workstations the Task Scheduler that we use to update some files for an application we have is not updating. The error is (0x1). This task has run without issue for the last year (0x0). The only changes to the workstations have been MS updates. There seems to have been a rather large update in the last week or so, and that may be causing our problem. It is important to note that this task is set to trigger on startup. If I change the trigger to logon/any user the task works just fine??? I have not found any thing that gives any inshight to the issue on line. Help pleae!!!!!!

Hi, According the issue, I want to know if there any other task in Task Scheduler? If it exsit, does it works fine? If there only this task, please create a new task and try to run it. If the new task works fine, please enable Task History and check the item which related the task, if any error massage in History, paste the details here. If the none task cannot be perform, please check if the task scheduler service is running. Also run SFC to check the system files. http://support.microsoft.com/kb/929833/en-us Also the Task Scheduler service depends on Remote Procedure Call (RPC), DCOM Server Process Launcher and RPC Endpoint Mapper services to start. Please use the same way to check these three services. Hope that helps Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

There are other tasks in the task scheduler. They all are working fine. My focus is how can this be working if I change the trigger to a logon from a startup trigger and it start working??? My workaround is to change the the trigger, but I would like to know what MS Update caused the issue and that will tell me what other workstations I need to alter the Task scheduler trigger for. What is interesting is the RCP nature of the task. In another issue I had some time back, after we just deployed our first batch of new Windows 7 pro machines we found that these new OS units had a spooler issue that tracked back to an asynchronis RPC from the the w2k7 pro box to our print server a w2k3 SP3 server. Microsoft suggested that we change the print server to a w2k8 R2 or STD and that fixed the problem with hung spooler in the w2k7 pro workstations.....I wonder if the task scheduler uses async RPC and if so if that might be what is failing the task scheduler update I'm trying to run at startup? In this case I guess the task is not running an RCP with the trigger mode set to logon. My sense is it must still be related to a security update either on the workstation or the server that we are getting the update from.

Another thought is perhaps an update changed the order of the startup OS tasks and the availability of the network is not ready for the task scheduler task to access the network file locations?? Again it would have to be an update that changed something in the w2k7 pro machines??