Critical database " SharePoint_Config" on SQL Server Instance is not empty and does not match current database schema
After installing our SharePoint 2013 Farm with March 2013 PU, we are facing some serious issues. When checking the SharePoint log files; Can not connect to configuration database due to compatibility issue: Microsoft.SharePoint.Upgrade.SPUpgradeCompatibilityException: SharePoint object [SPConfigurationDatabase] is in an unsupported state, and could not be used by the current farm. powershell (0x4A08) 0x3A8C SharePoint Foundation Upgrade SPConfigurationDatabaseSequence ajyxu ERROR Upgrade object too new (build version = 15.0.4481.1005, schema version = Current server (build version = 15.0.4420.1017, schema version = 00000000-0000-0000-0000-000000000000 05/13/2013 07:00:09.81 powershell (0x4A08) 0x3A8C SharePoint Foundation Upgrade SPUpgradeSession ajxmu DEBUG Skip [SPConfigurationDatabase] NeedsUpgrade. 00000000-0000-0000-0000-000000000000 When you check Central Administration, Upgrade and Migration, Review database status, the configuration database : No action required When checking the Upgrade status, I can see 5 out of 6 servers have succeeded to upgrade, one is not, but when running the config wizard on that box, it does show: completed successfully
May 13th, 2013 2:57am

Hi Jan, I think the SharePoint Versions is mismatched. So the Schema version also differ from one version to another version. Check the SharePoint Version and upgrade accordingly. SharePoint 2013 Build Numbers ---------- Vadivelu B Life with SharePoint
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2013 3:27am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics