Upgrade SharePoint 2013 farm to SharePoint 2016 failed

Ashraf El-Maadidi 21 Reputation points
2020-11-10T22:05:55.197+00:00

Hi Guys,
I have migrated SharePoint 2013 farm to SharePoint 2016 farm. I Followed MS doc instructions at this link https://video2.skills-academy.com/en-us/sharepoint/upgrade-and-update/overview-of-the-upgrade-process.
Evrything was OK and I tried to test the ContentDb before attaching it I got a lot of error messages, for instance MissingSiteDefinition, MissingLanguagePack, MissingFeatures, MissingSetupfile and more.
The SharePoint 2013 farm is updated to SP1 and the SharePoint 2016 is updated with the latest CU and Swedish Languagepack.

Have you any idea how to solve these problems?

Best Regards
Ashraf

SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,934 questions
0 comments
Accepted answer
  1. Emily Du-MSFT 45,746 Reputation points Microsoft Vendor
    2020-11-11T09:46:01.32+00:00

    @Ashraf El-Maadidi
    1.MissingSiteDefinition
    A site cannot live without it's definition, get the web sites that are being referenced. If the websites are no longer needed, try deleting them from PowerShell.

    Remove-SPWeb http://sitename/subsite

    For more detailed information, refer to the blog:
    Resolving missing references

    2.MissingLanguagePack
    Try to restart the server and also try to re-install the language pack.

    3.MissingFeatures
    This issue occurs when missing the related features in the SharePoint 2016 farm. So, you need to make sure the missing features are installed and configured in your SharePoint 2016 farm and they could work well. In addition, if you don't use some features anymore, you can remove it from the SharePoint 2013 farm, then upgrade it again.
    PowerShell script to find missing features in the SharePoint
    Test-SPContentDatabase returns missing features

    4.MissingSetupfile
    Here’s a reference for you:
    Fix MissingSetupFile error of Test-SPContentDatabase in SharePoint migration

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sharath Kumar Aluri 3,071 Reputation points
    2020-11-10T22:18:22.867+00:00

    It seems, The source SharePoint 2013 environment sites contains references to some of the Feature files and those features are not installed in the target SharePoint 2016 Farm. Install & Deploy all solutions from the source farm to the destination farm. Your organization may have built & deployed several customization such as 3rd party products (such as bamboo solutions), custom WSP solutions, site definitions, Features, event receivers, Web Parts, user controls, etc. in the SharePoint 2013 environment and you have to install and deploy all these binaries & solutions to your destination SharePoint 2016 environment prior testing content databases for upgrade.

    It seems you are also missing the language pack which is in the source try to install the language pack in 2016 farm as well.

    Below article will help you to deploy and install custom solutions:

    https://www.sharepointdiary.com/2016/01/fix-missingsetupfile-error-test-spcontentdatabase-in-sharepoint-migration.html

    Thanks & Regards,

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.