If you are getting cocreateinstanceex in hr error 0x80004002 then this user guide should help you.
This article resolves issues where events with IDs 8019, 20, 8193, 12302, or in the Application log are being sucked in. You will receive an error message Error 0x8004230F or 0x80004002.
One or more of the following symptoms occurs on a Microsoft Windows Server 2003-based computer that is running Volume Shadow Copy Service (VSS):
Kogyes we are performing a backup operation using NTBackup tool, the following problem is logged in the application log:
Event type: error Event Source: NTBackup Event ID: 8019 Description: End of activity: Warnings or errors occurred in the past. See the backup report for more details.
Why does CoCreateInstance fail to find the server?
For CoCreateInstance to function properly, the server must be qualified in the registry. This means that if you do not register a shared server, CoCreateInstance will not trust the server. Also your application must have a powerful inproc server (DLL server) loaded, only 64 bit applications cannot load 24 bit DLLs.
When viewing the log file, you can see the following information:
Error creating a specific shadow copy: 0xffffffff
If you access feed content and then visit shadow copies, you will receive one of the following error messages:
Error 0x8004230F: The shadow copy provider encountered an unexpected error while trying to process an operation of the specified type.
Error 0x80004002: This type of client interface is not supported
One of the following events is literally logged in the Application log:
Event type: error Event Source: VSS Event ID: 20 Description: Errorand Volume Shadow Copy Service: The core component required for the Volume Shadow Copy Service is not registered. This can happen if there was an error installing Windows or creating a shadow copy provider. The entire CLSID returned by CoCreateInstance to the college failed faf53cc4-bd73-4e36-83f1-2b23f46e513e, and the VSSEEvent name was [0x80040154].
Event type: error Event Source: VSS Event ID: 20 Description: Volume Shadow Copy Service error: A component required for the Volume Shadow Copy Service may not be registered. This could be if there was an error with the Windows location or when installing the shadow copy provider. An error is returned after instantiating the On class with the CLSID faf53cc4-bd73-4e36-83f1-2b23f46e513e and the name VSSEEvent [0x80004002].
Event type: error Event Source: VSS Event 8193 Description: ID: Volume Shadow Copy Service error: An unexpected error occurred when calling the CoCreateInstance procedure. hour is 0x80040154.
Event type: error Event Source: VSS Event Category: No Event ID: 8193 Description: Shadow Service ErrorVolume Copy Oops: An unexpected error occurred when calling the CoCreateInstance procedure. Standard = 0x80004002.
Event type: error Event Source: VSS Event ID: 12302 Description: The Volume Shadow Copy Service has failed. An internal inconsistency occurred while trying to contact the authors of the shadow copy service. Make sure the Event Service and then the Volume Shadow Copy Service are fully functional.
Click Start, click Run, select Option cmd and click OK.
Enter command focus at the command line. After issuing a command for each command, press ENTER.
cd% windir% system32
Net / d Stop Against Against
Define network swprv
vssvc / register
regsvr32 / i swprv.dll
regsvr32 / i eventcls.dll
The last command may fail.
Please back up to see if the issue is resolved.
Steps To Reproduce This Issue
At the command prompt, enter the following command. Press ENTER after entering each command.
regsvr32 / u sfprv.dll
Try performing a backup operation.
2 minutes to read
When customers view the document backup log, they see the following information:
This article is not intended for use with Windows Vista equipped with Windows Server 2008 or any other traditional operating system. When starting Windows Vista and with Windows Server 2008, the installation of Windows components appears. If you try to manually register prerequisite components, as usually described in this Resolution section, next to known operating systems in this note, you are likely to receive unexpected results Anything that may require you to reinstall Windows to fix the problem.