I recently ran in to som trouble, where my Content af admin database had a newer version than the SharePoint install.

The scenario:

You are planning to update your SharePoint Foundation 2010. First off, you take a VHD-copy of the SharePoint server and the SQL server, running the enviroment.

The update then fails and you decide to revert to the VHD-copies, you’ve made.

The SharePoint-VHD works just fine. But when you turn to the SQL-VHD, you discover that there is a AVHD-file, that the HyperVisor diden’t register and therefore you can’t revert to your original SQL-VHD. Unfortunately, you can’t turn back to the updated (but failed) SharePointVHD, because you allready replaced that VHD with you original copy. Now you are facing a problem. Your Database and SharePoint version are now different and you get errors in the SharePoint Health page.

When you try to run the PSConfig.exe command you get an error in the log saying: “Upgrade object too new”


Install the SharePoint update once again and run the PSConfig.exe -cmd upgrade -inplace b2b -force
command and your back to having a SharePoint with errors, but at least your databases are reconized and functions properly.


Allways run the PSConfig command from: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14BIN