Warning instead of failure for not copied deleted files does not work

For technical support visit http://support.2brightsparks.com/
Post Reply
mgutt
Knowledgeable
Knowledgeable
Posts: 27
Joined: Mon Nov 13, 2017 1:00 pm

Warning instead of failure for not copied deleted files does not work

Post by mgutt » Wed Jan 31, 2018 3:02 pm

In the settings, there is an option:
Log -> If a file cannot be copied because it was deleted before it could be copied then make it a warning and not a failure
Although I activated this option I still receive error logs like this:
2018-01-31 15_57_50.png
2018-01-31 15_57_50.png (229.6 KiB) Viewed 1122 times
Is this a bug or do I understand the setting wrong?

cliffhanger
Expert
Expert
Posts: 835
Joined: Tue May 31, 2011 5:59 pm

Re: Warning instead of failure for not copied deleted files does not work

Post by cliffhanger » Wed Jan 31, 2018 5:21 pm

Works for me (just tested with Pro x64 8.5.25.0). I think it's because the initial error returned by Windows in your case (when the APIs that SB tries to use to process the file in question are called) is not the expected trigger error. Your error states the file cannot be read, not that it cannot be found; I think the latter is what SB is programmed to detect/react to.

Easy test (takes less time to set up than to type...)
  • make a simple profile set to copy a file from a temp dummy Source folder on your C drive (or elsewhere if preferred) to >
  • make another temp/dummy Destination likewise
  • make sure the required logging option is on
  • add a test file to the dummy Source (I called mine ghost_test.txt)
  • Run the test profile manually (not Unattended; we need the Differences window to open/pause)
  • when the Differences window opens, let it pause while you use Explorer to manually delete the file ghost_test.txt
  • now click Continue in SB UI, let it finish & and check your log - you should see it recorded as a Warning
Here is some debug info from a similar test (copying from H to Z in my case - I adapted an existing profile)...note how the label {E] changes to [W} partway thru as the code decides to treat as a [W]arning, not an [E]rror

Code: Select all

16:23:48=LocationsNormal.TNormalLocation.CopyFromFile.524:\ghost_test.txt
16:23:48=[E]:FSWrapper.TFSWrapper.WideCopyFile.452:H:\ghost_test.txt: The system cannot find the file specified (2) [Z:\DATA\H_VERSIONED\SBSE____.X0X]
16:23:48=[E]:FSWrapper.TFSWrapper.NonShellCopyFile.1061:H:\ghost_test.txt: The system cannot find the file specified (2) [Z:\DATA\H_VERSIONED\SBSE____.X0X]
16:23:48=[E]:FSWrapper.TFSWrapper.NonShellCopyFile.1105:H:\ghost_test.txt: The system cannot find the file specified (2) [Z:\DATA\H_VERSIONED\SBSE____.X0X, Cannot copy file (2): The system cannot find the file specified The file may have been deleted between the time it was scanned and the attempt to copy it was made]
16:23:48=[E]:WindowsFS.TWindowsFS.FileExists.2298:Z:\DATA\H_VERSIONED\SBSE____.X0X: The system cannot find the file specified (2)
16:23:48=[E]:FSWrapper.TFSWrapper.NonShellDeleteFile.2253:Z:\DATA\H_VERSIONED\SBSE____.X0X [Does not exist]
16:23:48=[W]:ProfileEngine.pCopyFile.8487:\ghost_test.txt [File to copy missing]
16:23:48=[W]:ProfileEngine.TRunProfile.WarningMessage.14376:\ghost_test.txt [\ghost_test.txt:The file may have been deleted between the time it was scanned and the attempt to copy it was made]
16:23:48=[W]:Log.TLog.AddFileStatus.889:\ghost_test.txt [The file may have been deleted between the time it was scanned and the attempt to copy it was made]
Why you're getting a different error when it first tries to copy that journal file I can't say (maybe an accident of timing: trying to read it while Thunderbird is deleting it, maybe?), but of course we don't know exactly what TBird is doing with that file, nor when. In any case, I think the fact it doesn't return the error SB is expecting sends SB down a different logical path. Issue may also be linked to TBird security (I seem to remember funny things sometimes happening access-control-wise when I used to use/back-up TBird some years ago).

mgutt
Knowledgeable
Knowledgeable
Posts: 27
Joined: Mon Nov 13, 2017 1:00 pm

Re: Warning instead of failure for not copied deleted files does not work

Post by mgutt » Wed Jan 31, 2018 6:13 pm

This is nothing specially related to TB. I needed to add several filters for different temp files like the cache files of Google Chrome, too. All throw errors if the file is not found anymore.

I will post my test results later.

User avatar
mickyj
2BrightSparks Staff
2BrightSparks Staff
Posts: 927
Joined: Mon Jan 05, 2004 6:51 pm

Re: Warning instead of failure for not copied deleted files does not work

Post by mickyj » Thu Feb 01, 2018 4:51 am

Hi, could you submit a support ticket with a debug log? When using FTP the files are opened a different way (by the FTP component itself) so it's possible that it's not being noticed that the file doesn't exist. We'll also do some tests to see if we can reproduce it. Thanks.

User avatar
mickyj
2BrightSparks Staff
2BrightSparks Staff
Posts: 927
Joined: Mon Jan 05, 2004 6:51 pm

Re: Warning instead of failure for not copied deleted files does not work

Post by mickyj » Fri Feb 02, 2018 4:56 am


mgutt
Knowledgeable
Knowledgeable
Posts: 27
Joined: Mon Nov 13, 2017 1:00 pm

Re: Warning instead of failure for not copied deleted files does not work

Post by mgutt » Fri Feb 02, 2018 12:03 pm

Wow that was fast. I installed the beta, raised the log files to 50 (to check for warnings) and will give feedback in a few days.

mgutt
Knowledgeable
Knowledgeable
Posts: 27
Joined: Mon Nov 13, 2017 1:00 pm

Re: Warning instead of failure for not copied deleted files does not work

Post by mgutt » Thu Jun 14, 2018 10:58 am

Final feedback: It works. Thanks!

Post Reply