Forum » Support and Bug Reports »

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

mapiet wrote:

Maybe WinSCP should use quotes around pathname strings? Probably then would be no problems with spaces in path, in any operating systems.

There's nothing about quotes in the FTP specification. So such a change will likely break more than it would fix.
mapiet

Maybe WinSCP should use quotes around pathname strings? Probably then would be no problems with spaces in path, in any operating systems.
martin

I do not think that WinSCP is doing anything wrong. So, no, I do not plan to change anything. Please contact your FTP server software vendor.
mapiet

Will you do something with this problem in future (in WinSCP application)? Whether the problem there is only in my computer or in remote computer (i.e. in the FTP server) and it must be resolved by me?
martin

mapiet wrote:

I have to add: The other FTP client (Total Commander) work fine in this same situation, even if in the path are some spaces.

TC possibly does not use MLST command. Your server does not seem to have problems with other commands.
mapiet

I have to add: The other FTP client (Total Commander) work fine in this same situation, even if in the path are some spaces.
mapiet

That's true. I checked it a moment ago. This problem is bound with spaces in path. What is guilty: the FTP server or WinSCP application?
martin

The error message is actually misleading.

The actual problem is here:
> 2013-12-07 09:14:18.551 MLST /m.ptr/Program SN/tmp_tmp/tmp_dir
< 2013-12-07 09:14:18.551 501 Invalid number of arguments


Your server fails MLST command for some reason. Possibly it gets confused with the space in the path.
mapiet

This is the logfile (in attachment).
martin

Re: Empty directory copying error

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

To generate 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 may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.
mapiet

I have to clarify: I am using a FTP transfer protocol.
mapiet

Empty directory copying error

Using WinSCP 5.1.8 (build 3799) with “Commander” interface on Windows 2000 SP4.

The situation looks that:
I have one directory on the local machine and the one directory in the remote destination (this same name of directory). Both directories are empty. If I try copy empty directory from local machine to remote destination (override), an error message appears: "Copying files to remote side failed. Error creating folder 'folder name with path'. folder name: File exists". I am using the Default transfer settings.

Documentation

Support

Associations

Follow Us