共用方式為

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 AUTHORITYSYSTEM 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 SettingsAll UsersApplication
DataMicrosoftCryptoRSAS-1-5-18d42cc0c3858a58db2db37658219e6400_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.

Comments

  • Anonymous
    January 01, 2003
    PingBack from http://blueglowy.com/2008/05/13/shadow-copy-failures/

  • Anonymous
    January 01, 2003
    PingBack from http://availabledomains.biz/?p=1635

  • Anonymous
    June 29, 2006
    Thanks for this tip. Just had exactly the same problem with shadow copies not running on Server 2003 R2. Copies now running. :)

  • Anonymous
    June 30, 2006
    YOU ARE THE MAN... I have been searching for hours trying to fix all my scheduled tasks, they all had this problem. The fix is indeed:

    DELETE ->

    C:Documents and SettingsAll UsersApplication
    DataMicrosoftCryptoRSAS-1-5-18d42cc0c3858a58db2db37658219e6400_xxxx

  • Anonymous
    July 26, 2006
    Thanks a lot.
    had the same troubles after moving a server from domain to domain.
    Deleting the files in there did solve the problem.
    Even MS Knowledgebase did not have that solution.

    Thanks again and greetings from switzerland
    Alex

  • Anonymous
    August 17, 2006
    Any time! Glad I could help :-)

  • Anonymous
    August 23, 2006
    Wow, talk about serendipity. I had "figure out what the @#$@#% is wrong with Shadow Copies" on my home data server tonight, and I have many better things to do. Just before I started, I decided to stall by looking through your past blog entries as I've recently subscribed via NewsGator. Voila!
    <Twilight Zone Theme>

    Thanks!

    Sean

  • Anonymous
    March 17, 2008
    Great thanks. Fixed the problem for me. Think it got broken when I demoted a domain controller to be a normal server.

  • Anonymous
    March 21, 2008
    Thanks so much for the posting this info.  This helped me with fix my problem.  

  • Anonymous
    March 23, 2008
    Thanks for this man, you just saved me many hours and much vodka from frustration. Worked like a charm :)

  • Anonymous
    April 15, 2008
    Thanks, man! Good information is rare in some cases. Yours was very valuable today!

  • Anonymous
    July 10, 2008
    Great ... Thanks ... Fixed my problem

  • Anonymous
    September 16, 2008
    Wow!  That worked like a charm.  I'm so glad that you had this information available. Thanks so much!

  • Anonymous
    May 22, 2009
    youre cool! thanx from russian village golievo!

  • Anonymous
    May 23, 2009
    Great fix - very obscure! Mine broke when promoting a server to a DC.

  • Anonymous
    September 10, 2009
    I noticed that there was an unknown account with security priveleges to that file before I deleted it.  Similar to another poster...I think mine broke when I promoted to a DC.  This is a permissions issue.  The old machine accounts are gone, but the settings that refer to them are still hanging around in the scheduled tasks.  Thanks very much for posting this.  Immensely helpful.

  • Anonymous
    January 26, 2012
    I think mine broke when I demoted the server from a DC to a member server.  This fixed it though. Thank you for sharing the fix with us!!

  • Anonymous
    March 20, 2012
    You legend. I also demoted a 2003 machine from FP/DC to just FP. This seems to have worked!

  • Anonymous
    May 29, 2013
    Thank you! This was the one and only that helped me after a long web sdearch....

  • Anonymous
    August 29, 2013
    Well at least someone was paying attention in class. Works great. Thanks a bunch.

  • Anonymous
    April 30, 2014
    Thanks for doing all the leg work on this one, John. We had a client call in with this exact problem and luckily after some mad googling I found this post.

  • Anonymous
    July 08, 2014
    Great Fix

  • Anonymous
    December 15, 2014
    Thanks a lot. that worked!