AxioWorks | Error: "There is an error in XML document"

This error is raised when a list contains "dirty" characters in its XML. A common cause for this is when a user copy&paste formatted text from Word or PowerPoint into an HTML SharePoint column.

This is a SharePoint issue and, unfortunately, it is not possible for SQList to pinpoint the exact list item that causes the error.

You can use our WSSDebug the utility to run a health check against the list.

For example:

c:\Temp\WSSDebug>WSSDebug.exe lhc "myuser.name" "password1" "mydomain" "authWindows" "http://my-sp-server/sites/my-site" "out.xml" "MyList"

This command will check all items in the list, on by one, and report any items that fail to be retrieved via the web services. Once you find the culprit item(s), you can edit (or remove) them directly in SharePoint; it usually comes down to special characters pasted in text columns. All results are stored in the "out.xml" file.

We hope this allows you to solve your issue. Unfortunately there is not much more we can do from here, but please let us know how it goes.

You can download the WSSDebug utility from here:

http://support.axioworks.com/sqlist-v5-how-to/how-to-use-the-wssdebug-utility

Described below, is how a customer of ours was able to resolve this issue.

I did some research regarding the error (see email below) on our side and found out that the error seems to be caused by bad characters.

When I try to generate a report with "Report Builder 3.0" and user "SharePoint List" as a datasource and http://intranet (the root site) as the connection string I get the same error (but with more details):
==================================
'
', hexadecimal value 0x0B, is an invalid character. Line 1, position 9610. (System.Xml)
------------------------------
Program Location:
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
   at System.Xml.XmlTextReaderImpl.Throw(Int32 pos, String res, String[] args)
   at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
   at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
   at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
   at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
   at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
   at System.Xml.XmlTextReaderImpl.ParseAttributes()
   at System.Xml.XmlTextReaderImpl.ParseElement()
   at System.Xml.XmlTextReaderImpl.ParseElementContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlTextReader.Read()
   at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
   at System.Xml.XmlLoader.ReadCurrentNode(XmlDocument doc, XmlReader reader)
   at System.Xml.XmlDocument.ReadNode(XmlReader reader)
   at System.Xml.Serialization.XmlSerializationReader.ReadXmlNode(Boolean wrapped)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderSPListService.Read53_GetListCollectionResponse()
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer102.Deserialize(XmlSerializationReader reader)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)

Some analysis brought me to the following site which explains the error: http://weblogs.asp.net/rajbk/Contents/Item/Display/345

Some more information can can be found also here:

https://social.msdn.microsoft.com/Forums/office/en-US/36afb9b5-6d6e-41ec-9bd5-e4b38d5d4557/listservicegetlistitems-xml-exception-for-invalid-character-need-clarification?forum=sharepointdevelopmentlegacy

http://blogs.technet.com/b/stefan_gossner/archive/2009/08/26/how-to-deal-with-invalid-characters-in-soap-responses-from-asp-net-web-services.aspx

Note: AxioWorks Ltd does not take responsibility for content and technical solutions offered by third parties.

Our use of cookies

Popular articles

More support options:

Error: "There is an error in XML document"