Task Scheduler error
I received a error when creating a basic task on a Windows 2008 server, assigning the local administrator as the account to run the task -> weather logged in or not.
It happens after I typed in the correct password in the dialog that asks for the accounts password.
Error is:
An Error has occurred for the task <task name>. Error message: The following error was
reported. A specified logon session does not exist. It may have already been terminated.
Does anyone know what this message means ? It won't let me finish the task. It also doesn't seem to care what account I used it keeps giving me this error.
Also this system event is produced" Event id 116 Source: TaskScheduler
Task Scheduler validated the configuration for task "<taskname>" , but credentials could not be stored. User Action: Re-register the task ensuring the credentials are valid. Additional Data: Error Value: 2147943712.
Thanks
January 28th, 2011 4:13pm
Please refer to
this thread. It is about the same error.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2011 4:19pm
Yes that did correct it.
GP location:
Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\
Policy:
Network access: Do not allow storage of passwords and credentials for network authentication [disable]
Do we know what the purpose of the policy is then ? 2003 task scheduler doesn't care but 2008 task scheduler does. What other applications care about this setting and why would I not want to enable it, besides the 2008 task scheduler.
I also found in the 2008 task scheduler that if you have this enabled or set the [do not store password] selected on the task itself that it won't care what the password is and will run. Actually you have to select [do not store password] if it is enabled,
it's the only way it would work. In any case isn't this a security problem ?
January 28th, 2011 4:37pm