MRiley Posted March 23, 2010 Report Share Posted March 23, 2010 Running Retrospect 7.0 under MS-Windows XP (Media Edition) with SP3 installed. Had a major software problem that wrecked the operating system. I had to do a full restore. Now, when I run a backup I'm getting this error message (in the operations log): "Can't use Open File Backup option for AVT-LAPTOP3-C (C:), error -1017 (insufficient permissions)" I'm also getting other error messages which I think will go away if I can fix the "Open Files Backup" error. Some of the other errors are related to open files and others are permission errors. So clearly I have a "permissions" problem somewhere. I checked the log file history and this error was never appeared until after I had to do the restore. Actually, almost all backups prior to the recovery were error free. Anyone know What and/or How I can fix this ?? Thank you. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 23, 2010 Report Share Posted March 23, 2010 7.0 has never been tested on XP SP3, so I do not know if this is a compatibility issue or anything. You could download a trial to the latest version. Quote Link to comment Share on other sites More sharing options...
MRiley Posted March 23, 2010 Author Report Share Posted March 23, 2010 Thanks. But how would that explain that it all worked fine until I had to do a restore ?? Is there anywhere in Retrospect to set/change "permissions" ?? SP3 was installed quite a while ago with no apparent ill effects to any application. Quote Link to comment Share on other sites More sharing options...
MRIS Posted March 25, 2010 Report Share Posted March 25, 2010 I've seen this before, and it's basically a case that the volume shadow copy mechanism built into XP isn't working quite right. If you were to do a test backup using NTBACKUP (the one which comes with windows), it will also log error messages that it can't create the volume snapshot needed to backup all the files including normally open ones (such as the registry etc). Thus the problem isn't actually with retrospect itself, rather there's something broken in the internals of the Volume Shadow Copy system. To see if this is the case, do a backup of maybe just the windows folder using ntbackup to a file and take a note of the error log produced. If I'm right you'll see errors related to the vss service being unable to operate properly, and thus you'll see warnings about plenty of open files being skipped. Fixing this is a little more difficult, however from memory involves re-installing all the volume shadow copy modules, and re-registering DLLs etc. I followed some instructions I found via Google last time... 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.