22 June 2006
Shadow Copy failures: Scheduled task fails with General page initialization failed, error 0x8007000d.
I've rippled through quite a few nagging problems since my server failure at home a few weeks ago. One of the more intriguing problem I only noticed a couple of days ago. One server had not been running scheduled Shadow Copies. When you schedule shadow copies in Windows Server 2003 R2, not suprizingly it sets up a normal Windows Scheduled Task with name ShadowCopyVolume{volume} as shown below.
But, as you can see, it's never run and has status "Could not start". If you double click the task, you get the error "General page initialization failed. The specific error is 0x8007000d: The data is invalid". Once you dismiss the dialog, you see the normal task details, but cannot edit the user field (greyed out and blank). You could however create manual shadow copies, so that pretty much narrowed it down to a problem with the scheduled task rather than shadow copies itself.
Some searching on Technet and the MS Knowledgebase drew a blank (or at least nothing appearing to be directly relevant). There's an article here which gives some information which is close but only allows you to setup the task again with a domain account. I didn't want to do that as the Shadow Copy scheduled task is supposed to run under the NT AUTHORITY\SYSTEM account.
However, I bow to Anil's greater knowledge from his blog entry here, specifically the update part at the end. Indeed, deleting C:\Documents and Settings\All Users\Application
Data\Microsoft\Crypto\RSA\S-1-5-18\d42cc0c3858a58db2db37658219e6400_xxxx", deleting the scheduled task, disabling shadow copies and setting it back up again with a schedule creates it correctly.
Thanks Anil!
Cheers,
John.
[This post travelled in time. John is offline for a few days. It may take a while before any comments are published.]
Update June 2008. Apologies, the screenshots are lost in time.
Comment Notification
If you would like to receive an email when updates are made to this post, please register here
Subscribe to this post's comments using
Comment Policy: No HTML allowed. URIs and line breaks are converted automatically. Your e–mail address will not show up on any public page.
