Re: Download to UNC path
Maybe because of "open transfer binary". You probably wanted to do "option transfer binary.
- martin
Post a reply
Topic review
- dfoard
NVM - it actually is working using the UNC path name, though not sure why I am getting the too many parameters message.
- dfoard
Download to UNC path
I am using a script within SSIS to automate the download. I am trying to use a UNC path with the get command:
GET myfilename.zip \\nasgw\myfolder\
However, when testing this in SSIS I get the error too many parameters for command. The documentation states that UNC paths are supported, but what is the exact syntax to use when scripting?
Here is the sample script:
open sftp://username:password@sitename.com
open transfer binary
get myfilename.zip \\nasgw\myfolder\
close()
exit
Dave
GET myfilename.zip \\nasgw\myfolder\
However, when testing this in SSIS I get the error too many parameters for command. The documentation states that UNC paths are supported, but what is the exact syntax to use when scripting?
Here is the sample script:
open sftp://username:password@sitename.com
open transfer binary
get myfilename.zip \\nasgw\myfolder\
close()
exit
Dave