"Shenan Stanley" wrote:
| Patched our Windows 2003 servers and rebooted them last night.  I have a
| scheduled task on each that runs at startup - it emails me when the
machine
| has returned to startup.  I have always created this task using the NT
| AUTHORITY\System user.
|
| One machine did not email me - so I went to check.  The scheduled task
(and
| others that used the NT AUTHORITY\system user as credentials) had their
last
| state as "Could not Run".
|
| So I figured I would look at the properties of the task.. That gives me:
|
| General page initialization failed.
| The specific error is:
| 0x8007000d: The data is invalid.
| An error has occurred attempting to retrieve task account information.
You
| may continue editing the task object, but will be unable to change task
| account information.
|
| And the ability to change the user is lost.
|
| So I used SCHTASKS to delete the tasks and recreate them with the same
user
| credentials.  Same error.  So I used the GUI to create one with different
| credentials - no problem.  Changed the credentials using the GUI to NT
| AUTHORITY\System - same error as above.
|
| - File/Folder permissions still list the SYSTEM user as an option for
| permissions.
| - I looked for C:\WINDOWS\SchedLgU.Txt file - it doesn't seem to exist on
| the servers.
| - I stopped and started the Task Scheduler task..  Made sure it was set to
| "Allow service to interact with desktop"..
| - I checked the RPC service.
| - The "SYSTEM" account has permissions to the files I am trying to run.
| - Any Task scheduled with the NT AUTHORITY\System account presents the
same
| symptoms.
| - The other servers are not having this issue.  The twin system of this
| server is not having this issue.
|
| Does anyone know what has happened to the NT AUTHORITY\System account and
| how to remedy it?  Or is this a Task Scheduler thing?
|
| --
| Shenan Stanley
|     MS-MVP
|
|

> Patched our Windows 2003 servers and rebooted them last night.  I
> have a scheduled task on each that runs at startup - it emails me
> when the machine has returned to startup.  I have always created this
> task using the NT AUTHORITY\System user.
>
> One machine did not email me - so I went to check.  The scheduled
> task (and others that used the NT AUTHORITY\system user as
> credentials) had their last state as "Could not Run".
>
> So I figured I would look at the properties of the task.. That gives
> me:
> General page initialization failed.
> The specific error is:
> 0x8007000d: The data is invalid.
> An error has occurred attempting to retrieve task account
> information.  You may continue editing the task object, but will be
> unable to change task account information.
>
> And the ability to change the user is lost.
>
> So I used SCHTASKS to delete the tasks and recreate them with the
> same user credentials.  Same error.  So I used the GUI to create one
> with different credentials - no problem.  Changed the credentials
> using the GUI to NT AUTHORITY\System - same error as above.
>
> - File/Folder permissions still list the SYSTEM user as an option for
> permissions.
> - I looked for C:\WINDOWS\SchedLgU.Txt file - it doesn't seem to
> exist on the servers.
> - I stopped and started the Task Scheduler task..  Made sure it was
> set to "Allow service to interact with desktop"..
> - I checked the RPC service.
> - The "SYSTEM" account has permissions to the files I am trying to
> run. - Any Task scheduled with the NT AUTHORITY\System account presents
> the same symptoms.
> - The other servers are not having this issue.  The twin system of
> this server is not having this issue.
>
> Does anyone know what has happened to the NT AUTHORITY\System account
> and how to remedy it?  Or is this a Task Scheduler thing?