Tuesday, August 7, 2018

SharePoint migration (2010, 2013, 2016) errors correction

Many of us have faced migration to the new version SharePoint server and, of course, not without exception, experienced difficulties with errors, today I will describe the mistakes I personally encountered and try to show one or more solutions.

We have already attached the database to MS SQL Server and open Windows PowerShell ISE (run as Administrator). Make sure that the account under which we work has system account rights on the current farm SharePoint server and db_owner for a migrated database.
Now add script "Add-PSSnappin":

Add-pssnapin Microsoft.sharepoint.powershell

Now add script "Test-SPContentDatabase", if you need comfortable view use "Out-GridView"

Test-SPContentDatabase -Name WSS_ContentSPS -WebApplication http://sp-test | Out-GridView
OR export data to file "Export-Csv"
Test-SPContentDatabase -Name WSS_ContentSPS -WebApplication http://sp-test | Export-Csv -path 'C:\TestMigration_WSSContentSPS_07.08.2018.csv' -Encoding unicode -Delimiter "`t"
Run script and will see error:

Category : MissingAssembly
Error : True
UpgradeBlocking : False
Message : Assembly
[Microsoft.ReportingServices.SharePoint.UI.ServerPages,
Version=14.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91] is referenced in the
database [WSS_ContentSPS], but is not installed on the
current farm. Please install any feature/solution which
contains this assembly.
Remedy : One or more assemblies are referenced in the database
[WSS_ContentSPS], but are not installed on the current
farm. Please install any feature or solution which contains
these assemblies.


How is the fix? You can install the solution or if you are sure that you do not need this solution on the current farm, then you can delete it via T-SQL, first open MS SQL Management studio, click create query and select the database you need, then add script (you need table "EventReceivers" -> column "Assembly")
Select * from EventReceivers where Assembly like '%Microsoft.ReportingServices.SharePoint.UI.ServerPages,Version=14.0.0.0,Culture=neutral,PublicKeyToken=89845dcd8080cc91%'
We are convinced that this solution is really present and then delete:
Delete from EventReceivers where Assembly like '%Microsoft.ReportingServices.SharePoint.UI.ServerPages,Version=14.0.0.0,Culture=neutral,PublicKeyToken=89845dcd8080cc91%'


Category : MissingFeature
Error : True
UpgradeBlocking : False
Message : Database
[WSS_Content] has reference(s) to a missing feature: Id = [bf8b58f5-ebae-4a70-9848-622beaaf2043],
Name = [Power View Integration Feature], Description = [Enables interactive data exploration and visual presentation against PowerPivot workbooks and Analysis Services tabular databases.],
Install Location = [PowerView]."
","The feature with Id bf8b58f5-ebae-4a70-9848-622beaaf2043 is referenced in the database [WSS_Content]
but is not installed on the current farm.
The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary."


Is the addin for "SSRS installed" in your new farm.

Category : MissingWebPart
Error : True
UpgradeBlocking : False
Message : WebPart class
[6a1f4b36-329d-317b-802a-96130a9ae5e7] (class [Microsoft.SharePoint.Portal.WebControls.BusinessDataFilterWebPart] from assembly
[Microsoft.SharePoint.Portal, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced [1] times in the database [WSS_Content], but
is not installed on the current farm. Please install any feature/solution which contains this web
part.","One or more web parts are referenced in the database [WSS_Content], but are not installed
on the current farm. Please install any feature or solution which contains these web parts."


Category : MissingWebPart
Error : True
UpgradeBlocking : False
Message : WebPart class
MissingWebPart,"True","False","WebPart class [69a2a58c-9b8d-d5c5-a7f6-a0feeeaf3867] (class
[Microsoft.SharePoint.Portal.WebControls.SpListFilterWebPart] from assembly
[Microsoft.SharePoint.Portal, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c]) is referenced [10] times in the database [WSS_Content],
but is not installed on the current farm. Please install any feature/solution which contains this web part."


After you migrate the sites on Microsoft SharePoint Server 2013 to SharePoint Server 2016, the following web part controls no longer work on the migrated sites:

SpListFilterWebPart;
ExcelWebRenderer;
ReportViewerWebpart;

"Web part controls don't work after sites are migrated to SharePoint 2016."

Solutions: add your file web.config 2 row:
<SafeControl Assembly="Microsoft.SharePoint.Portal, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.Portal.WebControls" TypeName="SpListFilterWebPart" Safe="True" />
<SafeControl Assembly="Microsoft.SharePoint.Portal, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.Portal.WebControls" TypeName="BusinessDataFilterWebPart" Safe="True" />

To be continued,
Happy Coding!

No comments:

Post a Comment