Default Transfer = Binary transferring as text after OS upgrade.

Advertisement

raulblack
Joined:
Posts:
2
Location:
Olympia, WA

Default Transfer = Binary transferring as text after OS upgrade.

I recently built a new server (OS = Windows Server 2016) and installed WinSCP with the same version and settings as the old server (OS = Windows Server 2008). However, the old server properly transfers text files in Binary. I believe the new server is transferring text files as TEXT. I'm using Version 5.9.6 (Build 7601). The files are going between a folder on the local drive to a secure SFTP site on the network.

Notice the extra CR in line 906 of the file transferred on the new server that's not there on the old server. Have you any ideas about why this might be happening?

Thanks!

TransferSettings.jpg

OldAndNewServersTransferredFile.jpg

Reply with quote

Advertisement

raulblack
Joined:
Posts:
2
Location:
Olympia, WA

Re: Default Transfer = Binary transferring as text after OS upgrade.

I should add that when I put -transfer = binary in the script that moves the file on the new server, the problem goes away. If I leave it out, I get the extra CR that causes a blank line.

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
28,658
Location:
Prague, Czechia

Re: Default Transfer = Binary transferring as text after OS upgrade.

Please attach a full session log file showing the problem (using the latest version of 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

Advertisement

You can post new topics in this forum