RandyStevens Posted March 30, 2009 Report Share Posted March 30, 2009 (edited) When I try to execute an open file backup, Retrospect hangs at the "preparing for backup" stage. The only way to clear the hang is to use the Windows Task Manager to kill the "retrospect.exe" process (or reboot). Simply cancelling the backup will not work. System: Windows Vista Home Premium SP1 Retrospect: Professional Version 7.6.126 with Driver and HotFix 7.6.2.101 When the hang occurs, there are 4 event messages posted from VSS listed in the Windows Event Log. All of these are posted with the same timestamp: [color:red] Log Name: Application Source: VSS Date: 3/30/2009 5:44:30 AM Event ID: 12292 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Randy08 Description: Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {790f2886-9889-4c99-8ef5-531add05d044} [0x8007007e]. Operation: Obtain a callable interface for this provider Add a Volume to a Shadow Copy Set Context: Provider ID: {262b716e-bb23-41b5-aaef-e2c15e767167} Class ID: {790f2886-9889-4c99-8ef5-531add05d044} Snapshot Context: 0 Execution Context: Coordinator [/color] [color:brown] Log Name: Application Source: VSS Date: 3/30/2009 5:44:30 AM Event ID: 13 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Randy08 Description: Volume Shadow Copy Service information: The COM Server with CLSID {790f2886-9889-4c99-8ef5-531add05d044} and name SW_PROV cannot be started. [0x8007007e] Operation: Obtain a callable interface for this provider Add a Volume to a Shadow Copy Set Context: Provider ID: {262b716e-bb23-41b5-aaef-e2c15e767167} Class ID: {790f2886-9889-4c99-8ef5-531add05d044} Snapshot Context: 0 Execution Context: Coordinator [/color] [color:red] Log Name: Application Source: VSS Date: 3/30/2009 5:44:30 AM Event ID: 12292 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Randy08 Description: Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {790f2886-9889-4c99-8ef5-531add05d044} [0x8007007e]. Operation: Obtain a callable interface for this provider List interfaces for all providers supporting this context Check If Volume Is Supported by Provider Add a Volume to a Shadow Copy Set Context: Provider ID: {262b716e-bb23-41b5-aaef-e2c15e767167} Class ID: {790f2886-9889-4c99-8ef5-531add05d044} Snapshot Context: 0 Snapshot Context: 0 Execution Context: Coordinator Provider ID: {00000000-0000-0000-0000-000000000000} Volume Name: \\?\Volume{7526c4bc-0b10-11dd-9d06-806e6f6e6963}\ Execution Context: Coordinator [/color] [color:brown] Log Name: Application Source: VSS Date: 3/30/2009 5:44:30 AM Event ID: 13 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Randy08 Description: Volume Shadow Copy Service information: The COM Server with CLSID {790f2886-9889-4c99-8ef5-531add05d044} and name SW_PROV cannot be started. [0x8007007e] Operation: Obtain a callable interface for this provider List interfaces for all providers supporting this context Check If Volume Is Supported by Provider Add a Volume to a Shadow Copy Set Context: Provider ID: {262b716e-bb23-41b5-aaef-e2c15e767167} Class ID: {790f2886-9889-4c99-8ef5-531add05d044} Snapshot Context: 0 Snapshot Context: 0 Execution Context: Coordinator Provider ID: {00000000-0000-0000-0000-000000000000} Volume Name: \\?\Volume{7526c4bc-0b10-11dd-9d06-806e6f6e6963}\ Execution Context: Coordinator [/color] I've tried uninstalling and re-installing Retrospect, but it does not help. As a workaround, I have disabled Open File Backup. This allows the backup to run, but there are many files that are missed during the backup. I would like to get this working. Any help would be appreciated. Edited March 30, 2009 by Guest Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 30, 2009 Report Share Posted March 30, 2009 The errors are coming from WIndows and not Retrospect. Reinstalling Retrospect will not fix a Windows VSS error. Retrospect is hanging because it is waiting for a reply from the VSS service which isn't coming. I don't know what those errors mean, you can check with Microsoft or try to google the Event ID's listed in the Event Logs above. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 30, 2009 Report Share Posted March 30, 2009 example: http://www.eventid.net/display.asp?eventid=12292&eventno=4714&source=VSS&phase=1 http://www.itnewsgroups.net/group/microsoft.public.windows.server.general/topic2482.aspx http://www.tomshardware.com/forum/198961-46-event-12292-event-event-source Quote Link to comment Share on other sites More sharing options...
RandyStevens Posted March 30, 2009 Author Report Share Posted March 30, 2009 I believe I discovered the problem and the solution! I had installed Norton Ghost 14.0 on my computer so I could get backups for my Vista x64 computer. (OK, I hated it, but at the time Retrospect 7.5 did not support Vista x64.) When Retrospect 7.6 came out I started using both Retrospect and Ghost in parallel for awhile. Eventually, I uninstalled Ghost from the system. However, the uninstall program left substantial remains in the Windows Registry. Apparently the "Symantec Software VSS Provider" was still hanging around as a VSS service even though the underlying software was removed. The VSS Events that were generated when I attempted an open file backup were being generated from the Symantec VSS Provider, not the Microsoft VSS provider that came with Vista. Here is what I did to get the open file backkups working again: 1. Stop "Symantec SymSnap VSS Provider" service, if it is running. Configure it so its startup is Disabled. 2. Using regedit, delete all registry keys containing the following strings: Symantec Software VSS Provider 262b716e-bb23-41b5-aaef-e2c15e767167 Norton Ghost 3. Reboot the computer After rebooting, I opened a command windows and typed "vssadmin list providers". The Symantec VSS provider was no longer listed -- just the Microsoft one was there. I tried the open backup and it worked. There were no errors posted in the Event log. In addition, a "vssadmin list shadows" showed that 5 shadow copies were created to support the backup -- these all used the Microsoft VSS provider. Quote Link to comment Share on other sites More sharing options...
cheesechoker Posted April 1, 2009 Report Share Posted April 1, 2009 THANK YOU RANDY IT WORKED PERFECTLY I registered just to post this Quote Link to comment Share on other sites More sharing options...
mlts22 Posted April 3, 2009 Report Share Posted April 3, 2009 Excellent advice. That addressed a similar problem that an acquaintance was having. This is definitely FAQ material. For most things, if I end up with VSS errors, I run CHKDSK on the volumes (rebooting when doing the system volume.) Quote Link to comment Share on other sites More sharing options...
bdsa Posted April 29, 2009 Report Share Posted April 29, 2009 I had the same problem and the event viewer told me nothing! Did you have any success with the NPS Database backup failure or NPS VSS Writer backup failure solution? Thanks. Bruce Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.