XML error apparently... any ideas?

Rob Jones

Trying to work with an on-prem server and something has changed... got this error message above and in house support is stumped. Any ideas what could have caused this and if we can repair the xml (if it's even got an error?)

Karen Weir

Hi @Rob Jones , I have moved your post so that our Content Server experts can review:

Trying to work with an on-prem server and something has changed... got this error message above and in house support is stumped. Any ideas what could have caused this and if we can repair the xml (if it's even got an error?)

Greg Griffiths

@Rob Jones can you provide some more details on what you were doing to cause the issue ? if you can get the actual request to OTCS you can run that in the browser and see the XML being returned to review as that may help spot the issue.

Appu Nair

@Rob_Jones this RH is the one establishing a connection to Enterprise Connect

?Func=ngd.ucroot if you put that in a browser tacked to the URL of the content server you should get a valid XML document. One could check that as well. Some troubles in JSON/XML will happen if the obscure command "show weblingo comments " is set on Content Server admin pages .

Some pointers to help...