Error when generating mapping (in mapper) (MEC)

Hello,

I created a new mapping and it's validated.
When I try to generate it, I get an error forom "console commandes and output :

com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character (CTRL-CHAR, code 0) in prolog, after '<'.

Do you have any ideas about this kind of problem?

Regards.

Find more posts tagged with

General Discussions

Accepted answers

Jonathan Amiran

Hi,

Double-click on the xsd file (under documents) and it will open with the default XML Editor you set in MEC Mapper Preferences (best to use Notepad++).

Then examine the xsd file for unseen characters in the beginning of the file, it should be:

<?xml version="1.0" encoding="UTF-16" ?>

then save the file (you can ignore the utf-16 warnings).

right-click on Documents and select Update Document Checksums

then try to open and generate your map.

Jonathan

All comments

Jonathan Amiran

Hi,

Double-click on the xsd file (under documents) and it will open with the default XML Editor you set in MEC Mapper Preferences (best to use Notepad++).

Then examine the xsd file for unseen characters in the beginning of the file, it should be:

<?xml version="1.0" encoding="UTF-16" ?>

then save the file (you can ignore the utf-16 warnings).

right-click on Documents and select Update Document Checksums

then try to open and generate your map.

Jonathan

unknown

Hi Jonathan,

Thanks for your quick revert on this

I understand from your answer that I have to repair my XSD file according to the UTF-16 encoding and concerning the encoding, do I have to change it?
Also for PAT do I have to change the API communication in PAT to UTF-16 ?

Regards

Jonathan Amiran

Hi,

I'm not sure why the encoding is UTF-16 in the XSD, I usually ignore the error from Notepad++ and it works fine in the mapper.

As for PA, M3 API encoding, from my experience, is always UCS-2 (UTF-16 with no BOM) but it is not related to the schema encoding of the mapper.

Best regards,

Jonathan

unknown

Hi ,

Thank you very much the problem is solved with points that you communicated:

XSD (UTF-16, encoding UCS-2 LE BOM)
PA (UCS-2 (UTF-16 with no BOM)

Regards

unknown

Please forgive my pedantic hat for a moment. The relation between UCS-2 and UTF-16 is that of a subset rather than an equivalence. Both are encodings for Unicode. Both may, but are not required to, contain a Byte Order Mark (BOM). The difference is UCS-2 only supports the Unicode Basic Multilingual Plane (BMP). UTF-16 includes the concept of a surrogate pair which allows encoding of characters from the Unicode Supplementary Planes in addition to the BMP. As a result, UCS-2 should be considered obsolete (and technically it is no longer part of Unicode).

References:
* www.unicode.org/.../utf_bom.html - What is the difference between UCS-2 and UTF-16?
* www.unicode.org/.../utf_bom.html - What are some of the differences between the UTFs?
* www.unicode.org/.../appC.pdf - see section C.2 Encoding Forms in ISO/IEC 10646

Copyright © 2025 Infor. All rights reserved.