"The attempt to retrieve account information for the specified task failed" error message when you use Task Scheduler to schedule volume shadow copy to run in Windows Server 2003

You use Task Scheduler to schedule a shadow copy backup of a volume to run on a Microsoft Windows Server 2003-based computer. You enable the Volume Shadow Copy service and then run the Dcpromo.exe utility. However, the task does not run successfully, and you do not receive an error message.

Additionally, if you right-click the scheduled task and then click Properties, you receive the following error message: If you then click OK in the error box to display the properties, the Run as line is blank and unavailable. The correct parameters appear in the Run line, but the Run line is also unavailable.

This problem occurs because you used a local computer account that is no longer available to create the task.

To work around this problem, run the Dcpromo.exe utility before you enable the Volume Shadow Copy service, and then use Task Scheduler to schedule volume shadow copy.

You can also work around this problem by re-creating the d42* files. To do this, follow these steps:

1. Log on as user who has administrative credentials.
2. Delete all scheduled tasks. To do this, follow these steps:
   1. Click Start, Run, type control schedtasks, and then press ENTER.
   2. Confirm the list of jobs that are registered in the Scheduled Tasks window.
   3. Delete all registered tasks.
   4. Close the Scheduled Tasks window.
3. Click Start, click Run, type cmd, and then click OK.
4. At the command prompt, type the following to move to the specified folder:
   cd %SystemDrive%\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\S-1-5-18
5. Delete all files that start with d42* by typing the follow command:
   del d42*
6. At the command prompt, type exit.
7. Reschedule the volume shadow copy tasks. The files that start with d42* are re-created after the volume shadow copy tasks are rescheduled.
8. Make sure that the scheduled tasks function correctly on the domain controller.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.