If you plan your SharePoint 2010 SP1 and June CU Upgrade, you may encounter some upgrade errors from Test-SPContentDatabase script. One of the popular error in the Test-SPContentDatabase you may find after you setup new test environment is as follows.
Category : MissingWebPart
Error : True
UpgradeBlocking : False
Message : WebPart class [baf5274e-a800-8dc3-96d0-0003d9405663] is referenced [20] times in the database [WSS_Content_it_ems_dev], but is not installed on the current farm. Please install any feature/solution which contains this web part.
Remedy : One or more web parts are referenced in the database [WSS_Content_it_ems_dev], but are not installed on the current farm. …
Category : MissingWebPart
Error : True
UpgradeBlocking : False
Message : WebPart class [07f48b68-2e69-c86a-ebe4-16359e03ebc2] (class [Microsoft.Office.Server.Search.WebControls.AdvancedSearchBox] from assembly Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [WSS_Content_it_ems_dev], but is not installed on the current farm. Please install any feature/solution which contains this web part.
Remedy : One or more web parts are referenced in the database [WSS_Content_it_ems_dev], but are not installed on the current farm. …
1. The “simple” procedures to resolve most of these errors is described here.
a. Open the following search center pages
b. Open the search administration page by following this procedure if you get error to access searchfarmdashboard.aspx page.
c. May need to iisreset/noforce and restart SharePoint 2010 Timer
2. There are some other similar errors you need to be aware of. You could identify from the class name they are all from search package. Here is the list you could found from logs. Here is the list of the class you might have error.
Microsoft.SharePoint.Portal.WebControls.SearchBoxEx |
Microsoft.Office.Server.Search.WebControls.SearchSummaryWebPart |
Microsoft.Office.Server.Search.WebControls.RefinementWebPart |
Microsoft.Office.Server.Search.WebControls.SearchStatsWebPart |
Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart |
Microsoft.Office.Server.Search.WebControls.SearchPagingWebPart |
Microsoft.Office.Server.Search.WebControls.QuerySuggestionsWebPart |
Microsoft.Office.Server.Search.WebControls.FederatedResultsWebPart |
Microsoft.Office.Server.Search.WebControls.HighConfidenceWebPart |
Microsoft.Office.Server.Search.WebControls.TopFederatedResultsWebPart |
Microsoft.SharePoint.Portal.WebControls.PeopleSearchBoxEx |
Microsoft.Office.Server.Search.WebControls.PeopleRefinementWebPart |
Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart |
Microsoft.Office.Server.Search.WebControls.AdvancedSearchBox 3. Way to identify mis-match webparts using db query. First, you could identify the features from 14 hive on all search related features and classes. Second, you could query the content database what webparts are installed. Here is the simple query. SELECT * FROM AllWebParts WHERE tp_Class is NOT NULL You could filtyer out the webparts based on class names. I have tried the procedure and it indeed cleaned up almost all errors except one with WebPart class [baf5274e-a800-8dc3-96d0-0003d9405663]. I'm not sure why other people were able to clean up even this one. We will continue working this and keep you posted. Here are some reference I could find for your reference. |
Great opinion.
ReplyDeleteLondon Escort Services