Recently, i tried to install Sharepoint Services 3.0 SP2 & Sharepoint Server 2007 SP2. Sharepoint Services 3.0 sp2 install failed. I got this error: Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: Topology Event ID: 5617 Date: 8/20/2010 Time: 4:02:03 PM User: N/A Computer: webserver Description: The schema version (3.0.149.0) of the database dbname on dbserver is not consistent with the expected database schema version (3.1.8.0) on websesrver. 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. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I then tried the following: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>psco nfig -cmd upgrade -inplace b2b -wait -force SharePoint Products and Technologies Configuration Wizard version 12.0.6413.1000 Copyright (C) Microsoft Corporation 2005. All rights reserved. Performing configuration task 1 of 4 Initializing SharePoint Products and Technologies upgrade... Failed to initialize SharePoint Products and Technologies upgrade. An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfig urationTaskException was thrown. Additional exception information: The initiali ze command is invalid or a failure has been encountered. Unable to upgrade SharePoint Products and Technologies because an upgrade is alr eady in progress. Upgrade progress can be monitored using the Central Administr ation Web Application or by monitoring the upgrade log on server. Total number of configuration settings run: 1 Total number of successful configuration settings: 0 Total number of unsuccessful configuration settings: 3 Successfully stopped the configuration of SharePoint Products and Technologies. Configuration of SharePoint Products and Technologies failed. Configuration mus t be performed before you use SharePoint Products and Technologies. For further details, see the diagnostic log located at D:\SharePointLogs\PSCDiagnostics_8_2 0_2010_18_44_0_785_352064456.log and the application event log. I was given this advice: "Disconnect the dbs from the WebApp using the stsadm -o deletecontentdbs, then complete the upgrade by running psconfig –cmd upgrade –inplace b2b -wait. if you need to list the dbs first run stsadm -o enumcontentdbs... Once the the Uprade is complete reattach the DBs using stsadm -o addcontentdbs and the dbs will be upgraded to the new schema..." I disconnected the databases and the upgrade completed successfully, but now when I try to reconnect the databases using the addcontentdb command I get the following errors: Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: Database Event ID: 3759 Date: 8/20/2010 Time: 7:34:49 PM User: N/A Computer: webserver Description: Database 'database' on SQL Server instance 'dbserver' is not empty and does not match current database schema. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. and: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa dm -o addcontentdb -url siteurl -databasename dbname dbname on dbserver contains user-defined schema. Databases must be empty before they can be used. Delete all of the tables, stored procedures and other objects or use a different database. Please, I am not finding anything on how to fix this and need to try to get it running by monday. Thanks ahead of time.Christopher Webb http://christophermichaelwebb.com

Try To add content new Empty content DB and restore the database from SQL to that new empty DB

Hi, I am also facing the same problem, while installing the WSS 3.0 sp2 (x64-bit) on my SharePoint server 2007 i have followed the following steps to trouble shoot and overcome this issue, but i am unable to fix the problem. http://social.technet.microsoft.com/Forums/en/sharepointadmin/thread/aebee008-89ca-4dcc-8bfb-243a9d99a363 My logs are here. While using the “psconfig - cmd upgrade -inplace b2b –force” 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.PostSetupConfiguration.PostSetupConfig urationTaskException was thrown. Additional exception information: The upgrade command is invalid or a failure has been encountered. Failed to upgrade SharePoint Products and Technologies. 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 mus t be performed before you use SharePoint Products and Technologies. For further details, see the diagnostic log located at C:\Program Files\Common Files\Micros oft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_8_24_2010_0_47_26_654_20 81822617.log and the application event log. The System Evet IDs are: Log Name: Application Source: SharePoint Products and Technologies Configuration Wizard Date: 8/24/2010 12:28:18 AM Event ID: 104 Task Category: None Level: Error Keywords: Classic User: N/A Computer: sharepoint.test.domain.com Description: Failed to upgrade SharePoint Products and Technologies. 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: 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. Microsoft.SharePoint.Upgrade.SPUpgradeException: 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. at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSession(IUpgradable root, Boolean bRecursive) at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask() Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="SharePoint Products and Technologies Configuration Wizard" /> <EventID Qualifiers="0">104</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-08-24T07:28:18.000Z" /> <EventRecordID>734986</EventRecordID> <Channel>Application</Channel> <Computer>sharepoint.test.domain.com</Computer> <Security /> </System> <EventData> <Data>Failed to upgrade SharePoint Products and Technologies. 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: 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. Microsoft.SharePoint.Upgrade.SPUpgradeException: 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. at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSession(IUpgradable root, Boolean bRecursive) at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()</Data> </EventData> </Event> Any Help greatly appreciated.

Hi suresh, you will find the error under the log files "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\" you will find more information there, most probably from SSP check and feed me back

Mina Fouad, Thanks for your mail. I have resolved the issue with help of diagonistic log and Upgrade log. The problem was, one of the web application and it's content DBs does not have the permission for the server account hence i was not able to install and update the WSS 3.0 SP2. I have added my service account into errored (Access Denied) DBs admin group and tried, the configuration was successful. During the problem search i found similar problem has been posted one of the portal, which is quite intersting. If you have time please go through and sugest the answer if you have on you packet. http://www.windows-tech.info/6/1295b34aa5d8df7a.php (Reference Site with Similar Issue: http://sharepoint.microsoft.com/Blogs/fromthefield/Lists/Posts/Post.aspx?ID=39) Thanks lot for all your help and reply. Best Regards, Suresh G Visual Source Safe 2005

I tried that, it attached fine, but then Sharepoint wouldnt recognize after i did the restore.Christopher Webb http://christophermichaelwebb.com

I actually ended up calling MS support on this. Something I've never had to do before, but after going through all the forums I could find and trying multiple things, I had lost hope and I was on a serious time crunch. MS said that the only resolve would be to rebuild the config database, which essentially requires a reinstall of sharepoint. (Glad I called to be told I would still have to reinstall) Anyway, this is pretty straightforward, uninstall/reinstall, attach your content dbs, then apply all patches/SPs. The only problem we have is there is tons of custom templates and custom code on our site, so it had to be reapplied and just took forever, as we had kept poor track of what all was implemented on it. Anyway, all in all, as long as you dont have custom code, i think the reinstall was a simple fix. 2-4 hours, cause you gotta reconfig all the shared services and any other tweaked settings, but i mean, you'll have your content back up fairly quick.Christopher Webb http://christophermichaelwebb.com