The data map contains a VERSION record and so must be in UTF8 but some bytes break the rules for UTF8. On Windows the problem might be caused by incorrectly saving a DMP file containing a VERSION record as ANSI.
The data map is not loaded. Processing ends.
If the problem exists in the exported data maps file used by the PowerExchange Listener, then refresh the data map by sending it from the PowerExchange Navigator.
If the problem exists in the data map (DMP) file used by the PowerExchange Navigator, edit the DMP file by using an external editor.
If a VERSION record is present and the characters are not in UTF8, then it is best to delete the VERSION record, ensure that the characters are in the ISO-8859 code page (on Windows, save as type ANSI), and then edit the map in the PowerExchange Navigator. If that is not successful, correct the invalid characters - either in UTF8 if the VERSION record is present, or in ISO-8859 if the VERSION record is absent.