Yes, it appears that there is non-standard character in the base XML data that the Container uses, causing a failure. I've alerted @joagomez as to the root cause and potential solution:
The good news is that even if he isn't able to do something in time, if the program falls out of the guide, then things should work again. However, for future proofing, a more robust removal/replacement of non-standard characters or more graceful error handling (i.e., skip the offending item and continue) would still be recommended to be implemented.

