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.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Can't transfer - Treating files like they are directories

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
tjj

Can't transfer - Treating files like they are directories

Version 5.17.19
Sometime this morning WinSCP stopped working properly.
It appears to be treating everything on the source side (left pane) as a directory. If I transfer a file(L->R) with an existing file on the R, I get an error code 4 (which I believe is indicating it's trying to copy a directory that already exists).

If I transfer a file(L->R) that does not already exist on the R, I get a code 267 (invalid directory name) and it creates a directory on the R with the same name as my file.
Error retrieving file list for "Z:\m...\foo.pdf\*.*".
System Error. Code: 267.
The directory name is invalid

Transfers from R->L seem to work.