Openeing session using command-line parameter is deprecated. Use 'open' command instead.

fadrian
Joined:: 2019-03-08
Posts:: 2
Location:: Portland, OR

Openeing session using command-line parameter is deprecated. Use 'open' command instead.

2019-03-08 19:12

I am using the following command in my .bat file:

winscp.com /logsize=1*1M /log=rxbe2.log /loglevel-0 /nopermissions /script=winscpcmd.txt

In the file winscpcmd.txt, I have the following commands:

option batch abort 
option confirm off 
open sftp://walsftp:MyPassword@192.168.0.43:22/ 
put NOTX_Welig_20190308_105445_1249.txt.pgp /Walgreens/ 
exit

However, I still get the error listed in the subject followed by an immediate abort. Why?

Reply with quote

martin◆ Site Admin
Joined:: 2002-12-10
Posts:: 41,453
Location:: Prague, Czechia

Re: Openeing session using command-line parameter is deprecated. Use 'open' command instead.

2019-03-12

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, use /log=path_to_log_file command-line argument. 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

You can post new topics in this forum

Openeing session using command-line parameter is deprecated. Use 'open' command instead.

Openeing session using command-line parameter is deprecated. Use 'open' command instead.

Re: Openeing session using command-line parameter is deprecated. Use 'open' command instead.

Documentation

Support

Associations

Follow Us