Yes, that is exactly what is happening. Will this be fixed in the next release?
It's not a bug. That's how it is supposed to work.
- martin
It's not a bug. That's how it is supposed to work.
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.
Topic review
It's not a bug. That's how it is supposed to work.
- RJB
Yes, that is exactly what is happening. Will this be fixed in the next release?
- martin
Re: Renaming with Error 4
I am having the exact same problem, is there a fix for this?
Renaming to the name of already existing file is not allowed, if that is your problem.
- RJB
Renaming with Error 4
I am having the exact same problem, is there a fix for this?
- martin
Re: Why Renaming fails as of version 3????
Have you read the FAQ? Does it help?
- I_Dont_recall
Why Renaming fails as of version 3????
As for renaming remote files to a filename that already exists in the remote directory when I use SFTP protocol.
I checked my winscp versions. The last one that worked was
version 2.3.0 (just confirmed it still works).
Winscp 3.6.8, 3.7.1, 3.7.4 and 3.7.6 do not work.
I cannot rename remote files to an existing name anymore.
Here's more info:
When I fail it uses
SSH-2 OpenSSH3.1p1
exncryption algorhyim aes
compression no
File Transfer protocol SFTP(v3)
The error message I get is:
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Request code: 18
By default I would think winscp 3.x would allow me to do this.
I just compared the protocols SCP and SFTP and its apparent the SFTP has many of the features I rely on now like huge over 2 GB file transfers and transfer resumes.... so SFTP is a good choice.
Now if I manually DELETE the old file on the remote server in SFTP mode, and then manually rename the remote file to the old file in SFTP mode this is no problem..... So this can be programmed to work via WinSCP3 using SFTP, since I can do it via the GUI in two steps instead of one.
So in a way this is a bug.... but I truly understand if you have no time to fix it, as fixing bugs sometimes cause new bugs and sometimes make the code more complex.
I checked my winscp versions. The last one that worked was
version 2.3.0 (just confirmed it still works).
Winscp 3.6.8, 3.7.1, 3.7.4 and 3.7.6 do not work.
I cannot rename remote files to an existing name anymore.
Here's more info:
When I fail it uses
SSH-2 OpenSSH3.1p1
exncryption algorhyim aes
compression no
File Transfer protocol SFTP(v3)
The error message I get is:
General failure (server should provide error description).
Error code: 4
Error message from server: Failure
Request code: 18
By default I would think winscp 3.x would allow me to do this.
I just compared the protocols SCP and SFTP and its apparent the SFTP has many of the features I rely on now like huge over 2 GB file transfers and transfer resumes.... so SFTP is a good choice.
Now if I manually DELETE the old file on the remote server in SFTP mode, and then manually rename the remote file to the old file in SFTP mode this is no problem..... So this can be programmed to work via WinSCP3 using SFTP, since I can do it via the GUI in two steps instead of one.
So in a way this is a bug.... but I truly understand if you have no time to fix it, as fixing bugs sometimes cause new bugs and sometimes make the code more complex.