This error is usually related to a missing site template that is being used on the SharePoint 2010 farm but is not supported on the target farm 2013 or other.…
Category: Administrative
After running Test-SPContentDatabase you might get the following error : Category : Configuration Error : False UpgradeBlocking : False Message : The [Application name] web application is configured with claims…
Deploying / Publishing a Custom Web-Part
There are three steps for deploying / publishing a custom web part : adding, installing, and activating. the following is the code for installing a new WSP # Add the…
Remove a Feature from a content DB
This power shell code provide the option to remove missing features referenced on a content database migration log. Before migrating content Database you need to test the DB using the test-spcontentdatabase powershell…
Upgrade SharePoint Content Database 2016 – SharePoint experience error
Before attaching, mounting, upgrading ( all the same thing ) a SharePoint content DB from SharePoint 2013 to SharePoint 2016 you MUST test the DB Upgradeblocking errors, In order to…
Prepare SharePoint 2016 for Workflow Migration
The following steps needs to be completed prior of migrating any workflow data from SharePoint 2013 to 2016. even though not specified, I would recommend applying these steps on both…
Nintex Live ID – Get the existing Nintex Live ID on SP 2013
Nintex Live ID is an external end Point and you should copy it from the SharePoint 2013 as a preparation to a SharePoint 2016 migration. You can save it temporarily on a notepad.…