KB2160841 or KB2416472 brakes WSS 3.0 SP2
We just ptched our WSS 3.0 SP2 server (only updates KB2160841 and KB2416472) and all sites stopped working: The schema version (3.1.8.0) of the database WSS_AdminContent on <MYSERVER> is not consistent with the expected database schema version (3.1.11.0) on <MYSERVER>. Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match. What happened and how do we fix it?
October 15th, 2010 8:49am

i think it's a database issue, when you install the patch sp2, please make sure yourself upgrade your database version.SharePoint Gardener in China
Free Windows Admin Tool Kit Click here and download it now
October 15th, 2010 9:05am

i googled this issue, someone has the same problem with you. this is the answer: Since you have 10 days of changes, you should try the following.... However, I would probably uninstall SharePoint perform a slipstream Installation rebuild the farm, restore the SSP and then attach the Content dbs I needed to upgrade. 1. Backup All Dbs 2. Run (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe) 3. Remove the content Dbs run STSADM.EXE – o deletecontentdb for each Web Applications (MySites, ShareServices, CentralAdmin, Portal) and any additional Content Dbs 4. Run PSCONFIG.EXE - cmd upgrade - inplace b2b - wait or SharePoint Products and Technologies Configuration Wizard 5. Add the content Dbs to the Web Applications run STSADM.EXE – o addcontentdb Note : Always backup the DBs prior to installing any of the Cumulative Updates or Service Packs. http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/ec405c4f-d4a5-497e-8731-4f9c06a1a65a SharePoint Gardener in China
October 15th, 2010 9:07am

Try this one, it will fix your problem stsadm -o upgrade -inplace -url (central admin site Url). hope this help thanks -wsSharePoint administrator, MCTS,MCITP
Free Windows Admin Tool Kit Click here and download it now
October 15th, 2010 9:11am

This is how we fixed it: http://support.microsoft.com/?kbid=2345304.
October 15th, 2010 6:44pm

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

Other recent topics Other recent topics