Before posting, and to avoid disappointment, please read the following:
- This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
- If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.
- Posts: 27
- Joined: Mon Nov 13, 2017 1:00 pm
I'm using the Surface of my wife with my own account. By that I do not have full rights so SyncBack is not able to copy some (20-30) locked files, buts that is really ok for me:
Failed to copy from Quelle : File is locked: Cannot open file "\\?\C:\Users\xxxxx\NTUSER.DAT". Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird
R:550 /xxxxx/$SBV$: No such file or directory.
R:250 CWD command successful.
R:257 "/xxxxx" is current directory.
R:550 SBSE____.0XD: No such file or directory.
But as I'm receiving every 30 minutes an error log I like to have an option to grade locked file errors as warnings.
A second wish: Create an error if more than 1% of all files are warnings.
- 2BrightSparks Staff
- Posts: 992
- Joined: Mon Apr 13, 2015 6:22 am
To prevent the occurrence of any risky or unexpected situations, we record all file copy errors (including locked file copy errors) as Errors. However, I will pass your request to the relevant department for their review.
- Posts: 39
- Joined: Mon Sep 12, 2016 5:27 pm
Yes, it would be nice with a more granular classification of errors/warnings.
One idea, that would work for me, is checkbox options to only display "access denied" or "locked" errors for files that haven't previously been detected in a scan with those errors, but on all subsequent scans with the same problem either silently ignore them (flag them as "skipped")
or reduce them to warnings.
Another idea is a filter list, similar to the backup selection filter, for those errors.