File download issue using WinSCP client, file integrity check failed, CRC, Unexpecte End of file err

Advertisement

shp143
Joined:
Posts:
1
Location:
India

File download issue using WinSCP client, file integrity check failed, CRC, Unexpecte End of file err

Hi All,
I am using WinSCP to download from one of the Akamai Netstorage SFTP server. Download finishes without any error but the file is not intact. When I check its integrity using 7Zip it shows either CRC error or Unexpected end of file error. I am suspecting that its happening with files with size more than 2MB. I am using binary transfer mode, proxy to reach the SFTP server and it uses key pair for authentication. File extension is gz and size varies from 1KB to 15MB.
I tried to download the same using other sftp client like "Tectia Secure File transfer" and it works perfectly. I am suspecting the transfer mode. When I set the transfer mode to ASCI on Tectia I get the same error for the files. If I set it to binary then file downloads properly.

Please help me to get this issue fixed. WinSCP is the only client where I am getting the file / folder synchronization option. My goal is to download the files and delete from remote server which I am able to achieve with WinSCP .Net assemble / powershell script.

Version of WinSCP : 5.11.2.7781
OS Version : Windows Server 2012 R2
Transfer protocol : SFTP
Using GUI and Automation
File verification error : CRC Failed and Unpected end of file

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
41,367
Location:
Prague, Czechia

Re: File download issue using WinSCP client, file integrity check failed, CRC, Unexpecte End of file err

Please attach a full session log file showing the problem. As well as some verbose Tectia log file.

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

Advertisement

You can post new topics in this forum