Weblog entry #287 for simonw
#287
W2K Demotion and Task Scheduler error
Posted by simonw on Thu 13 Nov 2008 at 15:11
Decommissioning a W2K box acting as a domain controller.
After demoting the box, so it is no longer a domain controller no scheduled tasks were run. Clicking the the "properties" for a Scheduled Task produced an error message. Since we'd really like an up to date backup before moving all the data off that server, I wanted to fix the back-up.
Typical errors in SchedLgU.Txt were:
"friday-system-backup.job" (NTBACKUP.EXE) 13/11/2008 11:56:12 ** ERROR **
The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task.
The specific error is:
0x8007000d: The data is invalid.
"System - Friday Backup.job" (NTBACKUP.EXE) 13/11/2008 12:04:22 ** ERROR **
The attempt to log on to the account associated with the task failed, therefore, the task did not run.
The specific error is:
0x8007052e: Logon failure: unknown user name or bad password.
Verify that the task's Run-as name and password are valid and try again.
Google was not much help, apparently machines with multiple CPUs can produce the same error, and not run your scheduled tasks. Others reported the same issue, but usually reverted to a reinstall since you don't demote Domain Controllers very often if you are organized.
After more effort than it was worth, I noticed that the "Task Scheduler" was disabled for the current hardware profile (despite it allegedly running and restarting fine). "Services">"Task Scheduler">"Properties">"Log On" box at the bottom of the dialog.
Moral - don't demote Domain Controllers till the last minute before you decommission the box. Demoting the domain controller also required a number of clients (not all of them in the domain, but some using services) to be rebooted.
Perhaps I should dust off my old Netware Administrator certificate, and grab some SuSE CDs, and go work for Novell.
After demoting the box, so it is no longer a domain controller no scheduled tasks were run. Clicking the the "properties" for a Scheduled Task produced an error message. Since we'd really like an up to date backup before moving all the data off that server, I wanted to fix the back-up.
Typical errors in SchedLgU.Txt were:
"friday-system-backup.job" (NTBACKUP.EXE) 13/11/2008 11:56:12 ** ERROR **
The attempt to retrieve account information for the specified task failed; therefore, the task did not run. Either an error occurred, or no account information existed for the task.
The specific error is:
0x8007000d: The data is invalid.
"System - Friday Backup.job" (NTBACKUP.EXE) 13/11/2008 12:04:22 ** ERROR **
The attempt to log on to the account associated with the task failed, therefore, the task did not run.
The specific error is:
0x8007052e: Logon failure: unknown user name or bad password.
Verify that the task's Run-as name and password are valid and try again.
Google was not much help, apparently machines with multiple CPUs can produce the same error, and not run your scheduled tasks. Others reported the same issue, but usually reverted to a reinstall since you don't demote Domain Controllers very often if you are organized.
After more effort than it was worth, I noticed that the "Task Scheduler" was disabled for the current hardware profile (despite it allegedly running and restarting fine). "Services">"Task Scheduler">"Properties">"Log On" box at the bottom of the dialog.
Moral - don't demote Domain Controllers till the last minute before you decommission the box. Demoting the domain controller also required a number of clients (not all of them in the domain, but some using services) to be rebooted.
Perhaps I should dust off my old Netware Administrator certificate, and grab some SuSE CDs, and go work for Novell.