Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The search results page throws an exception when a name in a document metadata column contains "&", "<", or ">" characters in SharePoint Server 2010


View products that this article applies to.

Symptoms

You perform a search on a Microsoft SharePoint Server 2010 site. However, the search results page throws an exception when a name in a document metadata column contains the & character, the < character, or the > character. Additionally, the following Unified Logging Service (ULS) log is logged:

[Time] w3wp.exe (0x0B84) 0x29C0 SharePoint Server Search Query g1j9 Exception Internal server error exception: System.Xml.XmlException: An error occurred while parsing EntityName. [LineNumner, PositionNumber.] at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ParseEntityName() at System.Xml.XmlTextReaderImpl.ParseEntityReference() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlLoader.ParsePartialContent(XmlNode parentNode, String innerxmltext, XmlNodeType nt) at System.Xml.XmlLoader.LoadInnerXmlElement(XmlElement node, String innerxmltext) at Microsoft.Office.Server.Search.WebControls.TaxonomyFilterGenerator.CreateFilterResultElement(XmlDocument filterXml, String filterId, String displayName, FilterCategory filterCategory, String mappedProperties, SortedList`2 filterValueList, String associateTermSets) at Microsoft.Office.Server.Search.WebControls.TaxonomyFilterGenerator.CreateMetadataColumnFilters(XmlDocument filterXml, List`1 filterValue, Int32 maxFilterCats, FilterCategory fc, Boolean includeAutoFilters) at Microsoft.Office.Server.Search.WebControls.TaxonomyFilterGenerator.GetRefinement(Dictionary`2 refinedData, XmlDocument filterXml, Int32 maxFilterCats) at Microsoft.Office.Server.Search.WebControls.RefinementManager.MergeFiltersFromGenerators() at Microsoft.Office.Server.Search.WebControls.RefinementManager.GetRefinementXml() at Microsoft.Office.Server.Search.WebControls.RefinementWebPart.GetXPathNavigator(String viewPath) System.Xml.XmlException: An error occurred while parsing EntityName. [LineNumber, PositionNumber.] at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ParseEntityName() at System.Xml.XmlTextReaderImpl.ParseEntityReference() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlLoader.ParsePartialContent(XmlNode parentNode, String innerxmltext, XmlNodeType nt) at System.Xml.XmlLoader.LoadInnerXmlElement(XmlElement node, String innerxmltext) at Microsoft.Office.Server.Search.WebControls.TaxonomyFilterGenerator.CreateFilterResultElement(XmlDocument filterXml, String filterId, String displayName, FilterCategory filterCategory, String mappedProperties, SortedList`2 filterValueList, String associateTermSets) at Microsoft.Office.Server.Search.WebControls.TaxonomyFilterGenerator.CreateMetadataColumnFilters(XmlDocument filterXml, List`1 filterValue, Int32 maxFilterCats, FilterCategory fc, Boolean includeAutoFilters) at Microsoft.Office.Server.Search.WebControls.TaxonomyFilterGenerator.GetRefinement(Dictionary`2 refinedData, XmlDocument filterXml, Int32 maxFilterCats) at Microsoft.Office.Server.Search.WebControls.RefinementManager.MergeFiltersFromGenerators() at Microsoft.Office.Server.Search.WebControls.RefinementManager.GetRefinementXml() at Microsoft.Office.Server.Search.WebControls.RefinementWebPart.GetXPathNavigator(String viewPath)Time

↑ Back to the top


Resolution

To resolve this issue, apply this following hotfix package: 
2459257 Description of the SharePoint Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package): December 31, 2010

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Keywords: kbqfe, kbsurveynew, kbexpertisebeginner, kb

↑ Back to the top

Article Info
Article ID : 2464368
Revision : 1
Created on : 1/7/2017
Published on : 1/21/2011
Exists online : False
Views : 238