The Infrastructure Update failed a number of times and left the databases inaccessible to the SharePoint webs they belong to. The database schema update had not completed but the Configuration Wizard was not used to repair the problem. The contractors made the databases available again by manually changing the schema number in the database. They don't remember what they did to the database.1) A SQL query shows that our content databases have a Version number of 12.0.0.6219 (SP1).2) The SharePoint_Config database is at 12.0.0 6318 (Infrastruct. Up.). 3) A spot check of important files shows that the Infrastructure Upgrade files are installed. 4) Central Admin -> Operations -> Servers in Farm shows a Version of 12.0.0.6318 (Infrastruct. Up.). 5) Site Settings -> Version shows 12.0.0.6219 (SP1).6) When I try to use STSADM it reports, "The server administration programs and the Windows SharePoint Services Web applications on the Web server are not compatible. Ensure that the administration program is the same version as the Web application.7) I can do a backup using SharePoint Designer but when I try to restore to an empty web it fails part way through with the following error, "Error occurred while importing the web <web address> @bRetainObjectIdentity is not a parameter for procedure proc_AddNonListViewFormWebPartForUrl." Questions:1) I want to Repair the Infrastructure Update. Can this happen if the schema number has been edited and may be incorrect? 2) How can I verify which schema is actually imposed on the databases, other than listing the version number? 3) Would the SP2 install fail with this discrepancy?

> The contractors made the databases available again by manually changing the schema number in the database. This (manually changing the database) is an absolute No No and you should immediately fire the contractors and never use them again.You will now never get any support from Microsoft on anything to do with your SharePoint system (unless you go back to a backup done before the database was manually changed).In fact, why don't you go back to the state before you did the Upgrade? FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com Complete Book Lists (incl. foreign language) on each site.

Mike: As is sometimes the case, we cannot go back to the backup as it happened in November. However, I am trying to find a solution today. Since the system creates new content databases correctly with the right version number I am looking dividing the current system up onto new webs with fresh content databases. I may do this in place or on a fresh built server. Do you or the others have any advice? Thanks, KC