0

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://forums.msrportal.com/archive/index.php?t-24866.html

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

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

http://www.msfn.org/board/topic/70962-restore-volume-shadow-copy-vss-and-ms-software-sha/page__s__14c8dc10ac9e4b9cc0a4a3f08e6e8eaf

http://support.microsoft.com/default.aspx?scid=kb;en-us;833167

Any suggestions are greatly appreciated.

Regards,

Mike

2
Contributors
2
Replies
3
Views
7 Years
Discussion Span
Last Post by amadeus47
0

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.

0

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.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.