Error returned while creating the volume shadow copy ffffffff
05/20/2011 — Russ- When you perform a backup operation by using the NTBackup tool, the following event is logged in the Application log:
Event Type: Error
Event Source: NTBackup
Event ID: 8019
Description: End Operation: Warnings or errors were encountered. Consult the backup report for more details.Note If you view the backup log file, the following information is displayed:Error returned while creating the volume shadow copy:0xffffffff - If you access the properties of a volume and then click Shadow Copies, you receive one of the following error messages:
Error 0x8004230F: The shadow copy provider had an unexpected error while trying to process the specified operation.Error 0×80004002: No such interface supported
- One of the following events is logged in the Application log:Event Type: Error
Event Source: VSS
Event ID: 20
Description: Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy Service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and Name VSSEvent is [0x80040154].Event Type: Error
Event Source: VSS
Event ID: 20
Description: Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy Service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and Name VSSEvent is [0x80004002].Event Type: Error
Event Source: VSS
Event ID: 8193
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0×80040154.Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0×80004002.Event Type: Error
Event Source: VSS
Event ID: 12302
Description: Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.
CAUSE
This issue occurs because the VSS system files are not registered….
RESOLUTION
Note This article is not for use with Windows Vista, with Windows Server 2008, o…
To have us fix this problem for you, go to the “Fix it for me” section. If you prefer to fix this problem yourself, go to the “Let me fix it myself” section.
Fix it for me
To fix this problem automatically, click the Fix it button or link. In the File Download dialog box, click Run and then follow the steps in the Fix it Wizard.
Notes
- This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
- If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
Then, go to the “Did this fix the problem?” section.
Let me fix it myself
To resolve this issue, follow these steps:
- Click Start, click Run, type cmd, and then click OK.
- Type the following commands at a command prompt. Press ENTER after you type each command.
- 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
Note The last command may not run successfully.
- Perform a backup operation to verify that the issue is resolved.
Did this fix the problem?
- Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support (http://support.microsoft.com/contactus) .
- We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the “Fix it for me (http://blogs.technet.com/fixit4me/) ” blog or send us an email (mailto:fixit4me@microsoft.com?Subject=KB) message.
Back to the top