Member Avatar for amadeus47

The message from Windows Logs\Application for Error 8193 is: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040154, Class not registered

The message from Windows Logs\Application for Error 22 is: 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 {4e14fba2-2e22-11d1-9964-00c04fbbb345} and Name CEventSystem is [0x80040154, Class not registered].

Operation:
Subscribing Writer

Context:
Writer Class Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Name: IIS Config Writer
Writer Instance ID: {2eb57964-9547-43c9-bfc3-def722c5e46f}

Among options tried unsuccessfully so far are:

http://social.msdn.microsoft.com/Forums/en/windowsgeneraldevelopmentissues/thread/eadf5dcd-fbd1-4224-9a56-b5843efebb15?prof=required

http://support.microsoft.com/kb/940184

Any suggestions are greatly appreciated.

Regards,

Mike

  • 2 Contributors
  • 2 Replies
  • 431 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by amadeus47

Dani AI

Generated

Short expert summary and action plan

The Application log entries you posted (Event 8193 / 22, CoCreateInstance hr = 0x80040154 for CEventSystem) point to a COM/COM+ registration problem with the Event system that VSS depends on — so ’s registry idea was a sensible check, and ’s move toward the COM+/EventSystem area is the right direction. The practical, minimally-invasive steps below follow Microsoft guidance and avoid risky “blind” DLL re‑registrations.

Suggested checks and fixes (in order)

  1. Confirm the COM+ Event System is present and running. Use Services or these commands from an elevated prompt:

    sc query EventSystem
sc config EventSystem start= auto
sc start EventSystem

    COM+ Event System (EventSystem) is required by SENS/VSS; make sure it is Automatic and started. (learn.microsoft.com)

  2. Correct the Event class TypeLib entry (Microsoft’s supported fix when writers/providers are missing). In regedit back up the registry, then edit the TypeLib value under the EventSystem EventClasses key so it points to the system EventCLs file:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\EventClasses\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}
TypeLib  =  %SystemRoot%\System32\EVENTCLS.DLL

    After editing, restart COM+ Event System and the Volume Shadow Copy service, then verify writers. This is the Microsoft-recommended registry correction for Class-not-registered VSS errors. (learn.microsoft.com)

  3. Verify VSS state and providers

    vssadmin list writers
vssadmin list providers

    Look for missing/hung writers or unexpected third‑party providers (Acronis, VMware snapshot drivers, etc.) that can cause provider/class registration problems. Remove or reinstall conflicting snapshot providers if present. (learn.microsoft.com)

  4. Repair system files if the registry/service fixes don’t help

    sfc /scannow

    System File Checker can restore corrupted system DLLs used by COM/VSS. If SFC finds and repairs files, reboot and re-check VSS. (learn.microsoft.com)

Notes and cautions

  • Back up the registry before edits and create a restore point. Manual DLL re-registration (regsvr32) is historically used but can be unsafe on Vista/7+ because of manifest-based components — prefer the registry TypeLib fix and SFC first. (learn.microsoft.com)

If these steps still leave Event IDs 8193/22 in the log, capture the exact VSS entries (full event text) and the outputs of vssadmin list writers / vssadmin list providers — those items will indicate whether a specific provider or writer remains unregistered and whether a deeper COM+ catalog repair or OS repair is needed.

Recommended Answers

All 2 Replies

Member Avatar for Technocrate25

According to the research, the issue may be caused by an invalid entry inside the following registry sub tree.

HKey_Local_Machine\Software\Microsoft\Windows NT\CurrentVersion\ProfileList

Please open the registry editor with regedit.
Expand and local to the subtree, check if there is an entry that has a ".bak" value appended. If so, this may be cause the failure when trying to resolve the SID of the writer.

Please backup the registry key first, and then delete that entry with the extra ".bak"

Then you may reboot the problematic server to check if it the issue can be fixed.

Member Avatar for amadeus47

thanks for the reply. Checked all the subtrees. All were clear of any .bak entries.
Investigation seems to point to a COM+ component not properly registered or corrupt (COM+ Applications). Checking that.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.