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

When I have tried to restore a SharePoint Content Database Backup to another farm that has been restored successfully.

But unfortunately, 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

errorcontentdb

Scenario

I tried to use the database- attach upgrade method to migrate a web application from one farm to another.

During mounting the Content Database to a Web Application in the destination farm by doing the following steps:

  • Central Administration > Manage content database.

managecontentdatabase

  • Click on Add a content database.

addcontentDB

  • Add the name of the Restored Content Database.

addcontentdatabase

I got this error:

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

 

errorcontentdb

Note: You can also use a SharePoint Management Shell to Mount the Content Database to a Web Application by using the following Cmdlet.

Mount-SPContentDatabase "<ContentDb>"
-DatabaseServer "<DbServer>"
-WebApplication http://SiteName

Cause

In the database attach upgrade methodThe destination farm build number must be as same as or higher than the source farm build number to avoid this error.

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

Solution

To solve this issue, before taking a database backup from the source farm, you should patch the destination farm with current installed CU/Service Pack in the source farm to match the build version of destination farm with the build version of the source farm.

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

Steps

In source farm,
  • Open Central Administration > System Settings > Manage Servers In This Farm.

System Settings

  • Below Farm Information > Check the Configuration database version.

Server in farm - 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.

Check also the alternatives to get the farm build number.

Versions Content Database Table

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 is SharePoint Server 2013 RTM that is lower than the source farm build number (SP1). Therefore, I should download and install the Service Pack 1 in destination farm.

Note:

  • You can’t rollback the installed CU. so it’s heavily recommended to perform a full farm backup before patching your farm with a new update.
    • At least you need to perfomr back  up for
      • Databases
      • Your customization.
      • back up farm configuration by running Backup-SPFarm -ConfigurationOnly
  • If you experience difficulty in implementation of the previous steps. you can only install the latest CU on both farms to become the same in Configuration database version (build farm).
  • It’s not recommended to install the latest CU in production farm until tested in Dev/Staging farm.

Unsupported Workaround

There is a simple workaround that is faster than the previous solution but it is unsupported by Microsoft and you will lose the Microsoft support! (I advise to apply this workaround only in Dev environment if it’s heavily required)

In source farm,
  • Open SQL Server Management Studio.
  • Open the Content Database > Versions Table > Copy the Version field value that it’s “VersionId” is not equal 00000-000. In this example It’s 4.0.8.0 & 4.1.1.0

  • Or from Central Administration > Upgrade and Migration > Review Database Status.

Upgrade and Migration - Review Database Status.png

  • Manage Database Upgrade Status.

Manage Databases Upgrade Status

  • Get the database Schema Versions.

Database Schema Versions

In destination farm,
  • Go back to open the Restored Content Database > Open Versions Table in Edit Mode.

restoredDBVersion

  •  Replace the “Version” field value from Source Content Database to the corresponding version field value in the Restored Content Database. (In my case I will 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.

addcontentDBSucsess


See also
Advertisements

6 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!!

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s