VAST error codes / Parsing and schema
VAST error 100: XML parsing error
Short answer: The player could not parse the VAST document as XML.
Debug this tag now
If you only have a live URL, test it first. If the failure is in the wrapper chain, inspect each hop. Validate resolved XML when you already have the response.
What your player reported
100· XML parsing error.
Wording from the IAB VAST 4.3 specification error table. Players may shorten or reformat it, but the code is the same.
What it means
The response never got far enough to be treated as VAST. The XML itself is malformed, so the player stops before reading any ad.
Common causes
- Unescaped `&`, `<`, or `>` in a URL that was not wrapped in CDATA
- Broken or unterminated `<![CDATA[ ... ]]>` sections
- Mismatched or unclosed tags, or invalid nesting
- A truncated response, or HTML (an error page) returned instead of XML
How to fix it
Paste the raw response into the validator. A 100 is almost always a structural XML problem the validator points to by line, not a VAST-semantics problem.
VAST error codes are runtime buckets emitted by the player. They tell you where the failure happened, not which line of XML caused it. Paste the raw tag into the validator to map this code onto the exact element and rule.
Related vastlint rules
- VAST-2.0-root-element: Root element must be <VAST>
Related error codes
Debug this tag now
Validate the XML, follow the wrapper chain, or check it in CI before launch:
# CLI: exits non-zero on errors, ideal for pipelines
vastlint check creative.xml