0

Question: What can cause that in rare times (in a few %), 0 Byte sized files are created over FTP with the following errormessage:

Data was truncated on an input, output or update operation

UPDATE: the mode is "BINARY". The problem still occurs.

  • I wonder if this has to do with the BINARY versus ASCII modes. Try the `BIN` command before you upload and see if that resolves the issue. Depending on the FTP client you're using specifying BINARY MODE versus ASCII mode for the transmissions and the defaults may be different. Let me know whether or not this helps you any and if so I will add as an answer. – Pimp Juice IT Jan 30 '16 at 02:56
  • Are you by any chance connecting in FTP Active mode ? In that case, the actual data channel is a TCP session opened from the server to the client, which is pretty much guaranteed to fail in any scenario where a firewall is involved. This could potentially result in a 0 byte result, though I would have expected it to end with a timeout error. – Jeremy Gibbons Jan 30 '16 at 07:08
  • @1Fish_2Fish_RedFish_BlueFish : I updated the question, thanks – LoukiosValentine79 Jan 30 '16 at 11:01
  • @JeremyGibbons : First, the client tries with passive FTP, then when the error message occurs, it tries with Extended Passive FTP, then it timeouts. – LoukiosValentine79 Jan 30 '16 at 11:02
  • Where/how exactly you are seeing this "Data was truncated on an input, output or update operation" message? – Castaglia Feb 01 '16 at 20:45

0 Answers0