Changing the log path in builds 294 and 296 isn't remembered: the next time I look there, the old log path is still there. I have downgraded to build 290 in order to "fix" this.
Could you please resolve this bug?
Log path not remembered in builds 294 and 296
Answer very much appreciated!
I do hope I get an answer to this some day, unlike for instance the post with SID 1fc1e33b789cfdc6ea8b714910dda573 and URL http://coreftp.com/forums/viewtopic.php ... 4910dda573 which still has 0 replies after more than 6 months and talks about the same bug...
Thanks
Thanks for the new build, but (at least in our case) it doesn't help. It looks like the invalid filenames problem has indeed been tackled (but that wasn't really a big issue for us), but not that the path changes back to "C:\Program Files\CoreFTPServer" after changing it something else. So unfortunately, this is still a problem for us and I've already downgraded back to build 290 in expectation of better times...
Yes, it points to a directory on the D: disk. We wouldn't like the system disk to get full because of the log files, so that's why it's on a different partition/disk. Build 290 accepts, uses and remembers this location, but the builds after that just revert back to C:\Program Files\CoreFTPServer after changing this setting and checking the setting.
The service runs under the local system account and I've double-checked that the system account has full control permissions, so it's not a permissions issue.
The service runs under the local system account and I've double-checked that the system account has full control permissions, so it's not a permissions issue.