550 Filename invalid

[bobbleyutd]

Hi all,

I'm getting a couple of "550 Filename invalid" errors. Reading existing posts on the subject, I've upgraded to 0.9.60 server and have made sure the folder "mitel" exists.

Can anyone advise what is wrong with the filename D:\mitel\b_dbsave_ilkrc_13.1.0.38_20171020131209.tar.tmp ?
Are there too many .'s ?
Is the filename too long ?

(000004)20/10/2017 13:05:03 - mitel (xx.xx.xx.xx)> 257 "/" is current directory.
(000004)20/10/2017 13:05:03 - mitel (xx.xx.xx.xx)> PASV
(000004)20/10/2017 13:05:03 - mitel (xx.xx.xx.xx)> 227 Entering Passive Mode (10,95,134,106,237,122)
(000004)20/10/2017 13:05:03 - mitel (xx.xx.xx.xx)> STOR D:\mitel\b_dbsave_ilkrc_13.1.0.38_20171020131209.tar.tmp
(000004)20/10/2017 13:05:03 - mitel (xx.xx.xx.xx)> 550 Filename invalid

(000011)23/10/2017 01:58:24 - mitel (xx.xx.xx.xx)> 257 "/" is current directory.
(000011)23/10/2017 01:58:24 - mitel (xx.xx.xx.xx)> PASV
(000011)23/10/2017 01:58:24 - mitel (xx.xx.xx.xx)> 227 Entering Passive Mode (10,95,134,106,251,48)
(000011)23/10/2017 01:58:24 - mitel (xx.xx.xx.xx)> STOR D:\mitel\/direxp_CSVExport_ilkrc_20171023020534.csv.tmp
(000011)23/10/2017 01:58:24 - mitel (xx.xx.xx.xx)> 550 Filename invalid

I'm not so bothered about the second example - but out of curiosity, is it a / \ thing ?

Thanks in advance !

Kind Regs,
Bobbley.

[botg]

The filename is the problem. Colons are not valid in filenames on Windows.

[botg]

Let's say your home directory is mapped to t:\foobar\ and for the sake of simplicity, there are no configured aliases. Your home directory is represented by the server as /

D:\mitel\b_dbsave_ilkrc_13.1.0.38_20171020131209.tar.tmp is a relative path, as it does not start with a slash. It's relative to the current working directory, which is / according to the log.

So after canonicalization the absolute virtual path is /D:/mitel/b_dbsave_ilkrc_13.1.0.38_20171020131209.tar.tmp

Mapping it to the physical path on the server's host system, that's t:\foobar\D:\mitel\b_dbsave_ilkrc_13.1.0.38_20171020131209.tar.tmp

[boco]

In other, more simple terms:

FileZilla Server exposes a virtual, UNIX-like filesystem to the client. The root directory is /. The client must not send physical paths to the server, those aren't understood.

[bobbleyutd]

Thanks Both !

This has solved my problem

And if anyone else is reading this thread with a similar problem, you can set up the path for the incoming file in
EDIT - USERS - SHARED FOLDERS

Great service - Great product - Thank you !!

Kind Regs,
Bobbley.