ThomasKluge wrote:

I did not see this error again since I use version 5.1.2.
This is the first version for me which really does support unattended up-/downloads.

Thanks for your feedback.

I did not see this error again since I use version 5.1.2.
This is the first version for me which really does support unattended up-/downloads.
Thank you.
Thomas

*done*

ThomasKluge wrote:

Yes it's working with this release but is somewhat unstable. I get messages like: "Invalid access to memory" and invalid drive access messages.

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

Yes it's working with this release but is somewhat unstable. I get messages like: "Invalid access to memory" and invalid drive access messages.

As you can see in the tracker, this got resolved in 5.0.3 beta. You are using 4.3.7. Try upgrading. Let me know.

martin wrote:

Thanks for your post. This issue is being tracked already.

No, this issue is not resolved!

See my trace with the latest release:

. 2012-06-08 01:25:37.475 WinSCP Version 4.3.7 (Build 1679) (OS 6.1.7601 Service Pack 1)
. 2012-06-08 01:25:37.475 Configuration: HKEY_CURRENT_USER\Software\Martin Prikryl\WinSCP 2\
<snip>
. 2012-06-08 11:15:44.002 [Background 1] Waiting for dispatching send buffer timed out, asking user what to do.
. 2012-06-08 11:15:44.002 [Background 1] Asking user:
. 2012-06-08 11:15:44.002 [Background 1] Host is not communicating for 60 seconds.
. 2012-06-08 11:15:44.002 [Background 1]
. 2012-06-08 11:15:44.002 [Background 1] Wait for another 60 seconds? ()
<snip>

. 2012-06-08 12:09:27.429 Sending null packet to keep session alive.
. 2012-06-08 12:09:27.429 Sending special code: 15
. 2012-06-08 12:09:57.474 Sending null packet to keep session alive.
. 2012-06-08 12:09:57.474 Sending special code: 15
. 2012-06-08 12:10:27.904 Sending null packet to keep session alive.
. 2012-06-08 12:10:27.904 Sending special code: 15

<snip -> this is what happens after clicking on close icon>

. 2012-06-08 12:10:45.430 [Background 1] Attempt to close connection due to fatal exception:
* 2012-06-08 12:10:45.430 [Background 1] Terminated by user.
. 2012-06-08 12:10:45.430 [Background 1] Closing connection.
. 2012-06-08 12:10:45.430 [Background 1] Sending special code: 12
. 2012-06-08 12:10:45.430 [Background 1] Sent EOF message
. 2012-06-08 12:10:47.430 [Background 1] Looking up host "<removed>"
. 2012-06-08 12:10:47.430 [Background 1] Connecting to <removed> port 22


This behavior prevents unattended uploads. It is really annoying.

best wishes,
Thomas

Thanks for your post. This issue is being tracked already.

This behavior does not make sense to me:

The Warning "Host ist not communicating for more than 15 seconds. Still waiting..."
Warning: Aborting this message will close connection!

If I press "Abort" the connection will be closed and reastablished.

Would like to have this automatically and none blocking, especially if I leave my PC allone uploading large files.

regards,
Thomas