| | | Forum Newbie
       
Group: Forum Members Last Login: 4/14/2008 3:41:00 PM Posts: 9, Visits: 4 |
| Dear Friends, I'm getting an error 80004005 these days for downloading pretty large files. It happens at the very end of process. The downloed file is usable. But the error is really a big trouble for me. More strange thing is this error does not occur for smaller size files. I have searched everywhere for this error, but no help. Can anyone give me a guild how to trouble shooting this problem. I have WSFTP Pro SDK8.0 in VB 6.0. Transfer progress, 149308710 bytes transferred Transfer finished, 149309015 bytes transferred [2005.11.02 10:59:12.907] Error result 80004005 reading response line [2005.11.02 10:59:12.917] # transferred 149309015 bytes in 22461.325 seconds, 51.933 Kbps ( 6.492 Kbps), transfer failed. [2005.11.02 10:59:12.987] QUIT [2005.11.02 10:59:12.987] Error 825e0000 Sending Command. The connection is probably dead. [2005.11.02 10:59:12.997] Dead connections are not restarted For "QUIT" commands. [2005.11.02 10:59:13.008] Connection closed. Ready for next connection. |
| | | | Time Traveler
       
Group: Ipswitch Employees Last Login: Today @ 4:27:41 PM Posts: 228, Visits: 1,379 |
| I think the problem you are having is that the control channel breaks or timeout on large transfers because it does not have any activity during this time. (files are transferred using another TCP connection, a data channel). In your case, based on the log, the transfer took 22461.325 seconds, which is more than 6 hours. There could be a router on the way that it timing out the connections without activity in certain period of time. That is why small transfers do not have this problem. Claudio Robles WS_FTP Team |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 4/14/2008 3:41:00 PM Posts: 9, Visits: 4 |
| Hi Claudio, Thank you for replying back. Your answer makes sence to me. I will check with my team to find out the timeout setting. Lanex. |
| |
|
|