G
Guest
We're having problems with the Task Scheduler on several computers in our
domain. Whenever I try to bring up the properties on a task that's been
configured to run under the NT AUTHORITY\System account, I get the following
error:
General page initialization failed.
The specific error is:
0x8007000d: The data is invalid.
An error has occurred attempting to retrieve task information. You may
continue editing the task object, but will be unable to change task
account information.
On computers with this problem, tasks with this error do not run; the Tasks
window lists the Status as "Could not start."
I confirmed that the Task Scheduler service is running under the System
account and has permission to interact with the desktop. I tried deleting the
tasks, rebooting, and recreating them, as a couple of sites suggested. I
tried creating tasks through both the GUI and the schtasks command. Nothing
seems to help.
Tasks that are configured to run under other accounts work.
Any suggestions? These tasks are created by a GPO-assigned startup script,
if that makes any difference.
Josh Kelley
domain. Whenever I try to bring up the properties on a task that's been
configured to run under the NT AUTHORITY\System account, I get the following
error:
General page initialization failed.
The specific error is:
0x8007000d: The data is invalid.
An error has occurred attempting to retrieve task information. You may
continue editing the task object, but will be unable to change task
account information.
On computers with this problem, tasks with this error do not run; the Tasks
window lists the Status as "Could not start."
I confirmed that the Task Scheduler service is running under the System
account and has permission to interact with the desktop. I tried deleting the
tasks, rebooting, and recreating them, as a couple of sites suggested. I
tried creating tasks through both the GUI and the schtasks command. Nothing
seems to help.
Tasks that are configured to run under other accounts work.
Any suggestions? These tasks are created by a GPO-assigned startup script,
if that makes any difference.
Josh Kelley