Fix(XML): Sanitize invalid char#182
Merged
Merged
Conversation
bc8b7b1 to
bdba55d
Compare
2 tasks
Contributor
|
@stonebuzz the xml file is now ok: Text: xmlvalidation tell me "no errors were found" in file. But the error continue, the sccm.log says: I have launch several times and I have ensure the new file is generated but error persists.. |
Contributor
Author
|
@tolemac best regards |
Contributor
|
👍 done!! Good job, now this work fine! |
Rom1-B
requested changes
Jun 3, 2026
Co-authored-by: Romain B. <8530352+Rom1-B@users.noreply.github.com>
Co-authored-by: Romain B. <8530352+Rom1-B@users.noreply.github.com>
Rom1-B
approved these changes
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist before requesting a review
Please delete options that are not relevant.
Description
SCCM stores certain metadata in fixed-length
NCHARdatabase fields. In some cases, these fields may contain trailing null bytes, residual binary data, or Unicode non-characters such asU+FFFEandU+FFFF. When this data is exported into XML files, it can introduce characters that are not valid according to the XML 1.0 specification.As a result, the inventory import or push process may fail with an XML parsing error, preventing successful processing of the generated file.
Example of a corrupted value observed in production environments:
And should be
In this example, unexpected trailing characters are appended to the publisher name. These characters originate from corrupted or improperly sanitized database content and generate invalid XML output, leading to parsing failures during downstream processing.
Fixes #181
Screenshots (if appropriate):