Scheduled task does not run after you push the task to another computer (317529)

SYMPTOMS

When you either create a local at command to schedule a command, a script, or a program to run at a specified date and time or use Task Scheduler to create a scheduled task, if you push either the at command or the scheduled task over the network to another computer, the task may not run. When the task does not run, the following error is logged in the schedule log:

0x8004130f: No account information could be found in the Task Scheduler security database for the task indicated.

CAUSE

This issue occurs because when a task is pushed to another computer, the security descriptor is broken. If you are not logged on, Windows cannot access the local Protected Storage database to verify whether the task can be run. An Example of pushing a job to a remote computer is:

AT \\remotecomputername 15:00 /Every:M,T,W,TH,F c:\windows\system32\calc.exe

The job must be pushed. Any attempt to copy the job or move the job breaks the security.

RESOLUTION

To resolve this issue, log on to the computer. When you log on to the computer, Windows can gain access to the local Protected Storage database.

MORE INFORMATION

When you create a scheduled task, the password that is supplied for the task is stored in the Protected Storage database; the password is not stored in the actual task. When you create the scheduled task, the task is given a security descriptor. The task uses this security descriptor to gain access to the Protected Storage database to get the password. If you either move or alter the task, the security descriptor is broken, and the link to the Protected Storage database is broken. Therefore, the task cannot access the password, and the task cannot run.