Post a reply

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Re: Scripting cross contamination?

Sorry for the slow response. We call WinSCP scripts from a third party scripting tool using the command line. The ftp scripts are copied from a ftp script folder and things like username, passwords, etc are added to the script file. Then WinSCP is executed via command line redirecting input and output. Sometimes, If multiple WinSCP processes execute at the same time, WinSCP can grab the wrong script from the secondary instance and execute it.

Since this data is healthcare related, we are running into potential HIPAA issues.

Example below:

FATAL ERROR -> PStepp_270In_FTP2AS400 CSCDC1-MBS FTP Failure. FTP Out script results attached................... 2012-01-26 09:09:47.203 --------------------------------------------------------------------------

-WinSCP output....

2012-01-26 09:09:47.203 WinSCP Version 4.1.0 (Build 375) (OS 5.2.3790 Service Pack 2)
. 2012-01-26 09:09:47.203 Login time: Thursday, January 26, 2012 9:09:47 AM
. 2012-01-26 09:09:47.203 --------------------------------------------------------------------------
. 2012-01-26 09:09:47.203 Session name:
. 2012-01-26 09:09:47.203 Host name: (Port: 21)
. 2012-01-26 09:09:47.203 User name: selectcare (Password: Yes, Key file: No)
. 2012-01-26 09:09:47.203 Tunnel: No
. 2012-01-26 09:09:47.203 Transfer Protocol: FTP
. 2012-01-26 09:09:47.203 Ping type: C, Ping interval: 30 sec; Timeout: 240 sec
. 2012-01-26 09:09:47.203 Proxy: none
. 2012-01-26 09:09:47.203 FTP: Passive: Yes
. 2012-01-26 09:09:47.203 Local directory: default, Remote directory: home, Update: No, Cache: Yes
. 2012-01-26 09:09:47.203 Cache directory changes: Yes, Permanent: Yes
. 2012-01-26 09:09:47.203 DST mode: 1
. 2012-01-26 09:09:47.203 --------------------------------------------------------------------------
. 2012-01-26 09:09:47.203 Connecting to ...
. 2012-01-26 09:09:47.203 Connected with Waiting for welcome message...
< 2012-01-26 09:09:47.281 220 lse01web05 Microsoft FTP Service (Version 5.0).
> 2012-01-26 09:09:47.281 USER xxxxxxxxxxx
< 2012-01-26 09:09:47.328 331 Password required for selectcare.
> 2012-01-26 09:09:47.328 PASS ********
< 2012-01-26 09:09:47.375 530 User selectcare cannot log in.
. 2012-01-26 09:09:47.375 Connection failed.
. 2012-01-26 09:09:47.375 Password prompt (no password provided or last login attempt failed)

------>Script that was called at execution time.

open -passive -timeout:240 ftp://<**username**>:<**password**>@
option echo on
option batch on
option confirm off
option transfer ascii
lcd "E:\data\postoffice\CSCDC1-MBS\GOOD"
cd MBS
put -delete CHS270IN.* ./

------>Script that was actually executed at execution time.

open -passive -timeout:240 ftp://<**username**>:<**password**>
option echo on
option batch on
option confirm off
option transfer automatic
lcd "<**LocalFolder**>"
cd "Inbound"
put -delete *.pgp


Re: Scripting cross contamination?

Can you give me more details on what "one instance will pick up the script from the other instance" actually means? Also what version of WinSCP are you using?

Scripting cross contamination?

We are calling WinSCP scripts to send files out to multiple ftp servers. (Winscp /script = <script> /ini= <.ini file> /log= <logfl>).

Sometimes when multiple instances of WinSCP executes at the same time, we have found the one instance will pick up the script from the other instance. This causes ftp/sftp failures or files being routed to the wrong destination.

Is this a know issue? Is there anyway to insure this does not happen?

Note: we do use the same .ini file in every script.