Error log too big, full of info

[vrak58]

My Free File Sync error log is too big, 99% full of Info messages, like:
Info: Creating file "C:\Users\steinh\AppData\Local\Microsoft\Windows\WindowsUpdate.log"
True errors are hiding in this huge pile of info messages. How can I suppress such Info messages from error log?

[vrak58]

And, thousands of errors like:
[2:32:14 PM] Error: Cannot move file "C:\Users\steinh\AppData\Local\Microsoft\Windows\WER\ERC\TemplateCache\Template_86_9.xslt.ffs_tmp" to "C:\Users\steinh\AppData\Local\Microsoft\Windows\WER\ERC\TemplateCache\Template_86_9.xslt".

I have in my ffs_batch file:
<SyncConfig>
<Variant>Update</Variant>
<CustomDirections>
<LeftOnly>right</LeftOnly>
<RightOnly>left</RightOnly>
<LeftNewer>right</LeftNewer>
<RightNewer>left</RightNewer>
<Different>none</Different>
<Conflict>none</Conflict>
</CustomDirections>
<DetectMovedFiles>false</DetectMovedFiles>
<DeletionPolicy>Versioning</DeletionPolicy>
<VersioningFolder Style="TimeStamp">C:\Users\steinh\ffstemp</VersioningFolder>
</SyncConfig>

Why should it not simply "update" and create a new version in ffstemp folder I have designated?

[vrak58]

Any one knows how to handle "non-errors" messages and unexplained-errors in ffs_batch?

[vrak58]

Well, if no one knows how to avoid flooding of error logs with info messages, I guess I have to advise my users to try some other backup solution. So sorry to abandon ffs which looked promising to me:(

[vrak58]

My code section was not correctly formatted in above posting, reposted below:

I have a huge error log file, 99.9% of the messages are not errors but info like\bla\bla\bla.txt created. The real errors are lost like a needle in the haystack. I tried adding to my ffbatch file the following without success:

<freeFileSync>
<MainConfig>
...
...
</MainConfig>
<batchConfig>
<HandleError>Ignore</HandleError>
<LogfileFolder Limit="100">\ffstemp</LogfileFolder>
</batchConfig>
</freeFileSync>

[Zenju]

Uhm, why not search for "error" in the log file? Generally, errors should be exceptions rather than the rule, therefore listing error messages conveniently was not a prime design goal.

> I tried adding to my ffbatch file the following without success:

What did you add?

[vrak58]

Uhm, why not search for "error" in the log file? Generally, errors should be exceptions rather than the rule, therefore listing error messages conveniently was not a prime design goal.

> I tried adding to my ffbatch file the following without success:

What did you add?

Sure, everything is possible. But I am trying to suggest an improvement to the product that user should be given a choice to avoid dumping "info" type messages into the "error" log, specially when the real errors become a needle in the haystack.

I "added" the option of "Ignore" to the HandleError tag because the resulting file was way to big to be of much practical use, but it did not help.