Event ID 12302 Source VSS
| Event ID | 12302 |
| Source | VSS |
| Type | Error |
| 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. |
| English, please! | Request a translation of the event description in plain English. |
| Concepts to understand |
What is Volume Shadow Copy Service (VSS)? What is a shadow copy? |
| Comments |
Anonymous
(Last update 11/10/2009): M940184 solved the problem for me, apparently, a registry key might be corrupted. Anonymous (Last update 4/13/2009): the same issue with regard to the Visio key. Had uninstalled Visio, but the separate catalogue key remained - deleted this, and VSS was back and running. Mihai Andrei (Last update 8/4/2007): This issue can occur because the VSS system files are not registered. See M940032 for information on how to solve this problem. This problem occurs when you uninstall a program that is listed in this registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\Catalogs but only the location information is removed from the registry subkey. See M907574 to solve this problem. Anonymous (Last update 9/29/2006): To fix this problem do the following: 1. Backup the follwing regkey: HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions 2. Erase the regkey 3. Reboot. 4. Verify that things are working by running "vssadmin.exe list writers". Anonymous (Last update 6/28/2006): In my case, Microsoft update M913648 did the trick. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Charles L. (Last update 5/27/2005): System started experiencing this error repeatedly and all VSS backups would fail. NTBACKUP also could not backup a simple text file. Running the command “vssadmin list writers” normally returns a long list of writers. The affected system returned nothing for this command. The fix the problem I reregistered ole32.dll. The syntax is as follows: “c:\regsvr32 ole32.dll”. The server will need to be restarted after this command is executed. Afterwards "vssadmin list writers" returned the proper list and the backup worked again. Ionut Marin (Last update 10/12/2004): From a newsgroup post: "I seem to have solved the problem. Thanks to the “Google Thread”. It seems that when I was beta testing Office 11 (a.k.a. Office 2003), Visio installed a key in the Content Indexing Service creating a separate index catalog for Visio files. When I uninstalled Visio, that key did not go away. Because CISVC was disabled, it never made a difference to content indexing. However, it certainly got on the wrong side of VSS. I deleted “HKLM\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs\visio” and now VSS seems to run OK. Go figure". |
| Links | M907574, M940032, Google Thread, M940184 |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Custom search | The custom search information is available to subscribers only. |
| Feedback | Send comments - Notify me when updated |
| Print version |