Error message in pipe log "Content is not allowed in prolog"
- Article Type: General
- Product: Primo
- Product Version: 4.5
Problem Symptoms:
The following error message can be found the log file of the failed pipe.
=====================
2014-02-04 16:01:04,669 INFO [t-SplitRecords] [c-ZipReader] - nextRecord=new_BELI07.xml
2014-02-04 16:01:04,670 ERROR [t-SplitRecords] [c-RecordSplitter] - from new_BELI07.xml
org.xml.sax.SAXParseException: Content is not allowed in prolog.
=====================
Cause:
This error is probably related to a byte order mark (BOM) prior to the actual XML content.
The encoding can cause some additional bytes/ spaces/ spl characters (invisible in the web browser).
For example UTF-8 --- EF BB BF
Parse the returned string and discard the BOM, so SAXParser can process the document correctly.
Resolution:
Remove extra the character
1. Remove with notepad, xml editor or re-save it in XML editor
Category: Primo
- Article last edited: 6/28/2014