Timeout waiting for WinSCP to respond

I get error "Timeout waiting for WinSCP to respond" on scripts for one vendor. It occurs intermittently, several times a week (~5 of ~70 runs fail).
I have similar scripts to other vendors that do not get this error, so I think this could be a connection issue- but I'm open to the possibility that I have a configuration issue and hoped you might see something in the logs to indicate this.

I have reviewed documentation about this error, but had a question about:
"Alternatively, you can use (undocumented) property Session.XmlLogPath to change the log file location."

In my scripts, I set up locations for session and debug logs that I know the account running the script has access to. Are these logs different than the log mentioned above?
If so, would I set this (in Powershell) as: $session.XmlLogPath = "\\location_of_log\"

Thank you.

I do not see any "Timeout waiting for WinSCP to respond" error in the log file. Is this really a log file of the failed session? Can you post a callstack of the exception?

I have the script set up to create separate log files. I have attached the log file for the script itself, which shows the exception caught.

I also create separate session and debug logs for each connection the script makes and in the previous post attached the logs for the connection that failed.

I'm not sure what the callstack is, or I would post it.

OK, I didn't notice, that you are not using the latest version of WinSCP.

Please upgrade and post new session and debug log files.

martin wrote:

OK, I didn't notice, that you are not using the latest version of WinSCP.

Please upgrade and post new session and debug log files.

I have updated to the latest version. Again, this error occurs intermittently, so this is the first occurrence after updating.

Thank you.

WinSCP stops on waiting for the server to open file fil2041144889.mbx.PAH60384.75261.

I do not know if your server is ever going to respond, obviously.

Anyway, you have set SessionOptions.Timeout to 120 seconds.

But as Session.Timeout is set to its default 60 seconds, the .NET assembly will kill WinSCP after those 60 seconds, so WinSCP will never have a chance to wait 120 seconds.

If you really want WinSCP to wait 120 seconds (hoping the server ever responds), you have to set the Session.Timeout at least to 120 seconds too.

Thank you, I set session.timeout to 120 seconds.

I do not understand the difference between the sessionoptions.timeout and session.timeout.

Would it make sense for me to set sessionoptions.timeout to 120 seconds and session.timeout to a larger value?
Would I then get an error that says "Timeout waiting for the remote server" instead of "Timeout waiting for WinSCP to respond".
Or how would you expect these to be set?

martin wrote:

WinSCP stops on waiting for the server to open file fil2041144889.mbx.PAH60384.75261.

I do not know if your server is ever going to respond, obviously.

Anyway, you have set SessionOptions.Timeout to 120 seconds.

But as Session.Timeout is set to its default 60 seconds, the .NET assembly will kill WinSCP after those 60 seconds, so WinSCP will never have a chance to wait 120 seconds.

If you really want WinSCP to wait 120 seconds (hoping the server ever responds), you have to set the Session.Timeout at least to 120 seconds too.

GRR3 wrote:

Would it make sense for me to set sessionoptions.timeout to 120 seconds and session.timeout to a larger value?
Would I then get an error that says "Timeout waiting for the remote server" instead of "Timeout waiting for WinSCP to respond".

Yes. That's about right.