I also just started seeing the issue with a log file being created during sync that is then deleted when the sync is done. The log name I can see while the sync is running is the name of the batch job with a space then .log at the end. For example "MyBackup .log"
Forgot to add that this is on a ...
Search found 3 matches
- 06 Mar 2015, 20:24
- Forum: General Discussion
- Topic: PROBLEM: Illegal Character in Log File Name (Windows)
- Replies: 22
- Views: 5728
- 23 Feb 2015, 22:17
- Forum: Help
- Topic: after update to 6.14 can no longer open log files
- Replies: 2
- Views: 588
Re: after update to 6.14 can no longer open log files
Thank you very much for the info and the link. I was hoping I wasn't the only one having problems with the new format. And that is great that it will be fixed in the next release. :-)
- 23 Feb 2015, 20:41
- Forum: Help
- Topic: after update to 6.14 can no longer open log files
- Replies: 2
- Views: 588
after update to 6.14 can no longer open log files
Running FreeFileSync on CentOS 7. Have had no trouble until the update to v6.14. My logs used to be written in this format:
Wednesday 2015-02-11 210002.log
Since the update they are now written like this:
Wednesday 2015-02-18 21˸00˸02.log
The new format is preventing me from opening the new logs. I ...
Wednesday 2015-02-11 210002.log
Since the update they are now written like this:
Wednesday 2015-02-18 21˸00˸02.log
The new format is preventing me from opening the new logs. I ...
