Jump to content

RandyStevens

Members
  • Content count

    6
  • Joined

  • Last visited

  • Days Won

    1

RandyStevens last won the day on May 7 2018

RandyStevens had the most liked content!

Community Reputation

2 Neutral

About RandyStevens

  • Rank
    Newbie
  1. RandyStevens

    Error -1103 after Windows 10 April Update

    I upgraded from Retrospect 15.0 to 15.1 and that has resolved all problems with doing the open file backups.
  2. RandyStevens

    Error -1103 after Windows 10 April Update

    Lucky_Phil and others, I am now seeing similar problems. When the script runs from the scheduler on the host (local) computer, it fails during a scan of the C: drive. No problems with other drives on the host computer. Running the script via the Run pull-down will run successfully. I believe this may be a different problem than the client issues, although both are throwing the same -1103 error on the host. The open file backup on the client C: drive is failing and throwing VSS errors in the clients' event logs. The error propagates back to the host as a -1103 error. This problem only occurs on the C: drive, not on other drives on the client. For the problem backing up on the local machine, I can find no related problems in the windows event logs.
  3. RandyStevens

    Error -1103 after Windows 10 April Update

    I am running Retrospect 15 and I'm having similar problems backing up a Windows 10 (Build 1803) laptop as a client. The client has 2 drives: C: (the OS) and Z: (a recovery partition). There are no issues backing up the host, which is a Windows 10 (Build 1803) desktop computer. No issues backing up 2 other clients that are Windows 7 computers. The first backup of the client laptop was working. It passed through the scan and was backing up files. However, I had to stop the backup midway for unrelated reasons. The next 2 attempts at a backup made it successfully through the scan for drive C: and some files were backed up. However, the -1103 error was thrown for the C: drive and the backup aborted. No issues at all backing up the Z: drive. All subsequent attempts for open file backup on the client resulted in the C: drive failing during the scan and no problems with the Z: drive. I confirmed VSS errors in the event log on the client at the same time as the -1103 errors. I can do a backup with "open files" disabled, although there are several warnings for sharing violations, which I assume would be expected. I have submitted a support ticket.
  4. I had a similar problem with Open File Backup hanging. See the following thread: Open File Backup hangs - VSS errors
  5. RandyStevens

    Open File Backup hangs - VSS errors

    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.
  6. RandyStevens

    Open File Backup hangs - VSS errors

    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.
×