Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 5399 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error Check of update source failed due to unexpected error 'XML_ERROR_INVALID_TOKEN'.

torpy

Hello Sophos Community,

One of our SUMs started acting up the other day and is unable to update from Sophos. Looking at the logs I consistently see the following error: "    Error    Check of update source failed due to unexpected error 'XML_ERROR_INVALID_TOKEN'."

Any ideas on how to fix this?

Thanks!

:15539


This thread was automatically locked due to age.
Parents
  • 0
    Looks like also the "self update" fails - please check the SUM version reported to SEC. Where does this SUM update from? If the source is not Sophos only a subset of the Warehouse is available to a "child" and there might be incompatibilities. If this is the cause, the question is why this SUM is backlevel - as it is set to RECOMMENDED it should be current.

    Christian
    :15797
Reply
  • 0
    Looks like also the "self update" fails - please check the SUM version reported to SEC. Where does this SUM update from? If the source is not Sophos only a subset of the Warehouse is available to a "child" and there might be incompatibilities. If this is the cause, the question is why this SUM is backlevel - as it is set to RECOMMENDED it should be current.

    Christian
    :15797
Children
No Data