Volume Shadow Copy Service error


  • Event 12292 -

    Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {463948d2-035d-4d1d-9bfc-473fece07dab} [0x80070005, Access is denied.

    Event 13 -

    Volume Shadow Copy Service information: The COM Server with CLSID {463948d2-035d-4d1d-9bfc-473fece07dab} and name HWPRV cannot be started. [0x80070005, Access is denied.

    Event 12289 -

    Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{869ecff5-0cc6-11e2-93f1-00155d03f90d} - 0000000000000064,0x0053c008,000000E100014880,0,000000E100015890,4096,[0]).  hr = 0x80070057, The parameter is incorrect.

    I'm receiving these errors on both virtual and physical installs of Windows Server Standard 2012.  The VSS seems to work on the local drive, but fails for iSCSI connected drives.  Any thoughts?

    Wednesday, October 03, 2012 9:25 PM


All replies

  • Hi,

    Sometimes the event 12292 could be caused by third party VSS provider. So please first run:

    vssadmin list writers

    Check if there is any third party VSS provider listed. If so, you could test to backup and delete it from HKLM\System\CurrentControlSet\Services\Vss\Providers to see if it will get to work on iSCSI drives.

    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact

    Tuesday, October 09, 2012 8:15 AM
  • Please try the following fix for configuring the credentials:

    Microsoft Partner

    • Proposed as answer by rEMOTE_eVENT Wednesday, October 10, 2012 10:53 AM
    • Marked as answer by dbiz Friday, October 12, 2012 5:48 PM
    Tuesday, October 09, 2012 9:32 PM
  • Thanks r_EMOTE_eVENT,

    This helped me track dow the issue.

    • Edited by dbiz Friday, October 12, 2012 5:49 PM problem solved
    Friday, October 12, 2012 3:52 PM
  • Thanks a lot ... you made my day!

    A question I'd ask Microsoft as this is very troublesome - why is there no hint or info on the MS download pages or in the installation program?

    In fact you install an update like dozens of others - but afterwards, the complete VSS system is hosed until you configure the creds (in case you knew) or uninstall the hotfix. It renders your backup software unusable (Symantec Backup Exec for example, except you are able to dedicatedly choose a VSS provider) and breaks other VSS-based stuff like NetApp SnapVaults.

    I also see problems in server farms deploying the update - especially the "set the credentials" part. And updating the credentials when regular password changes occur.

    Nevertheless you spared me a lot of grief in a storage project, thanks again :-)

    Thursday, October 25, 2012 7:00 PM