Hi I'm running a preupgradecheck on an SP2 MOSS2007 farm. The check runs through fine until it gets to the SPSearchInfo section whereupon it fails with: SPSearchInfo... Information Only An error occurred while parsing EntityName. Line 11, position 65. It may be that its failing immediately after the SPSearchInfo check rather than during it as it displays the 'Information Only' message before the error message. Has anyone seen this before? Any fixes? Cheers Mike

Public internet search and private support database search indicate that the error "An error occurred while parsing EntityName" is usually caused by special character such as "&" use in places such as SharePoint group name. Could you please check the pre-upgrade operation output http://technet.microsoft.com/en-us/library/dd793609(office.12).aspx#bk_output or ULS log (http://blogs.msdn.com/b/opal/archive/2009/12/22/uls-viewer-for-sharepoint-2010-troubleshooting.aspx ) to see if you can find any information about where the special character is used? Gu Yuming TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

I search a little bit on internet and within microsoft private support database. The error "An error occurred while parsing EntityName" is usually caused by special characters such as "&" use in places such as SharePoint group name. Could you please check the pre-upgrade operation output http://technet.microsoft.com/en-us/library/dd793609(office.12).aspx#bk_output or ULS log (http://blogs.msdn.com/b/opal/archive/2009/12/22/uls-viewer-for-sharepoint-2010-troubleshooting.aspx ) to see if you can find any information about where the special character is used? Gu Yuming TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

Hi I've been unable to find an '&' character in either of the xlm rule files (WssPreUpgradeCheck.xml and OssPreUpgradeCheck.xml) or indeed any part of these files. The failuer appears to be in WssPreUpgradeCheck.xml. Line 11 looks like this: <Substitution Name="SearchRuleAssembly">Microsoft.SharePoint.Search, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Substitution> The ULS logs give a similar error message but include the call stack: stsadm: An error occurred while parsing EntityName. Line 11, position 65. Callstack: 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.LoadNode(Boolean skipOverWhitespace) at System.Xml.XmlLoader.ParsePartialContent(XmlNode parentNode, String innerxmltext, XmlNodeType nt) at System.Xml.XmlLoader.LoadInnerXmlElement(XmlElement node, String innerxmltext) at Microsoft.SharePoint.StsAdmin.SPHealthAnalyzerReport.ConvertReportToXml() at Microsoft.SharePoint.StsAdmin.SPHealthAnalyzerReport.SaveAsXml(String s) at Microsoft.SharePoint.StsAdmin.SPPreUpgradeCheck.Run(StringDictionary keyValues) at Microsoft.SharePoint.StsAdmin.SPStsAdmin.RunOperation(SPGlobalAdmin globalAdmin, String strOperation, StringDictionary keyValues, SPParamCollection pars) Does this help? Cheers Mike

Also, just curious what CU are you running for the preupgrade check I prefer at least 10/2010 and always use the 12/2010 CU for SP2007, but do not deploy the 12/2010 CU to SP2010.. -Ivan Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.

Still on sp2 but April 2011 CU is planned for tomorrow.

HI Mike, 1. Remove the start addresses with ampersand sign(s) from any content sources. (OR) 2. Remove the 'SearchContentSourcesInfo' rule of the 'OssPreUpgradeCheck.xml' file: a) Open the 'OssPreUpgradeCheck.xml' file which is located in the folder 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG\PreUpgradeCheck' b) Remove the following lines: Title="{0}" Text="{1}" P0="$.[1]" P1="$.[2]"/> c) Save the 'OssPreUpgradeCheck.xml' file. then re run the pre-upgrade and check. Thanks, Raj

HI Mike, PLease let us know the outcome if you have followed my above plan. Thanks, Raj

Hi Mike, If your issue is resolved or you need more guidance please let us know, if resolved please close the post. -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.

HI Mike, PLease let us know the outcome if you have followed my above plan. Thanks, Raj