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

Comments (12)

  1. Same error here.. but no solution.

    Worse in my case even the central admin site shows the damn 404 error.

    Sridhar B

    WinWire Technologies

  2. Hopefully, you had a backup of your Central Administration Content and Configuration databases.

    I haven’t seen any answers to that issue and do not know what triggers it unfortunately.

    Maxime

  3. usbusi says:

    The fix for me was to uninstall, in add/remove programs, Microsoft GroupBoard Workspace application template, then run the SharePoint Configuration Wizard.

    I found the solution while googling — apparently the same problem occurred with previous SharePoint 3.0 updates.

  4. roryschmitz says:

    I’m having the same problem and currently have an open support case with Microsoft.  I’ll have to check on the GroupBoard installed in my scenario.  However, I don’t remember it being listed.

    We (MS Engineer and I) haven’t had too good of luck thus far.  I was running WSS 3.0.  The SP1 upgrade somehow corrupted my DB (per MS Engineer) and had to restore from backup (Sym Backup Exec).  We are still struggling.  We are in the process of reinstalling WSS and create a new farm, then attach the content DB from the restore.

    Downtime thus far:  1 week…complete farm restore from Backup Exec failed also…

    So far, I’m not too impressed with this Service Pack.  Serves me right for not following correct installation instructions I guess…

  5. In my case (back then), I didn’t have the GroupBoard Workspace application template installed, in fact, we didn’t have any but the out of the box templates.  Though I’m glad it worked out for you!

    My case was closer to the previous comment on SP1 (albeit I was installing 941422).  I was following the correct steps to install a hotfix and it was in a personal single farm Virtual Machine so it’s easy to follow.

    What step didn’t you follow?

  6. roryschmitz says:

    Update for my case:

    I was finally able to restore our DB from Dec 25th (last good backup) to a newly created WSS 3.0 server with same WSS hotfixes as old server, pre-sp1.

    I then simply created a new web application and attached the existing DB from the restore.  It created a new top site URL but all the sub-sites are there and intact with same permissions, etc.

    This only left me with having to enter in alternate mapping and any additional templates, etc from the old server.  

  7. Glad you were able to put it back up with minimal impact (afterall, beside the downtime).  Very good job on your end.

    I will try to follow-up on the issue internally to see if they can reproduce it and fix the problem.

    Maxime

  8. roryschmitz says:

    Thanks.  I’m still struggling with the application templates I’ve been using (help desk, groupboard, etc), but I’m still playing with how to recover some of those.  If there’s any info for my case, I’m open to any links, etc.

    Rory

  9. I saw this command in the SP1 document that should be run after a failed installation :

    psconfig -cmd configdb -connect -server <SQLServerName> -database SharePoint_Config_<dbname> -user <domainusername> -password <password> -cmd helpcollections -installall -cmd secureresources -cmd services -install -cmd installfeatures -cmd applicationcontent –install

    Since I don’t have the issue, I didn’t test it but it would be worth a try if you receive this error again.

    Maxime

  10. ntotten says:

    I had this error upgrading from 12.0.0.4518 to 6300. I uninstalled groupboard and reran the sp config wizard and the upgrade completed successfully.

  11. Mark says:

    Yes – unistalling the  Microsoft GroupBoard Workspace application template worked for us.

Skip to main content