Quantcast
Channel: Ocsinventory Q&A - Recent questions without answers
Viewing all articles
Browse latest Browse all 4605

XML has not well formed (invalid token)

$
0
0
I installed OCSinventory agent (2.6.0) onto a CentOS7 machine. It's reporting to an OCS inventory server, version 2.7.0. It fails with this error in the agent logfile:-

"[error] Cannot establish communication : 500 Internal Server Error"

The server has this error in the httpd error file:-

"not well-formed (invalid token) at line 931, column 18"

So, I did a debug run of the OCS agent, and the data around line 931 in the agent's XML file is:-

    <MONITORS>
      <BASE64>AP///////wAe1gcJPTa9ABoNAQJoHhd46mP4nlZMmCQZUFW/74DRQIGAgYqBj6lAqUqpTwEBAAAA
/ABLVk0ARzU2MTAgCiAgAAAA/AAxOTIweDE0NDAKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAOk=
</BASE64>
      <CAPTION>KVM^@G5610 1920x1440</CAPTION>
      <DESCRIPTION>26/2003</DESCRIPTION>
      <MANUFACTURER>Unknown manufacturer code GVV</MANUFACTURER>
      <SERIAL>12400189</SERIAL>
    </MONITORS>
I believe the error is because of the ^@ character in the <CAPTION> line. Any ideas how to fix this?

Thank you, Symon

Viewing all articles
Browse latest Browse all 4605

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>