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

ReluctantPowershellGuy

Re: Re: success and failure debug attached

I've increased the timeout from 2 minutes to 5. I'll see if that makes a difference.

$WinSCPconfig.TimeoutInMilliseconds = 300000
martin

Re: success and failure debug attached

The system seems to be under a heavy load.
Can you try to set the Session.Timeout to higher value?
ReluctantPowershellGuy

success and failure debug attached

Here's a debug log from both a successful job and a failure. It took a while because it actually hadn't failed in a few days.
martin

Re: Error: Timeout waiting for WinSCP to respond - WinSCP has not responded in time - 5.7.5

Please attach a full debug log files showing both the successful and failed run.

To generate log file, set Session.DebugLogPath. Submit the log with your post as an attachment. If you do not want to post the log publicly, you can mark the attachment as private.
ReluctantPowershellGuy

Error: Timeout waiting for WinSCP to respond - WinSCP has not responded in time - 5.7.5

Daily scheduled task running PowerShell script to perform SFTP upload. Frequently (but not always) errors out with "Timeout waiting for WinSCP to respond - WinSCP has not responded in time (response log file blabla.tmp was not created)". We know it's not permission issues since it does run successfully more than half of the time.

Server is 2008 R2
WinSCP version 5.7.5 with .NET library file 1.2.9.5665 (part of version 5.7.5).

Recently upgraded from 5.5.6 (and rebooted) but it hasn't made a difference.

Any tips on troubleshooting this further?

Documentation

Support

Associations

Follow Us