get command is now allowed

WinSCP version - 5.15.3
windows 10 ver 10.0.18326.295
Transfer protocol - FTPS
scripting/automation
error: (Attachment)
MGETcommand is working good
when im using GET command - im getting error > get command is now allowed

Attachment

oron.david@loreal.com
davidoron7@gmail.com

thanks

Your server announces a support for MDTM command:

< 2019-09-18 14:38:08.027 211-Extended features supported:
< 2019-09-18 14:38:08.027 LANG EN*
< 2019-09-18 14:38:08.027 UTF8
< 2019-09-18 14:38:08.027 AUTH TLS;TLS-C;SSL;TLS-P;
< 2019-09-18 14:38:08.027 PBSZ
< 2019-09-18 14:38:08.027 PROT C;P;
< 2019-09-18 14:38:08.027 CCC
< 2019-09-18 14:38:08.027 HOST
< 2019-09-18 14:38:08.027 SIZE
< 2019-09-18 14:38:08.027 MDTM
< 2019-09-18 14:38:08.027 REST STREAM
< 2019-09-18 14:38:08.027 211 END

But when WinSCP tries to use it, it fails:

> 2019-09-18 14:38:08.199 MDTM /2.bmp
< 2019-09-18 14:38:08.215 500 Command not allowed.

Please talk to your server administrator.

martin wrote:

Your server announces a support for MDTM command:

< 2019-09-18 14:38:08.027 211-Extended features supported:
< 2019-09-18 14:38:08.027 LANG EN*
< 2019-09-18 14:38:08.027 UTF8
< 2019-09-18 14:38:08.027 AUTH TLS;TLS-C;SSL;TLS-P;
< 2019-09-18 14:38:08.027 PBSZ
< 2019-09-18 14:38:08.027 PROT C;P;
< 2019-09-18 14:38:08.027 CCC
< 2019-09-18 14:38:08.027 HOST
< 2019-09-18 14:38:08.027 SIZE
< 2019-09-18 14:38:08.027 MDTM
< 2019-09-18 14:38:08.027 REST STREAM
< 2019-09-18 14:38:08.027 211 END

But when WinSCP tries to use it, it fails:

> 2019-09-18 14:38:08.199 MDTM /2.bmp
< 2019-09-18 14:38:08.215 500 Command not allowed.

Please talk to your server administrator.

I'm the server administrator.
i dont see any problems , when i use WinCSP GUI client to download a file its working without problems , so what is the different between GUI and CLI ?

thanks
oron david

i dont see any problems , when i use WinCSP GUI client to download a file its working without problems , so what is the different between GUI and CLI ?

That's irrelevant. Your server misbehaves, that's the problem.
Anyway to answer your question: If you do get 2.bmp in the script, it needs to find out the file attributes (Is it a file or folder? What is its timestamp?) WinSCP can use several commands for that and it picks the command that the server claims to support. That's where you server fails. In GUI, WinSCP knows the file attributes from a directory listing (retrieved using different command). That part works on your server. If you do something like get * or get *.bmp or even get 2.bmp*, it would work as the scripting will use the same commands as GUI.