FTP Transfer Stopped Working

Martin,
Here is the pertinent information for this transfer: I am running Version 5.9.3.7136; Server 2012 R2; FTP transfer; Scripted transfer; Logfile at Level 2, which I have attached. This transfer was working correctly until an upgrade of some sort was performed at the remote site. They mentioned that they do not support WinSCP, but they didn't seem to know whether it might be a setting that needs to be changed on my end. As all of my other transfer jobs use WinSCP, I would prefer to continue using it for all of my jobs. Thank you.

451-Data set is out of space.

It looks you run out disk space or user quota.

I was telling them that it seemed to be a space issue, but they said that it was because they didn't support WinSCP. I'm not so sure that those I am dealing with are familiar with the hardware side. I'll try to find someone who might understand what the actual upgrade was, and why it is affecting the transfer. Thanks for you rhelp.

jmt1991 wrote:

but they said that it was because they didn't support WinSCP.

Sounds like a lame excuse for their incompetence to deal with the problem.

Martin,
They finally got back to me and told me to use Ipswitch WS_FTP. I don't want to use that program because I have all of our other transfers using WinSCP. I used the -implicit switch with the Open command, and am unable to connect. I have attached a log.
If it is any help, here is the script from Ipswitch that they provided:
TRACE SCREEN
LOG SCREEN
USER Username
PASS Password
CONNECT TEST_SSL
SYST
PBSZ 0
PROT P

CDUP
TYPE A
PUT Filename
CLOSE

Martin,

I have a job configured to transfer files each night after hours. A few months ago it stopped working. We have been busy with other things and are just now getting back to this to determine why it stopped working. I'm using ver 5.5.3 on Windows Server 2008 R2.
I have a simple .bat file:
start winscp.com /script=DailyScript2.txt

that runs a simple script:
option confirm off
open CallMiner
put TEST1*.zip
a
a
exit

Our files tend to have around 8000 records. This was never a problem in the past. Now I get a timeout and disconnect error. I have tried extending the timeout setting, but it does not help. When I test with a small batch of records like 450, the transfer succeeds. When I test with larger files it fails half way through and starts the transfer all over again. Also, I have been using FileZilla to transfer the files since WinSCP stopped working, and have had no problems. The only thing is I haven't been able to set up a job to automate FileZilla, which is why I am trying to fix whatever has gone wrong with WinSCP. I did ask the file recipient if they made any configuration changes and they claim they have not made any. I have attached my log file. Any help you can give is appreciated. Thanks.

jmt1991 wrote:

Martin,
They finally got back to me and told me to use Ipswitch WS_FTP. I don't want to use that program because I have all of our other transfers using WinSCP.

At least try it. And if it works, show us its log file.

I used the -implicit switch with the Open command, and am unable to connect.

Did you try the -explicit switch?

Greg1 wrote:

Our files tend to have around 8000 records. This was never a problem in the past. Now I get a timeout and disconnect error. I have tried extending the timeout setting, but it does not help. When I test with a small batch of records like 450, the transfer succeeds. When I test with larger files it fails half way through and starts the transfer all over again. Also, I have been using FileZilla to transfer the files since WinSCP stopped working, and have had no problems. The only thing is I haven't been able to set up a job to automate FileZilla, which is why I am trying to fix whatever has gone wrong with WinSCP. I did ask the file recipient if they made any configuration changes and they claim they have not made any. I have attached my log file. Any help you can give is appreciated. Thanks.

The number of files is not the problem. It's rather the size of the individual files. The file on which it fails in over GB large.
Try setting a longer timeout using the -timeout switch.
https://winscp.net/eng/docs/scriptcommand_open#timeout
If this does not help, please start your own thread (your problem is irrelevant to this topic) and post a new log file.

Martin,
I tried the transfer using their recommended software and settings, with no success. I found another program to use while I work with them to find out what is happening.

What is their recommended software? What program does work?