Contents
To troubleshoot the issue, you could check if the SharePoint 2010 is upgraded to SharePoint 2013 successfully from upgrade log. “If you can obtain a missing server-side file or dependency, install it, and then run upgrade again for the affected sites.
If you are performing an upgrade to SharePoint 2013, you can start the site collection upgrade after you have addressed all issues from the health checks. You can create an upgrade evaluation site to try the new user interface for your site, or you can upgrade your site collection directly.
When to run site collection health checks in SharePoint 2013?
For a visual overview of the entire upgrade process, see Overview of the upgrade process from SharePoint 2010 to SharePoint 2013. You run the health checks manually to prepare for an upgrade. In addition, the health checks are run automatically in repair mode when you start to upgrade a site collection.
How to stop the SharePoint content DB upgrade?
100.00% : SPContentDatabase Name=groups_contentMount-SPContentDatabase : Content database data integrity check has encountered a severe issue that upgrade process must be stopped. S how to resolve this issue. + Mount-SPContentDatabase “groups_content” -WebApplication “http://2010groups.port
In SharePoint migration, The source SharePoint 2010 environment sites contains references to some of the Feature files and those features are not installed in the target SharePoint 2013 Farm. Well, The resolution is: Install & Deploy all solutions from the source farm to the destination farm.
Getting “MissingSetupFile” errors when you run the “Test-SPContentDataBase” cmdlet on SharePoint content databases during a migration process. [MissingSetupFile] File [Features\\Feature-folder\\feature-artifact] is referenced [1] times in the database [SharePoint_Content_database], but is not installed on the current farm.