- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- Melakh
E-mail sent
- martin
Re: Long Filename logging Issue (and workaround)
Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.
You will find my address (if you log in) in my forum profile.
- Melakh
Long Filename logging Issue (and workaround)
I recently encountered a error with a new backup job I've created using batch mode. Whenever the job encounters a filename where the combined length of the directory and filename is very long it will be unable to copy the file with an error message stating that the target file cannot be created.
The target device is NTFS (this is not a FAT issue). Details of the reason for the error can be found at: https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file
It's easy to work-around by prefixing the local directory with '\\?\' e.g. '\\?\E:\MyFolder'
The bug I would like to raise though is that this file was skipped by WinSCP but that didn't appear in the output logs anywhere as a failure, it was only by manually checking that I noticed files of these types were not being backed up.
The target device is NTFS (this is not a FAT issue). Details of the reason for the error can be found at: https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file
It's easy to work-around by prefixing the local directory with '\\?\' e.g. '\\?\E:\MyFolder'
The bug I would like to raise though is that this file was skipped by WinSCP but that didn't appear in the output logs anywhere as a failure, it was only by manually checking that I noticed files of these types were not being backed up.