I have permission problems with some files that prevent FFS from archiving them.
I assume those file names appear in the error log, however that log is so verbose (~100k entrees) I need to parse it and search it. I presumably most errors are for system and application files that I don't care about.
I assume others have needed to do this. What is the best approach?
sorting and viewing the file error log
- Posts: 2
- Joined: 9 Aug 2026
- Posts: 1239
- Joined: 8 May 2006
I would think there is something you could key in on, a "keyword" to search for, such that you can quickly jump from error to error to see what might be up.
.
Like above, "Error:" (or "Error: ") might do the trick.
So in a text viewer (if you logs are in .txt format), or in an editor, or from command line with grep...
If you search for 'Error:', that would be a start.
Note that in the error, above, there is the line with 'Error:', & an additional line of context given.
So if you, grep Error: "2024-12-13 124444.661 [Error].log", that would only return the 1 line rather then the 2.
Also note that the actual log file name itself should clue you in - [Stopped], [Error], [Warning]...
[Last session] 2025-10-23 120438.431 [Stopped].log
2024-12-13 124444.661 [Error].log
STEVEN 2024-09-11 105414.447 [Warning].log
[12:45:12 PM] Error: Cannot create directory "O:\xfeR\LLL\dir_dot.".
Invalid folder name "dir_dot." ends with a dot character.
Like above, "Error:" (or "Error: ") might do the trick.
So in a text viewer (if you logs are in .txt format), or in an editor, or from command line with grep...
If you search for 'Error:', that would be a start.
Note that in the error, above, there is the line with 'Error:', & an additional line of context given.
So if you, grep Error: "2024-12-13 124444.661 [Error].log", that would only return the 1 line rather then the 2.
Also note that the actual log file name itself should clue you in - [Stopped], [Error], [Warning]...
[Last session] 2025-10-23 120438.431 [Stopped].log
2024-12-13 124444.661 [Error].log
STEVEN 2024-09-11 105414.447 [Warning].log
- Posts: 2
- Joined: 9 Aug 2026
Thanks for your reply. I can examine the html file in a text editor. But it is over 1.7 million lines long because the log does not seem to be limited to error and warnings.
Is there a way to filter the log in FFS and then export only the errors?
If I can pare the file down to fewer lines, I could probably import the html table it into excel and sort it.
In a text editor, I don't know how to sort the html table without loosing the relationship between the elements within each row. (independently sorting the tr and td tags). That is, how to keep the rows together. Sure I could write a python script, but that is more of a rabbit hole that I wanted to travel.
Is there a way to filter the log in FFS and then export only the errors?
If I can pare the file down to fewer lines, I could probably import the html table it into excel and sort it.
In a text editor, I don't know how to sort the html table without loosing the relationship between the elements within each row. (independently sorting the tr and td tags). That is, how to keep the rows together. Sure I could write a python script, but that is more of a rabbit hole that I wanted to travel.
-
- Posts: 2997
- Joined: 22 Aug 2012
If the HTML tags bother you, why not set the log file to be created as plain text, instead of as HTML.
You can do so in the FFS main menu Tools / Options.
You can do so in the FFS main menu Tools / Options.