XML Parsing Troubleshooting

  • Last update: January 18, 2026
  • Overview

    This document introduces issues related to XML Parsing.

    Verifying the Standardization of XML Data Structure

    Abnormal Phenomenon:

    An error is reported when selecting a node: com.fr.dp.exception.FineDPException: xml data stream error - specific cause - error location

    Troubleshooting:

    1. Verify whether the XML-formatted data is valid.

    2. Check the completeness of XML tags and structures.

    3. Verify whether special characters are escaped.

    Error Report and Solutions:

    ErrorCauseSolution

    XML Sample Data:

    <person>
    <name age="24">Zhang San</name>
    </person>
    <person>
    <name age="27">Li Si</name>
    </person>
    <person>
    <name age="30">Wang Wu</name>
    </person>

    Error:

    com.fr.dp.exception.FineDPException: xml data stream error - Illegal to have multiple roots (start tag in epilog?). at [row,col {unknown-source}]: [6,6] - Illegal to have multiple roots (start tag in epilog?). at [row,col {unknown-source}]: [6,6]

    The root node tag is missing.Add a root node

    XML Sample Data:

    <person>
    <name age="24">Zhang San</person>
    </name>

    Error:

    com.fr.dp.exception.FineDPException: xml data stream error - Unexpected close tag </person>; expected </name>. at [row,col {unknown-source}]: [17,33] - Unexpected close tag </person>; expected </name>. at [row,col {unknown-source}]: [17,33]

    Tag nesting conflictAdjust tag position

    XML Sample Data:

    <text>
    <name>1<2</name>
    </text>

    Error:

    com.fr.dp.exception.FineDPException: xml data stream error - Unexpected character '2' (code 50) in content after '<' (malformed start element?). at [row,col {unknown-source}]: [31,17] - Unexpected character '2' (code 50) in content after '<' (malformed start element?). at [row,col {unknown-source}]: [31,17]

    Unescaped special characters

    If there are many characters that need escaping, you can use the CDATA tag to make the XML parser ignore special characters and treat them as character data.

    <![CDATA[Text content]]>

    Alternatively, use the replace function to replace escape characters.


    XML Sample Data:

    <person>
    <name age=24>Zhang San</name>
    </person>

    Error:

    com.fr.dp.exception.FineDPException: xml data stream error - Unexpected character '2' (code 50) in start tag Expected a quote at [row,col {unknown-source}]: [37,19] - Unexpected character '2' (code 50) in start tag Expected a quote at [row,col {unknown-source}]: [37,19]

    Missing quotes for attributesAdd quotes to attributes

    XML Sample Data:

    <person>
    <name>Zhang San</name>
    </Person>

    Error:

    com.fr.dp.exception.FineDPException: xml data stream error - Unexpected close tag </Person>; expected </person>. at [row,col {unknown-source}]: [44,12] - Unexpected close tag </Person>; expected </person>. at [row,col {unknown-source}]: [44,12]

    Uppercase tag nameCorrect the uppercase tag name.

    Data Preview Exception

    Abnormal Phenomenon:

    Nodes can be displayed normally when selected, but the preview is abnormal, either showing a blank page or throwing an error.

    Error:

    Namespace is incorrectly configured / XML nodes are not reselected after the namespace is modified

    com.fr.dp.exception.FineDPException: Spark execution error - xml namespace error - specific namespace

    Troubleshooting:

    Check whether the namespace exists and is correctly written.

    Verify whether the XML path is correct.

    Error Report and Solutions:

    ErrorCauseSolution

    com.fr.dp.exception.FineDPException: Spark execution error - xml namespace error - http://www.w3.org/2003/05/soap-envelope namespace uri is not exist in xml data - xml namespace error - http://www.w3.org/2003/05/soap-envelope namespace uri is not exist in xml data

    The XML nodes were not reselected after the namespace was modified.

    The error is caused by the failure to update the XPath path.

    Reselect the XML nodes to update the node path.


    Other Exception

    Field Parsing Exception

    Issue Description

    When parsing a specific field in XML, the field value can be parsed normally if the field is placed first in the parsing order; if it is not in the first position, the preview will be blank.

    Solution

    Upgrade to version 4.0.26 or later.


    附件列表


    主题: Data Development - Scheduled Task
    • Helpful
    • Not helpful
    • Only read

    滑鼠選中內容,快速回饋問題

    滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。

    不再提示

    10s後關閉

    Get
    Help
    Online Support
    Professional technical support is provided to quickly help you solve problems.
    Online support is available from 9:00-12:00 and 13:30-17:30 on weekdays.
    Page Feedback
    You can provide suggestions and feedback for the current web page.
    Pre-Sales Consultation
    Business Consultation
    Business: international@fanruan.com
    Support: support@fanruan.com
    Page Feedback
    *Problem Type
    Cannot be empty
    Problem Description
    0/1000
    Cannot be empty

    Submitted successfully

    Network busy