can't move remote files/folders on other drive on sameserver

hi all,

when i try to move a folder or file on my nas with winscp using either duplicate or move or drag&drop it always fails with this error:

General failure (server should provide error description).
Error code: 4
Error message from server: Failure

but when i type in a console window: mv /share/HDA_DATA/myfolder /share/HDB_DATA

it works fine.

is this a bug or is there a setting/option that i need to set in winscp for it to work with the context menu ? i'm new here and to winscp so talk slowly (lol).

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

Hi Martin, so sorry this took such a long time to get back to you, i never got a notificaiton email from your server.

i made a log file with winscp 5.5.6 and attached it below.

there's something interesting when i look in it, i did a move command on a single file for testing and i think i found the reason why it always fails:

. 2015-01-27 14:29:26.842 Moving file "test.txt" to "/share/HDB_DATA/hdd2/test.txt".
> 2015-01-27 14:29:26.842 Type: SSH_FXP_RENAME, Size: 71, Number: 176914

isn't the rename command only for a local file or move something on the same drive as the source ? if that's the case then a simple comparison of the source and dest drive would solve this problem.

Or better yet, 1st try rename since its faster on single drive moves, and if it fails don't show a popup but try a move instead, then if that fails show a popup.



ps: i hope you can fix the email notifications, i've been registered here for a sufficiently long time and no notifs at all. you may want to check with your isp if they have changed ports or enabled some extra security that prevents out going emails.

pps: i see there's a newer winscp version 5.6.5rc i'll do the update toute suite and see if the bug still appears...

nope, no change in v5.6.5

i still can't move from one drive to the other.

With OpenSSH SFTP server, you cannot move a file across file system boundaries:
https://winscp.net/eng/docs/sftp_codes#code_4

There's no difference between "move" and "rename" in SFTP.

Are you really getting the "Failure" error also for a Duplicate command? If you are, please attach a session log file for that.

the duplicate command works tho it times-out if it's set too low but i've set it to 60 seconds and that works for small to medium files. The duplicate window shows up and displays the progress bar and its a beautiful thing.

The move just doesn't want to move. But it still needs to do the job, some there must be some ways to work around that.



ps: i received an email notifications, thanks for fixing it.

Anonymous wrote:

the duplicate command works tho it times-out if it's set too low but i've set it to 60 seconds and that works for small to medium files. The duplicate window shows up and displays the progress bar and its a beautiful thing.

The move just doesn't want to move. But it still needs to do the job, some there must be some ways to work around that.



ps: i received an email notifications, thanks for fixing it.

that was me answering as guest.

The move just doesn't want to move. But it still needs to do the job, some there must be some ways to work around that.

You can use SCP protocol. It uses mv command for moving, which you claim to work.
If you need to use SFTP protocol, you can at least add a custom command with mv.
See https://winscp.net/eng/docs/custom_command

you're right the scp does move, i'll use that from now on.

just a thought, since this error occurs essentially because of a limitation in the SFTP protocol and not an actual bug in Winscp, i think that would be so helpful to educate user and tell him/her to switch to SCP instead of just displaying an error #4 popup.

anyway you're so smart for having figured out it was a protocol limitation. i'm glad it's not a bug.

Now my file managing will go much smoother, Thanks Martin!

smitty123 wrote:

just a thought, since this error occurs essentially because of a limitation in the SFTP protocol and not an actual bug in Winscp, i think that would be so helpful to educate user and tell him/her to switch to SCP instead of just displaying an error #4 popup.

Thanks for the suggestion. Will consider it.

martin wrote:

smitty123 wrote:

just a thought, since this error occurs essentially because of a limitation in the SFTP protocol and not an actual bug in Winscp, i think that would be so helpful to educate user and tell him/her to switch to SCP instead of just displaying an error #4 popup.

Thanks for the suggestion. Will consider it.

This issue has been added to the tracker:
https://winscp.net/tracker/1285

thank you :)