Winscp Script Option Transfer Binary

danbrown1888
Joined:: 2013-05-31
Posts:: 4
Location:: NJ

2013-09-27 xviii:52

Hullo scripting experts! I'm a network admin attempting to utilise WinSCP scripting for a file transfer. The trouble I am encountering is the format. The file needs to be in standard ASCII with CRLF at the cease of each line. Right now when viewed those are missing. I take made several attempts at changing the script parameters simply have seen no change which leads me to believe the problem is my syntax. The script is below, I would greatly appreciate any feedback on how to alter it to force the file to transfer in ASCII format so I get the CRLF formatting to show up. Thanks in advance!

endeavour
{
# Load WinSCP .Net associates
# Use "winscp.dll" for the releases before the latest beta version.
[Reflection.Assembly]::LoadFrom("C:\Program Files (x86)\WinSCP\WinSCP.dll") | Out-Null

# Setup session options
$sessionOptions = New-Object WinSCP.SessionOptions
$sessionOptions.Protocol = [WinSCP.Protocol]::Sftp
$sessionOptions.HostName = "XX.Thirty.internet"
$sessionOptions.UserName = "USERNAME"
$sessionOptions.Password = "Countersign"
$sessionOptions.SshHostKeyFingerprint = "ssh-rsa 1024 twenty:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:20:twenty:xx:xx"

$session = New-Object WinSCP.Session

try
{
# Connect
$session.Open($sessionOptions)

$localPath = "C:\XXXX File\"
$remotePath = "/Inbox/"
$file = "file.txt"

# Transfer Options set up to ASCII
$transferOptions = New-Object WinSCP.TransferOptions
$transferOptions.TransferMode = [WinSCP.TransferMode]::ASCII

# Download the file and throw on any mistake
$session.GetFiles(
($remotePath + $file),
($localPath + $file)).Check()
}
finally
{
# Disconnect, clean up
$session.Dispose()
}

exit 0
}
catch [Exception]
{
Write-Host $_.Exception.Message
exit 1
}

Reply with quote

martin◆ Site Admin
Joined:: 2002-12-10
Posts:: 37,378
Location:: Prague, Czechia

2013-09-30

If you demand the file to be CRLF at the server-end, just upload information technology in binary format, what is is default. (I suppose you take it in CRLF in source as you are on Windows).

Otherwise your lawmaking to enable Ascii way is correct. Trouble is that files are converted to LF line-endings with SFTP (version three and older) by default.

Reply with quote

danbrown1888

2013-ten-01 14:00

I've tried irresolute the format using ASCII, Binary, and default but the CRLF I demand at the finish of each line withal never shows upward. I thought peradventure I had a syntax consequence in my script which was preventing the transfer blazon from being correctly set.

Reply with quote

martin◆ Site Admin
Joined:: 2002-12-10
Posts:: 37,378
Location:: Prague, Czech republic

2013-10-04

First annotation that file transfer client is non generic line ending conversion tool. Then generally, information technology only converts the line ending between native formats of source and destination auto. And you do not seem to have the source file in native format of your local machine (Windows).

Anyway, assuming your server supports SFTP version 3, non higher, what is common, yous tin force WinSCP to catechumen the file to CRLF using raw session setting EOLType:
https://winscp.net/eng/docs/rawsettings

Reply with quote