Error after KB941422 : The specified SPContentDatabase has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.

After running the KB941422 on my personal MOSS Virtual Machine, I was getting this error in the Upgrade.log :

The specified SPContentDatabase Name=SharePoint_AdminContent_a3efdc71-2455-4b12-8d44-6395d42c9070 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()

 

Running the setup (GUI) again would result in the same error.  My web sites and the SSP site were down, only the Admin was working.  I ran this command : psconfig -cmd upgrade -inplace b2b -wait -force  and got this in return :

SharePoint Products and Technologies Configuration Wizard version 12.0.6023.5000
Copyright (C) Microsoft Corporation 2005. All rights reserved.

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

Successfully initialized SharePoint Products and Technologies upgrade.

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

Failed to initiate the upgrade sequence.

An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.
Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_a3efdc71-2455-4b12-8d44-6395d42c9070 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.

Total number of configuration settings run: 2
Total number of successful configuration settings: 1
Total number of unsuccessful configuration settings: 2
Successfully stopped the configuration of SharePoint Products and Technologies.
Configuration of SharePoint Products and Technologies failed.  Configuration must be performed before you use SharePoint Products and Technologies.  For further details, see the diagnostic log located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_10_20_2007_7_19_48_307_615953129.log and the application event log.

The event log receives this ID 104 error :

Failed to initiate the upgrade sequence.
Failed to upgrade SharePoint Products and Technologies.  Further information regarding this failure can be found at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: The specified SPContentDatabase Name=SharePoint_AdminContent_a3efdc71-2455-4b12-8d44-6395d42c9070 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object. Microsoft.SharePoint.Upgrade.SPUpgradeException: The specified SPContentDatabase Name=SharePoint_AdminContent_a3efdc71-2455-4b12-8d44-6395d42c9070 Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
   at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_CanUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveCanUpgrade(Object o)
   at Microsoft.SharePoint.Upgrade.SPManager.NeedsUpgrade(Object o, Boolean bRecurse)
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_NeedsUpgrade()
   at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

and this 3759 error :

Database 'SharePoint_AdminContent_a3efdc71-2455-4b12-8d44-6395d42c9070' on SQL Server instance 'MOSS' is not empty and does not match current database schema

 

NOTE: THE PROCESS BELOW IS NOT A SUPPORTED SCENARIO. IF YOU HAVE THIS ERROR OR BEFORE TRYING THIS ON A PRODUCTION ENVIRONMENT, CALL MICROSOFT SUPPORT. I only used it on my personal VM (and because I couldn't roll it back). DO NOT ATTEMPT AND EXPECT TO BE SUPPORTED AFTERWARD. You have been warned :)

 

I installed the KB939077 hotfix (for MOSS) just in case it could save me ... but unfortunately, the hotfix installed correctly but I still had the same issue :(  So I opened up that SharePoint_AdminContent_Guid database and saw that there was a table called "Versions".  I opened that one up and had 4 rows :

00000000-0000-0000-0000-000000000000    12.0.0.4518    1    LITWAREINC\administrator    10/20/2007 1:41:48 AM    NULL    0    0    2   
00000000-0000-0000-0000-000000000000    12.0.0.6036    4    LITWAREINC\administrator    10/20/2007 1:41:48 AM    NULL    0    0    1   
6333368d-85f0-4ef5-8241-5252b12b2e50    3.0.150.0    2    LITWAREINC\administrator    10/20/2007 1:40:14 AM    NULL    0    0    2   
19a05f82-f6b1-4310-9d24-f753222841a3    3.0.1.0    3    LITWAREINC\administrator    4/4/2007 7:28:31 AM    NULL    0    0    2   

 

I updated the version of 12.0.0.6036 to 12.0.0.4518 and ran psconfig -cmd upgrade -inplace b2b -wait -force again ... and it ran further in (ouch, my SQL Server process was at 900 MB RAM alone and psconfig at 150 MB RAM for the duration of the upgrade ... my poor little VM!).  The table looked like this after :

00000000-0000-0000-0000-000000000000    12.0.0.4518    1    LITWAREINC\administrator    10/20/2007 12:03:31 PM    NULL    0    0    3   
00000000-0000-0000-0000-000000000000    12.0.0.4518    4    LITWAREINC\administrator    10/20/2007 12:03:31 PM    NULL    0    0    2   
00000000-0000-0000-0000-000000000000    12.0.0.6036    5    LITWAREINC\administrator    10/20/2007 12:03:31 PM    NULL    0    0    1   
6333368d-85f0-4ef5-8241-5252b12b2e50    3.0.150.0    2    LITWAREINC\administrator    10/20/2007 1:40:14 AM    NULL    0    0    2   
19a05f82-f6b1-4310-9d24-f753222841a3    3.0.1.0    3    LITWAREINC\administrator    4/4/2007 7:28:31 AM    NULL    0    0    2   

The results on screen were:

SharePoint Products and Technologies Configuration Wizard version 12.0.6023.5000
Copyright (C) Microsoft Corporation 2005. All rights reserved.

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

Successfully initialized SharePoint Products and Technologies 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 and Technologies...

Failed to upgrade SharePoint Products and Technologies.

An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.
Additional exception information: Upgrade completed with errors. Review the upgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log. The number of errors and 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 and Technologies.
Configuration of SharePoint Products and Technologies failed.  Configuration must be performed before you use SharePoint Products and Technologies.  For further details, see the diagnostic log located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_10_20_2007_8_1_40_659_1586950601.log and the application event log.

 

I opened up the log to see that I had 153 errors where it was opening up the AdminContent database now (contrary to the first test) but then was saying the same error later in on some other rows/tables (presumably) that a newer version was there.  Next step I did was to detach that database and run the command line again but obviously, that database must be running (I think you could get away with it if the database was for a web site).  So I'm stumped at this point, I am re-downloading the VM and accepting defeat (and because I have a deliverable!).  If anyone has this issue and found a fix, let me know!

 

NOTE AGAIN: THIS IS NOT A SUPPORTED SCENARIO. IF YOU HAVE THIS ERROR OR BEFORE TRYING THIS ON A PRODUCTION ENVIRONMENT, CALL MICROSOFT SUPPORT. I only used it on my personal VM (and because I couldn't roll it back). DO NOT ATTEMPT AND EXPECT TO BE SUPPORTED AFTERWARD. You have been warned :)

 

There's also a thread on the forums with this, http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2273145&SiteID=1, it helped look at the right places but we are still looking for a solution.

 

Maxime