WinSCP 6.3 | Error 5 on any MOVE command with SFTP :: Support Forum

fwx3 Guest

WinSCP 6.3 | Error 5 on any MOVE command with SFTP

2024-02-17 00:12

We're noticing 6.3 has issues moving files. It can upload/download OK but any move throws "Error code: 5". This is even with the .filepart being removed at completion of a transfer. This is also happening with multiple different SFTP server software.

Bad message (badly formatted packet or protocol incompatibility).
Error code: 5
Error message from server (en): Badly formatted SFTP packet

Session information:

File transfer protocol = SFTP-6
Cryptographic protocol = SSH-2
SSH implementation = [redacted]
Encryption algorithm = [redacted]
Compression = No
------------------------------------------------------------
Server host key fingerprints
SHA-256 = [redacted]
MD5 = [redacted]
------------------------------------------------------------
Can change permissions = Yes
Can change ACL = No
Can change owner/group = No
Can execute arbitrary command = No
Can create symbolic/hard link = Yes/Yes
Can lookup user groups = No
Can duplicate remote files = No
Can check available space = No
Can calculate file checksum = No
Native text (ASCII) mode transfers = Yes
------------------------------------------------------------
Additional information
The server supports these SFTP extensions:
newline="\r\n"
supported2=0x0000003D000000000000000F000000000000000000000001000000010000000000000000
versions="3,4,5,6"

Reply with quote

martin◆ Site Admin
Joined:: 2002-12-10
Posts:: 40,605
Location:: Prague, Czechia

Re: WinSCP 6.3 | Error 5 on any MOVE command with SFTP

2024-02-17

Do you mean that it was working in previous versions of WinSCP and now it does not with WinSCP 6.3?

Please attach a full session log file showing the problem (using the latest version of WinSCP). If it was working in the previous version, please post its log file too. You can download the previous version from:
https://sourceforge.net/projects/winscp/files/WinSCP/

To generate the session 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 can mark the attachment as private.

Reply with quote