Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
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)

Options

Topic review

martin

mert wrote:

I am having the same issue, the process exits with code 1 or 3.

This is what I currently have
WinSCP Version 5.13.1 (Build 8265) (OS 6.1.7601 Service Pack 1 - Windows Server 2008 R2 Datacenter)

I am getting directly connection failed with no extra information about why it is failing.

Things I have tried
-Restarted the application
-run from command line with the same parameters(THIS WORKS)

I assume that when you run the script "from command line", you are using a different local account. Make sure that the account "xxxx\xxxx$" (from the log) has network connectivity allowed.
mert

Hi

I am having the same issue, the process exits with code 1 or 3.

This is what I currently have
WinSCP Version 5.13.1 (Build 8265) (OS 6.1.7601 Service Pack 1 - Windows Server 2008 R2 Datacenter)

I am getting directly connection failed with no extra information about why it is failing.

Things I have tried
-Restarted the application
-run from command line with the same parameters(THIS WORKS)

How can I see more details/logs? What am I doing wrong?

Thanks 

. 2018-09-07 12:29:10.190 WinSCP Version 5.13.1 (Build 8265) (OS 6.1.7601 Service Pack 1 - Windows Server 2008 R2 Datacenter)

. 2018-09-07 12:29:10.190 Configuration: HKCU\Software\Martin Prikryl\WinSCP 2\

. 2018-09-07 12:29:10.190 Log level: Normal

. 2018-09-07 12:29:10.190 Local account: xxxx\xxxx$

. 2018-09-07 12:29:10.190 Working directory: C:\Windows\SysWOW64\inetsrv

. 2018-09-07 12:29:10.190 Process ID: 25092

. 2018-09-07 12:29:10.192 Command-line: "C:\Program Files (x86)\WinSCP\WinSCP.exe"  /script="C:\inetpub\xxxxx\xxxx\xxxxx\xxxxxx_ftp.txt" /log="C:\xxxx\xxxxxx\xxxx\xxxxx\xxxxxxxx_ftp.log"

. 2018-09-07 12:29:10.192 Time zone: Current: GMT-4, Standard: GMT-5 (Eastern Standard Time), DST: GMT-4 (Eastern Daylight Time), DST Start: 3/11/2018, DST End: 11/4/2018

. 2018-09-07 12:29:10.192 Login time: Friday, September 07, 2018 12:29:10 PM

. 2018-09-07 12:29:10.192 --------------------------------------------------------------------------

. 2018-09-07 12:29:10.192 Script: Retrospectively logging previous script records:

> 2018-09-07 12:29:10.192 Script: option batch abort

< 2018-09-07 12:29:10.192 Script: batch           abort     

> 2018-09-07 12:29:10.192 Script: option confirm off

< 2018-09-07 12:29:10.192 Script: confirm         off       

> 2018-09-07 12:29:10.192 Script: option transfer ascii

< 2018-09-07 12:29:10.192 Script: transfer        ascii     

> 2018-09-07 12:29:10.192 Script: open ftp://xxxxx:***@vftp.xxxxx.com

. 2018-09-07 12:29:10.192 --------------------------------------------------------------------------

. 2018-09-07 12:29:10.192 Session name: [email protected] (Ad-Hoc site)

. 2018-09-07 12:29:10.192 Host name: vftp.xxxx.com (Port: 21)

. 2018-09-07 12:29:10.193 User name: xxxxx (Password: Yes, Key file: No, Passphrase: No)

. 2018-09-07 12:29:10.193 Transfer Protocol: FTP

. 2018-09-07 12:29:10.193 Ping type: Dummy, Ping interval: 30 sec; Timeout: 15 sec

. 2018-09-07 12:29:10.193 Disable Nagle: No

. 2018-09-07 12:29:10.193 Proxy: None

. 2018-09-07 12:29:10.193 Send buffer: 262144

. 2018-09-07 12:29:10.193 UTF: Auto

. 2018-09-07 12:29:10.193 FTPS: None [Client certificate: No]

. 2018-09-07 12:29:10.193 FTP: Passive: Yes [Force IP: Auto]; MLSD: Auto [List all: Auto]; HOST: Auto

. 2018-09-07 12:29:10.193 Local directory: default, Remote directory: home, Update: Yes, Cache: Yes

. 2018-09-07 12:29:10.193 Cache directory changes: Yes, Permanent: Yes

. 2018-09-07 12:29:10.193 Recycle bin: Delete to: No, Overwritten to: No, Bin path: 

. 2018-09-07 12:29:10.193 Timezone offset: 0h 0m

. 2018-09-07 12:29:10.193 --------------------------------------------------------------------------

. 2018-09-07 12:29:10.195 Connecting to vftp.xxxxxxx.com ...

. 2018-09-07 12:29:10.233 Connection failed.
Guest

Re: Seeing this bug again in 5.9.4.0

Anonymous wrote:

martin wrote:

Anonymous wrote:

Is there some number of times running winscp where this bug kicks back in even in the newer versions?

How are you "seeing this bug"?

Does the error happen randomly only, for some runs?

Or are you really getting the same symptoms: When the error happens, it consistently happens for all runs. And only system restart helps?


Haven't seen this issue for about 6 months since upgrading from a very old release to 5.9.4 and now the same issue has resurfaced. It isn't random but happens on all runs and only a restart will fix it. The only thing that has changed is that there would now be even more runs than before so I was wondering if there was some magic number where it would just stop working and we need a new session.


Hi, you can disregard this. It looks like someone installed a new application that has the old version still in it. Sorry for the trouble.
Guest

Re: Seeing this bug again in 5.9.4.0

martin wrote:

Anonymous wrote:

Is there some number of times running winscp where this bug kicks back in even in the newer versions?

How are you "seeing this bug"?

Does the error happen randomly only, for some runs?

Or are you really getting the same symptoms: When the error happens, it consistently happens for all runs. And only system restart helps?


Haven't seen this issue for about 6 months since upgrading from a very old release to 5.9.4 and now the same issue has resurfaced. It isn't random but happens on all runs and only a restart will fix it. The only thing that has changed is that there would now be even more runs than before so I was wondering if there was some magic number where it would just stop working and we need a new session.
martin

Re: Seeing this bug again in 5.9.4.0

Anonymous wrote:

Is there some number of times running winscp where this bug kicks back in even in the newer versions?

How are you "seeing this bug"?

Does the error happen randomly only, for some runs?

Or are you really getting the same symptoms: When the error happens, it consistently happens for all runs. And only system restart helps?
Guest

Seeing this bug again in 5.9.4.0

Is there some number of times running winscp where this bug kicks back in even in the newer versions?
Yannick

Thank you for the information. We'll upgrade the old clients to the new version and hope it won't break again :wink:

Kind Regards,
Yannick
martin

Re: Same issue

Yes, it's a know issue with WinSCP .NET assembly 5.2.4 and older:
https://beta.winscp.net/tracker/996

And as commented in the tracker:
While the fixed versions no longer gradually exhaust system resources, they cannot recover resources exhausted by previous buggy versions.


So the old version breaks even the application that uses the new version.
Yannick

Re: Same issue

Yannick wrote: