1

I am migrating my databases to my new server and encounter this error when trying to attach. "This content database has a schema version which is not supported in this farm."

How do I go about migrating the DB's if I am getting this error.enter image description here

  • Which SharePoint version is configured in new server? Also mention the CUs you have installed on the server? – Dikesh Gandhi Nov 7 '16 at 5:04
  • Ive gone from 2013 to 2016 – B.O'Brien Nov 7 '16 at 5:29
  • SharePoint 2013 server should be SP1 or higher version. This link may help you.: technet.microsoft.com/en-us/library/… – Dikesh Gandhi Nov 7 '16 at 5:51
  • 1
    @DikeshGandhi Never ever use the Farm Configuration Wizard. You need to configure service applications manually to control the process in good fashion. "For instance, running the Farm Configuration Wizard will create a series of content and service application databases. It is unlikely that the names of these databases will meet the naming convention requirements in your organization because SharePoint uses default database names that include a globally unique identifier (GUID) suffix." #Exam 70-339 book ref – Benny Skogberg Nov 7 '16 at 8:45
  • 1
    Apology....I was asking about SharePoint Product configuration wizard. Thanks @BennySkogberg for correction. – Dikesh Gandhi Nov 7 '16 at 8:52
1

At first you run Test-SPContentDatabase to see if you're missing fetures or site definitions. If you do, you need to install the solutions and site definitions that are missing.

Test-SPContentDatabase -name "WSS_Content" -webapplication http://sitename -ServerInstance "SQL2"

When you have a successful run of Test-SPContentDatabase, you run Upgrade-SPContentDatabase, which will migrate the database schema of your content database to the 2016 farm schema.

Upgrade-SPContentDatabase WSS_Content

When your database is upgraded, mount it using the cmdlet Mount-SPContentDatabase.

0

This issue occurs when the build number of your destination farm is not identical (lower) to the build number of the source farm.

So to solve this issue,before you take a backup of content database from source farm , you should match the Configuration database version of destination farm to be the same as the source farm by following the mentioned steps below:

  • Get the build number of your source and destination farm ,
  • Check which farm has a higher build number , and install it to the lower build number farm.
  • Now make sure that the build number at the source and destination farm is identical.
  • Get a backup from source , attach it to the destination , mount it to the destination . via PowerShell
Mount-SPContentDatabase "<ContentDb>" -DatabaseServer "<DbServer>" -WebApplication http://SiteName

I wrote about this issue in more details at This content database has a schema version which is not supported in this farm

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.