- Knowledgebase
- XML Schema
- Miscellaneous
-
Glossary
-
XML / ISO 20022 Standard
-
ISO 20022 Messages
-
XML Schema
- Miscellaneous
- Attribute
- Closing Tag
- Comment
- Content
- Cvc-complex-type
- Cvc-elt
- Cvc-id
- Cvc-identity-constraint
- Cvc-minexclusive-valid
- Cvc-mininclusive-valid
- Cvc-type
- Cvc-totaldigits-valid
- Cvc-attribute
- Cvc-datatype-valid
- Maximum Length
- Cvc-enumeration-valid
- Cvc-fractiondigits-valid
- Cvc-length-valid
- Cvc-maxexclusive-valid
- Cvc-maxinclusive-valid
- Cvc-maxlength-valid
- Cvc-minlength-valid
- Cvc-pattern-valid
- Element Value
- Encoding
- Length
- Mandatory element
- Missing
- Missing Tag
- Missing Child Element
- MIXD
- Root
- Unsupported Characters
- UTF-8
- Value
- Wrong Declaration
-
EPC SEPA
-
CGI-MP
-
US ACH (Nacha)
-
SWIFT MT
-
Finvoice
-
Bank-Specific
-
XMLdation Service Guides
-
Studio Guide
-
Simulator
MarkupNotRecognizedInContent
Notice! This page describes the nature of the error using a hypothetical example and not the erroneous data of the input test file. You should however be able to apply this information to your error case.
General description of the error:
The format of the error message: The content of elements must consist of well-formed character data or markup.
Error description in schema standard: http://www.w3.org/TR/2004/REC-xml-20...04/#NT-content
Meaning of error: Element or tag structure is not considered to be well-formed and service is not able to parse given content as XML.
Possible causes for this error:
- Tags are not presented correctly or data inside element consists of invalid characters. For reference a valid start tag, data and end tag looks like the following: <ElemNm>Data inside element</ElemNm>
- Tag consists of a non-allowed (first) character. Further reading at w3.org
Example
<GrpHdr>
<- almost a comment-->
<MsgId>2.012.001</MsgId>
Error message: Fatal Error MarkupNotRecognizedInContent : The content of elements must consist of well-formed character data or markup.
How to fix: In this case a comment was tried to be inserted before MsgId, but the structure of the comment is not correct and XML parsing thinks element starts with character <, and first character in element tag name is -. Correct way to mark a comment is to use character ! after <, as in <!--Comment-->
<GrpHdr>
<!--Comment-->
<MsgId>2.012.001</MsgId>