Share via


There is a compatibility range mismatch between the Web server and database

Question

Saturday, May 17, 2014 1:06 PM

HI,

Taken backup form production environment through TSM backup utility and restore same db on UAT environment by TSM Utility, after restore got below issue, past i had done many time but working fine this time it’s not working. Production environment have SP2010 and sql server 2008 ,UAT have same thing also.

Server Error in '/' Application.

There is a

compatibility range mismatch between the Web server and database "Portal_Contain", and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.

**Description: **An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 
**Exception Details: **Microsoft.SharePoint.Upgrade.SPUpgradeCompatibilityException: There is a compatibility range mismatch between the Web server and database "Portal_Contain", and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.
Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

 

[SPUpgradeCompatibilityException: There is a compatibility range mismatch between the Web server and database "Portal_Contain", and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.]

   Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.ValidateBackwardsCompatibility() +542

   Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request) +63

   Microsoft.SharePoint.SPWeb.InitializeSPRequest() +258

   Microsoft.SharePoint.WebControls.SPControl.EnsureSPWebRequest(SPWeb web) +365

   Microsoft.SharePoint.WebControls.SPControl.SPWebEnsureSPControl(HttpContext context) +520

   Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.GetContextWeb(HttpContext context) +27

   Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PostResolveRequestCacheHandler(Object oSender, EventArgs ea) +918

   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80

   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +171

 

Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

| | Twitter

All replies (13)

Sunday, May 18, 2014 8:35 AM ✅Answered | 7 votes

Hi 

Problem has been fixed by below command:

PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures 

Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

| | Twitter


Saturday, May 17, 2014 2:29 PM | 1 vote

Please check SharePoint content database version on Production farm using below SQL query

Run the below query against the content database

SELECT * FROM DBO.VERSIONS

Then check the same on SharePoint Configuration database of UAT Farm.

If Production is on higher SharePoint version then UAT then you will face such issues and if Production is on lower version than UAT it should work fine but still if you are facing issues then run the following powershell cmdlet and upgrade the content database:

Note:- You can bring content databases from a farm which is on lower version to a farm which is on higher version. While attaching lower version content database to a farm which is on higher version SharePoint will upgrade the database. But if you are attaching a database which is on higher version to a farm which is on lower version then it will not work.

Upgrade-SPContentDatabase

Referrence: http://technet.microsoft.com/en-us/library/ff607813(v=office.15).aspx

Please ensure that you mark a question as Answered once you receive a satisfactory response.


Saturday, May 17, 2014 3:56 PM

Hi Bhavik,

Version i will check tomaroo,

But when i try to run  and prompt come Y for Yes to all,when put Y

Upgrade-SPContentDatabase

Some message come like  you can not upgrade.

Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

| | Twitter


Saturday, May 17, 2014 6:57 PM

Please share the database, farm version of both Production and UAT SharePoint Farm. Also share the error message you got while running the Upgrade-SPContentDatabase cmdlet.

Kind regards,

Bhavik Jain

Sr. Software Engineer – SharePoint Administration


Sunday, May 18, 2014 5:52 AM

Hi Bhavik,

UAT Portal_Contain DB version given below:

Version ID Version id
00000000-0000-0000-0000-000000000000 12.0.0.4518 1
00000000-0000-0000-0000-000000000000 12.0.0.6219 3
00000000-0000-0000-0000-000000000000 12.0.0.6327 4
00000000-0000-0000-0000-000000000000 12.0.0.6421 5
00000000-0000-0000-0000-000000000000 12.0.0.6510 6
00000000-0000-0000-0000-000000000000 12.0.0.6514 7
00000000-0000-0000-0000-000000000000 14.0.6123.5006 9
1A707EF5-45B2-4235-9327-021E5F9B8BB0 4.1.6.0 8
6333368D-85F0-4EF5-8241-5252B12B2E50 4.1.18.0 2

Production Version given below:

00000000-0000-0000-0000-000000000000 12.0.0.4518
00000000-0000-0000-0000-000000000000 12.0.0.6219
00000000-0000-0000-0000-000000000000 12.0.0.6327
00000000-0000-0000-0000-000000000000 12.0.0.6421
00000000-0000-0000-0000-000000000000 12.0.0.6510
00000000-0000-0000-0000-000000000000 12.0.0.6514
00000000-0000-0000-0000-000000000000 14.0.6123.5006
1A707EF5-45B2-4235-9327-021E5F9B8BB0 4.1.6.0
6333368D-85F0-4EF5-8241-5252B12B2E50 4.1.18.0

I have matched both are the exact same.

Run the below command on App server:

Upgrade-SPContentDatabase

cmdlet Upgrade-SPContentDatabase at command pipeline position 1
Supply values for the following parameters:
Identity: Portal_Contain

