Troubleshooting MFT text data conversion error BFGIO0060E

What to do if a Managed File Transfer text transfer fails with error BFGIO0060E "Text data conversion has failed".

About this task

A text transfer can fail with error BFGIO0060E for one of two reasons:

• One or more characters in the source file cannot be converted from the source file code page to the destination file code page. This problem can occur when code pages have different character sets and certain characters cannot be converted between them.
• The source file encoding does not match the default encoding of the source agent. In this case performing a text transfer by using the default settings corrupts the character data.

• If it is acceptable for some characters not to be converted, define a replacement character sequence at the destination agent so that the transfer does not fail.

  Specify the agent property textReplacementCharacterSequence to define a replacement character sequence. For more information, see Advanced agent properties: Input/output.

• Transfer a source file that does not have the same encoding as the source agent:
  • Specify the file encoding in a transfer definition file. For more information, see Using transfer definition files.
  • Specify the file encoding by using the -sce parameter with the fteCreateTransfer command. For more information, see fteCreateTransfer: start a new file transfer.
  • Specify the file encoding as part of an Ant move or copy task. For more information, see Using Apache Ant with MFT.
• Check that you have selected the correct source file encoding for a transfer:
  1. Set the destination file encoding to UTF-8.
  2. Transfer the file in text mode.
  3. Use a UTF-8 file viewer to view the contents of the file. If all characters in the file are correctly displayed, the source file encoding is correct.