Messagebox said remote file can't open, but its exists and is workable.
I have seen, that files with German-Umlauts was downloading, so Umlauts is workable but I must actual hundreds times confirm to skip, but the file exists on remote side.
OK, so can you send me a trace files forI have synchronize a very small part of last sync (two days ago; folder have 129.074 files, 25.606 folders and size of 2,25 GB), with the same dev build. This time its show me the wrong files last time created to replace with correct file names:
1) Working transfer/synchronization of one of those files (by working with that one file only).
Which level I must set for enable session logging? Normal, Debug 1 or Debug 2?2) Failing transfer/synchronization (by working with large [but smallest possible] set of files).
I know, but I need it for comparison.Here is no issue. This issue exists only on very long time synchronization.
I was asking for trace logs from the debug version, I've sent you. Not for session log file.Which level I must set for enable session logging? Normal, Debug 1 or Debug 2?
After closing winscp, its not open explorer. And that's a good thing.Windows Explorer will open with the trace file selected.
In the folder with winscp there is no file named winscp*.log. This folder have write access. Its updated winscp.ini and its startet with administrator privileges.If the Windows Explorer does not open with the trace file, locate it manually in the same folder, where you have extracted the winscp.exe executable to. The trace file has a name like winscpXXXXtrace.log.
No. In September and November, on four different occasions, I've sent you a debug version of WinSCP to your email address. I need you to use that one. I'm sending you one more copy now.Okay... I must google what is a trace file and found this https://winscp.net/eng/docs/debugging
I use winscp 5.14.2 (Dev Build 8964 2018-11-20)
You can post new topics in this forum