This content database has a schema version which is not supported in this farm

This content database has a schema version which is not supported in this farm SharePoint 2016

In this post, we’re gonna solve This content database has a schema version which is not supported in this farm SharePoint 2016 and 2013.

This content database has a schema version which is not supported in this farm

You might also like to read Database running in compatibility range upgrade recommended


This content database has a schema version which is not supported in this farm SharePoint 2016

When I have tried to restore a SharePoint Content Database Backup to another farm that has been restored successfully. But when I tried to mount the restored Content Database to the Web Application in the destination farm, I got the below error:

This content database has a schema version which is not supported in this farm

This content database has a schema version which is not supported in this farm SharePoint 2016

Mount Content Database to SharePoint Web Application

Actually, I used the database- attach upgrade method to migrate a web application from one farm to another, and I tried to mount the Content Database to SharePoiny Web Application in the destination farm by doing the following steps:

Steps

  • Central Administration > Manage content database.
Manage SharePoint content database
  • Click on Add a content database.
addcontentDB
  • Add the name of the Restored Content Database.
add content database in SharePoint
  • Specifically at this step, when I clicked OK, I got this error “This content database has a schema version which is not supported in this farm
This content database has a schema version which is not supported in this farm SharePoint 2013

Mount Content Database to SharePoint Web Application Using PowerShell

I also tried to mount the SharePoint content database using PowerShell by running the “Mount-SPContentDatabase” command-line. But actually, it doesn’t help!

Mount-SPContentDatabase "ContentDB Name" -DatabaseServer "DBServer" -WebApplication http://SiteName

You might also like to check PowerShell Script: SharePoint Farm Scan Report


Why you got “This content database has a schema version which is not supported in this farm”?

The root cause of “This content database has a schema version which is not supported in this farm” is that the SOURCE SharePoint farm build number is HIGHER than or NOT the same as the DESTINATION SharePoint farm build number.

Therefore, when you use the SharePoint database attach upgrade methodyou should be aware of the destination farm build number must be as same as or higher than the source farm build number to avoid “This content database has a schema version which is not supported in this farm“.

Note: find farm patch level / latest cumulative update that has been installed on SharePoint farm

How to solve “This content database has a schema version which is not supported in this farm”?

To solve this issue “This content database has a schema version which is not supported in this farm“, before taking a database backup from the source farm, you must make sure that the SharePoint destination farm build number is NOT lower than the SharePoint source farm build number.

So that if the SharePoint destination farm build number is LOWER than the SharePoint source farm build number, you should patch the destination farm with at least the current installed CU/Service Pack in the source farm to match the build version in both farms.

Check SharePoint Farm Build Number

In source farm, you can get the SharePoint Farm Build Number by doing the following:

Steps
  • Open Central Administration > System Settings > Manage Servers In This Farm.
System Settings - Manage Servers in this farm
  • Below Farm Information > Check the Configuration database version.
SharePoint Configuration database version

Note: In some cases, this version number is not updated after applying the CU, so it is not considered a trusted version number. For more details check SharePoint patching demystified.

Get SharePoint Farm Build Number using PowerShell

You can also get the SharePoint Farm Build Number using PowerShell by doing the following:

  • Open SharePoint Management Shell as Administrator.
  • Run the below cmdlet to get the Get SharePoint Farm Build Number
(Get-SPFarm).BuildVersion
Get SharePoint Farm Build Number using PowerShell

You might also like to read How to get the farm build number.

Get SharePoint Farm Update Release Name

To get the corresponding release name of SharePoint farm farm build number, you should do the following:

Get SharePoint Farm Update Release Name

Again, In destination farm, Repeat the previous steps to get the corresponding CU release of the currently installed Configuration database version (Build Farm).

In my case, The corresponding release of destination build farm was the SharePoint Server 2013 RTM that is lower than the source farm build number (SP1). Therefore, I should download and install Service Pack 1 on the destination farm.

Note: If you are sure that the two farms have different build numbers, so you can also install (the latest CU update – 2 months) on both farms that will ensure that the two farms have identical build numbers.

SharePoint Patching Considerations

Before patching a SharePoint farm with a new update, you should be first aware of the following:

  • You can’t roll back the installed CU. so it’s strongly recommended to perform a full farm backup before patching your farm with a new update.
    • At least you need to perform a backup for the following:
      • Content Databases
      • Your customization.
      • Back up farm configuration by running Backup-SPFarm -ConfigurationOnly.
  • It’s not recommended to install the latest CU in the production farm until tested in Dev/Staging farm.
  • In SharePoint 2013 and SharePoint 2016 without high availability, the patching process requires downtime. so it’s preferred to apply the new update out of working hours.

Unsupported Workaround

There is a simple workaround for “This content database has a schema version which is not supported in this farm” issue that is faster than the previous solution but it is unsupported by Microsoft and you will lose Microsoft support! so it’s strongly recommended to only apply this workaround on DEV or learning environment.

Steps
  • In destination farm, Open SQL Server Management Studio.
  • Open any mounted Content Database > Versions Table.
  • Copy the Version field value where the “VersionId” is not equal 00000-000.
  • In this example It’s 4.0.8.0 & 4.1.1.0
Content database schema version
  • You can also get theses values from Central Administration.
  • Upgrade and Migration > Review Database Status.
SharePoint Upgrade and Migration
  • Manage Database Upgrade Status.
Manage Databases Upgrade Status
  • Get the database Schema Versions.
Get SharePoint content database schema versions
  • Go back to open the Restored Content Database from the source farm.
  • Open Versions Table in Edit Mode.
Get the content database schema versions
  • Replace the “Version” field value from the current mounted Content Database to the corresponding version field value in the Restored Content Database.
  • In my case, I should replace 4.2.9.0 with 4.1.1.0 &  4.1.7.0 with 4.0.8.0.
  • Go back to mount the content database that should be now mounted successfully and the “This content database has a schema version which is not supported in this farm” is gone!
add content database to web application

Conclusion

In conclusion, we have solved This content database has a schema version which is not supported in this farm by exploring the following:

Applies To
  • SharePoint 2016.
  • SharePoint 2013.
  • SharePoint 2010.
You might also like to rad
Have a Question?

If you have any related questions, please don’t hesitate to ask it at deBUG.to Community.

7 thoughts on “This content database has a schema version which is not supported in this farm”

  1. i am trying to restore my share point site that has been accidentally crashed,

    and i am having SQL server data base backup with me,

    namely

    WSS_Content

    WSS_Content_log

    WSS_Logging

    and while restoring WSS content database i am getting the same error,

    i have noticed the versions of old one is different with the new one

    VersionId Version

    1A707EF5-45B2-4235-9327-021E5F9B8BB0 4.1.7.0

    6333368D-85F0-4EF5-8241-5252B12B2E50 4.2.7.0

    but i am not able to set the value while i selected,

    please help on this!!

  2. Pingback: Failed to Provision site PWA : Failed to get schema version of Published database | Errors - Problems (SharePoint - ASP.Net - SQL ... etc)

Leave a Reply