Sunday, June 14, 2009

Volume Shadow Copy Broken

Had the following error:

Error: 0x80042304: The volume shadow copy provider is not registered in the system.




To fix create a bat file with the following commands:


cd /d %windir%\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
Net start vss
Net start swprv


Run the bat file... fixed

11 comments:

  1. Did you need to reboot after running the batch-file?

    ReplyDelete
  2. I can't remember to be honest mate. This was a few months ago now! This worked for me in my situation... I guess schedule in a reboot and let us know if it worked?

    ReplyDelete
  3. it works. thanks

    ReplyDelete
  4. Thank you so much...been chasing shadows for hours. This did the trick!

    ReplyDelete
  5. Just wanna say that it doesn't works for W2k8.
    MS doesn't have an idea what happens with VSS service in W2k8. There's a lot of posts in a lot of forums about the same issue; and MS only have one kb for this, and it's for W2k3 (http://support.microsoft.com/kb/940032/en-us). And more critical, if you read the kb, you can see inside: "This article is not for use with Windows Vista, with Windows Server 2008, or with later operating systems. Starting with Windows Vista and with Windows Server 2008, Windows component installation is manifest based. If you try to manually register specific components, such as those that are described in this "Resolution" section, in the operating systems that are mentioned in this note, unexpected results may occur that may require reinstalling Windows to resolve"
    Painful...

    ReplyDelete
  6. Thank you thank you and thank you again, I was trying to fix it for three days in a row on company server, did the regsrv* and it did not work I guess I forgot to register one.

    ReplyDelete
  7. This worked me too, exactly the same error, I did not need to reboot my 2003 standard server.
    Thanks

    ReplyDelete
  8. This worked me too, exactly the same error, I did not need to reboot my 2003 standard server.
    Thanks

    ReplyDelete
  9. Keep up the good work! After much digging this helped me out.

    ReplyDelete
  10. Isso deu certo muito bom

    ReplyDelete