Confirm
Are you sure you want to perform this action?
Performing operation "Upgrade-SPContentDatabase" on Target "Portal_Contain".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help
(default is "Y"):y
WARNING: Database [SPContentDatabase Name=Portal_Contain] cannot be upgraded.

Kindly suggest 

Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

| | Twitter


Sunday, May 18, 2014 7:21 AM

Also i have tried to run psconf command but still issue and command has failed

 psconfig -cmd upgrade -inplace b2b -wait
SharePoint Products Configuration Wizard version 14.0.6009.1000. Copyright (C) M
icrosoft Corporation 2010. All rights reserved.

Performing configuration task 1 of 4
Initializing SharePoint Products upgrade...

Waiting to get a lock to upgrade the farm.

Successfully initialized SharePoint Products upgrade.

Performing configuration task 2 of 4
Initiating the upgrade sequence...

Successfully initiated the upgrade sequence.

Performing configuration task 3 of 4
Upgrading SharePoint Products...

100.00%
Failed to upgrade SharePoint Products.

An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.
  Additional exception information: Upgrade completed with errors.  Review the u
pgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Se
rver Extensions\14\LOGS\Upgrade-20140518-093850-151.log.  The number of errors a
nd warnings is listed at the end of the upgrade log file.

Total number of configuration settings run: 3
Total number of successful configuration settings: 2
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products.
Configuration of SharePoint Products failed.  Configuration must be performed be
fore you use SharePoint Products.  For further details, see the diagnostic log l
ocated at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\1
4\LOGS\PSCDiagnostics_5_18_2014_9_38_43_990_681414127.log and the application ev
ent log.

Log details:

[PSCONFIG] [SPUpgradeSession] [ERROR] [5/18/2014 9:39:27 AM]: Cannot upgrade [SPContentDatabase Name=Portal_Contain].

[PSCONFIG] [SPUpgradeSession] [ERROR] [5/18/2014 9:39:27 AM]: Cannot upgrade [SPContentDatabase Name=Portal_Contain].

[PSCONFIG] [SPContentDatabaseSequence] [ERROR] [5/18/2014 9:39:27 AM]: Upgrade object too new (build version = 14.0.6123.5006, schema version = 4.1.18.0). Current server (build version = 14.0.6123.5000, schema version = 4.1.18.0).

[PSCONFIG] [SPContentDatabaseSequence] [ERROR] [5/18/2014 9:39:27 AM]: Upgrade object too new (build version = 14.0.6123.5006, schema version = 4.1.18.0). Current server (build version = 14.0.6123.5000, schema version = 4.1.18.0).

[PSCONFIG] [SPUpgradeSession] [ERROR] [5/18/2014 9:39:27 AM]: Cannot upgrade [SPContentDatabase Name=Portal_Contain].

[PSCONFIG] [SPContentDatabaseSequence] [ERROR] [5/18/2014 9:39:27 AM]: Upgrade object too new (build version = 14.0.6123.5006, schema version = 4.1.18.0). Current server (build version = 14.0.6123.5000, schema version = 4.1.18.0).

Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

| | Twitter


Wednesday, March 11, 2015 11:51 PM

Hi...do we need to run this command on the database server?


Friday, May 29, 2015 11:17 AM

Thanks....

It's work for me.


Thursday, June 30, 2016 1:25 PM

Hi

Verify if the content databases have the original name and verify the second last Cumulative Update installed and you can use PSConfig.exe -cmd upgrade -InPlace b2b -Force.

EAGM


Monday, September 26, 2016 2:00 PM

Hi Hasan,

I am getting the same error. Is there any update what should we have to do to overcome this error. 

10.00% Failed to upgrade SharePoint Products.

Total number of configuration settings run: 5
Total number of successful configuration settings: 4
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products.
Configuration of SharePoint Products failed.

In LOG File :

Entering function StringResourceManager.GetResourceString
09/26/2016 15:40:53  1  INF              Resource id to be retrieved is TotalTasksFailed for language English (United States)
09/26/2016 15:40:53  1  INF              Resource retrieved id TotalTasksFailed is Total number of unsuccessful configuration settings: {0}
09/26/2016 15:40:53  1  INF            Leaving function StringResourceManager.GetResourceString

@ ALL - Please suggest something.

Thanks in advance

/Shrikant


Sunday, October 2, 2016 5:04 AM

Sreepta

Not on DB server.

run on application and WFE servers.

Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

| | Twitter


Sunday, October 2, 2016 5:06 AM

Hi SHrikanKindly ,

Can you share full log details.

Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS

| | Twitter


Tuesday, May 16, 2017 11:24 AM

Dear Concern,

i am facing the same problem that has been described at first. I am running sharepoint server 2013 with sql 2014 in win server 2012 R2. i cannot do "recover unattached database". what should i do now? on of my opinion is: if i use sharepoint 2013 with sql 2008; will it be solved problem?

plz suggest accordingly..