LiinaaS on Thu, 01 Sep 2016 07:43:02
I am current using SharePoint Foundation 2013 and I wish to upgrade to SharePoint Server 2013. I have taken a SQL database backup of SharePoint Foundation 2013 and did a restore on a new database. when trying to add a Content Database from Manage Content Database but I am getting the error message 'This content database has a schema version which is not supported in this farm'. Can you please advise how to perform the upgrade?
stevelane85 on Thu, 01 Sep 2016 09:18:00
Make sure SQL SERVER is up and the instance you try to connect is running and your system Firewall should not block SQL Server port.
Also refer to below informative resources might helps you to get in more detailed to resolve this issue:
This content database has a schema version which is not supported in this farm: https://blog.devoworx.net/2014/12/05/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: This content database has a schema version which is not supported in this farm.
mohit.goyal on Thu, 01 Sep 2016 09:46:40
Source SP farm and destination SP farm, both should having same build numbers (they should have same cumulative updates installed) for this to work. Please check the build version and correct the same.
To get build version, use this command: (Get-SPFarm).buildversion
Rahul_Dagar on Thu, 01 Sep 2016 10:41:13
Agreed with Mohit comments
Check below URL for step by step instruction to check build number
Shane Young MVP on Thu, 01 Sep 2016 12:34:43
They don't have to be the same build number exactly. Ideally Server would be a later build than foundation.
The key is if they are not the same build then you have to add the database using PowerShell not Central Admin. Follow these instructions for mount-spcontentdatabase.
If the database is too old then you will have to upgrade-spcontentdatabase.
LiinaaS on Fri, 02 Sep 2016 09:52:36
The SQL version for SharePoint Foundation on one server is SQL 2012. The SQL version for SharePoint Server on another server is SQL 2014. After running the command prompt for the build number on SharePoint Server product, the version is 15.0.4420.1017 and that of SharePoint Foundation is 15.0.4833.1000. I have downloaded the latest release for August 2016 to apply on both SharePoint Foundation and Server. When running the ubersrv2013-kb3115450-fullfile-x64-glb.exe on SharePoint Server, I am getting the error message 'The expected version of the product was not found on the system'. Does the version of SharePoint Server show that SP1 has been installed? How to know whether SP1 has been installed. Please advise how to fix same.
mohit.goyal on Fri, 02 Sep 2016 10:06:21
If SP server build is 15.0.4420.1017, it should already have SP1 installed. Run get-spproduct -local and then try to install binaries again. You can also try to clear configuration cache and see if that helps. If this does not help too, run product bypass check against exe file like this:
LiinaaS on Sat, 03 Sep 2016 14:33:22
From my SharePoint Server, I have applied the 'officeserversp2013-kb2880552-fullfile-x64-en-us.exe'. I reboot my server.
But now when launching 'ubersrv2013-kb3115450-fullfile-x64-glb.exe', I am getting error message 'The installation of this package failed'. Can you please tell me what I shall do next? How do I run the Package Bypass detection?
Also, I have downloaded the 'ubersrv_1.cab' and after extracting it, there are lots of installer in there. How do I proceed?
Shane Young MVP on Sat, 03 Sep 2016 14:51:25
Watch this video.
It will show you how to install the CU. The problem is you don't extract the cab. You put the Exe and the two cabs in the same folder and then run the EXE. It will do all of the work.
In the video I talk through all of that and show you a script that makes the CU installer MUCH faster.
mohit.goyal on Sat, 03 Sep 2016 15:03:31
Agree with Shane. You need to put all 3 downloaded files in same folder to install CU.
LiinaaS on Mon, 05 Sep 2016 10:14:45
I was able to perform the installation for the SharePoint server. Thank you all :)