Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About dbookbinder

  • Rank
    Occasional Forum Poster
  1. dbookbinder

    VSS crashes, can't duplicate C volume

    In case anyone else has this problem and finds this thread, I was apparently able to solve the shadow copy / bitlocker parts of the problem by using mountvol /r to remove old mount volume data and mountvol /e to enable automatic mounting of new volumes. I don't know why this worked, but it appears to have eliminated the bitlocker errors, which in turn appears to have eliminated the VSS errors when I try to do an open file backup with Retrospect. Still not positive all is as it should be, but so far so good -- I did do a normal backup of my system volume.
  2. dbookbinder

    VSS crashes, can't duplicate C volume

    Using a tool called Tweaking.com Windows Repair, I was able to restore VSSADMIN functionality. However, VSS still fails to work with Event Log errors 8193 and 12293 and the Retrospect backups fail with error -1017 ( insufficient permissions). Ideas, anyone?
  3. dbookbinder

    VSS crashes, can't duplicate C volume

    One other detail: At about the same time, I started getting errors from Bitlocker at boot time. As I am running Windows 7 Home, bitlocker should not be on the system. I am wondering if something installed bitlocker on the system in a broken fashion, and that's causing a problem with VSS. I have no idea how to decrypt anything that might be encrypted and then remove bitlocker, if that's the case, and would be grateful for some pointers. What I've found on the Internet seems to apply only to a full, working installation of Bitlocker.
  4. dbookbinder

    VSS crashes, can't duplicate C volume

    A bit more information: I am running Windows 7 Home 64-bit. When I try to run VSSADMIN to find out the writers or to delete shadow copies, I get the following errors in the Event Log and VSSADMIN also returns an error. Event Log error 22: 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 {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and Name IVssCoordinatorEx2 is [0x80040154, Class not registered]. Event Log error 8193: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040154, Class not registered From VSSADMIN, I get: Error: A Volume Shadow Copy Service component encountered an unexpected error. Check the Application event log for more information. And finally, when I try to register the components of VSS, several of them do not register or cannot be found. Yet, I have run System File Checker with no errors. This problem seems to only affect Retrospect's use of Open File Backup. I can run Paragon Drive Backup, which also uses VSS, and can create Restore points. Any help is greatly appreciated! I have tried several purported VSS fixes found on the Internet, but none have been successful and most I have not been able to run to completion because VSSADMIN does not run on my system, and none of the troubleshooting I have done has gotten it to run, either.
  5. Until this week, I've been able to create a Duplicate of my System volume with just a couple of warnings. Now, however, Retrospect is unable to start VSS and the Duplicate operation begins with the error "Can't use Open File Backup option for System (C:), error -1017 ( insufficient permissions)", then produces about 70 errors before quitting with " Can't duplicate System State, error -1017 ( insufficient permissions)". This is new behavior, but I haven't been able to trace it to any particular update or other change. The Event Log errors are always the following: 8193: Volume Shadow Copy Service error: Unexpected error calling routine Cannot find anymore diff area candidates for volume \\?\Volume{32eb0121-e478-11de-884b-806e6f6e6963}\ [0]. hr = 0x8000ffff, Catastrophic failure 12293 Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({35596376-1998-4466-bbb5-d655bbc6728e}) [hr = 0x80042302, A Volume Shadow Copy Service component encountered an unexpected error. I have used Disk Cleanup to clean out old shadow copies and restore points, to no avail, and I have re-registered the VSS components in the Registry, but the problem persists. Anyone else have this problem and know how to resolve it? I'm using Retrospect 7.7.620. Thanks! - David
  6. Retrospect 7.7 appears to have a "feature" that 6.5 did not, and that I'd like to turn off. It displays the redundant "Overview" screen on startup, regardless of whether I've closed it in the previous session. Is there any way to turn this off? I've been able to cover it up with the activity monitor window (which I do want to see), which in practice is good enough, but I would prefer just to not display it. Thanks! David
  7. I did a search like this but was unable to find a match for the particular error in the Event Viewer that shed any light on the problem. Now I'm wondering if I even need VSS with Retrospect. When I did a backup, I got no significant errors with Open File Backup turned off, and I'm wondering if that's because Retrospect skipped open files or if it was able to read them and back them up without making a copy first. - David
  8. I forgot to add that sometimes I get errors such as these, just before Retrospect gives up: TPCFileLoc::GetInfo: UFindFirstFile failed, \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Program Files\Java\jre1.5.0_06\lib\zi\Europe\Zaporozhye, winerr 55, error -1102 TPCFile::BackupReadOpen: UCreateFile failed, \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Program Files\Java\jre1.5.0_06\lib\zi\Europe\Zaporozhye, winerr 55, error -1102 Thanks, David
  9. Hi, Waltr and Foster. The problem definately has to do with VSS not working correctly with Retrospect, though why that has occurred is a mystery. If I turn off Open File Backup, then the C: backup runs to completion. When it's turned on, it aborts after about 19 minutes, almost every time, with many thousands of errors, or it ends with a VolSnap error in the Error log. It seems to me that if the hard drive were the issue, or the cable, or the controller, I would have other indications of problems. So... I'm wondering how I can get VSS to run properly. Any pointers to how to troubleshoot it are welcome. Thanks, David
  10. In the last couple of weeks, I've started getting many thousands of -1101 errors while backing up my C: partition to a USB drive. The script I'm using and hardware I'm using hasn't changed, so I'm baffled. The files that Retrospect claims it can't read are in the Windows folder. Occasionally, I also get a Volume Shadow Copy error in the Event Viewer, Error 14 from VolSnap, "The shadow copy of volume C: was aborted because of an IO failure." A chkdsk of the C: drive shows no errors, and the drive is less than a year old. Any suggestions of how to troubleshoot (and fix) this problem? Thanks, David
  11. Thanks. Your information, however, confirms that this error message makes no sense. I was doing a Duplicate, not a Backup, when I got the error. There was no Backup Save Set being used; Duplicate merely duplicates the files on a file-by-file basis. I don't know what error really occurred, but the Snapshot error message makes no sense in the context of a Duplicate operation. Nate? - David
  12. How do I determine the number of snapshots? Since what I'm doing is a Duplicate, not a Backup, I would have imagined that there were no snapshots (though I confess I'm not sure I know what a snapshot is). - David
  13. I recently got this error when attempting to back up my C drive to a USB hard drive. Please explain what happened and what its significance is (and how to avoid such errors in the future). I was running a Duplicate of my C drive. Thanks, David + Duplicate using Duplicate Drive C to Drive H at 11/4/2004 11:13 PM VssWAddVolToSnapshot: AddToSnapshotSet failed for volume \\?\Volume{7b0ed122-db9f-11d8-92b2-806d6172696f}\, winerr -2147212521, error -3043 Can't use Open File Backup option for System (C:), error -3043 (the maximum number of Snapshots has been reached) To volume C on Buslink_40g (H:)...
  14. I'm just now running a script that duplicates all my photo files from my hard drive to an external USB hard drive. In the past, with earlier versions of Retrospect, running this script has duplicated only the new or changed files and left identical files alone. Now, it's copying all 48GB instead of the maybe .5 GB that have changed. The external drive is a FAT32 formatted drive. When I run a similar script to duplicate the files from my hard drive to an NTFS external USB drive, it duplicates only the changed or new files. What gives? How can I get Retrospect to leave the files that are already identical alone when copying to the FAT32 drive, as earlier versions of Retrospect did when I copied files from my old Win98SE machine to this drive. Thanks, David
  15. dbookbinder

    Can't successfully back up to DVD+RW media

    The problem I'm having is with DVD+RW media that has a write speed of 4x, which is the maximum write speed of the drive with DVD+RW media, so there is a match between the two. The system is new, and has an Athlon 2600+ processor running at somewhat over 2GHz. It does not have a problem writing to 8x DVD+R media, only with the DVD+RW rewritable media. I can try reducing the write speed, and that may solve the problem, but I don' know why I should need to, since the drive happily writes 8x media at 8x and 4x media at 4x when I use Nero. It seems, in other words, to be a Retrospect problem. (I wasn't aware of the Set Write Speed command; thanks for pointing me to it.) Thanks for thinking about this, David