FilePart Issue

Advertisement

BigCRob64
Guest

FilePart Issue

Hey WinSCP,

I'm having a problem at a couple of our sites. We have a PowerShell script that routinely TFTPs two zipped folders with text files in them. This script results in multiple filepart files (all 192 KBs in size) on our file server at our Main Building.

The exact error I'm seeing is
Exception calling "PutFiles" with "2" argument(s): "Timeout waiting for WinSCP to respond"
This isn't consistent with every site, it only affects 3 or 4 of our 50 sites.

What I've already attempted
  • Increasing timeout to 30 seconds
  • Set buffer to 0 and 999999
  • Disabled transfer resume (This just created several unusable zip files, all 192 KBs in size)
  • Updated WinSCP
  • enabled logging and reviewed logs
The logs don't say anything specific, just that connection was timed out. I'd be happy to send them over for further review. I'd also be happy to share script privately.

Thanks for your help!

Further Details

WinSCP Version – Version 6.3.5 (Build 14991 2024-09-10)
Microsoft Version – Version 1.421.1095.0
Transfer protocol – TFTP
GUI / script – Powershell

Error Message -
Exception calling "PutFiles" with "2" argument(s): "Timeout waiting for WinSCP to respond
Log Message
. 2024-12-30 12:30:15.406 Waiting for data timed out, asking user what to do.
. 2024-12-30 12:30:15.406 Asking user:
. 2024-12-30 12:30:15.406 **Host is not communicating for 30 seconds.
. 2024-12-30 12:30:15.406 
. 2024-12-30 12:30:15.406 Wait for another 30 seconds?** ()
< 2024-12-30 12:30:15.406 Script: Host is not communicating for more than 30 seconds.
< 2024-12-30 12:30:15.406 Still waiting...
< 2024-12-30 12:30:15.406 Note: If the problem repeats, try turning off 'Optimize connection buffer size'.
< 2024-12-30 12:30:15.406 Warning: Aborting this operation will close connection!
  • SFTP Script.txt (5.63 KB, Private file)
Description: Our SFTP script that runs on our probe to zip and send the text files.
  • WINScpISSUE.png (142.4 KB, Private file)
Description: Picture of what we're seeing on our file server
Description: I replaced our public ip with "[PUBLIC IP]" for security.

Reply with quote

Advertisement

Advertisement

You can post new topics in this forum