Can anyone share their Successful Story in Upgrading WSS 3.0 SP2 and MOSS 2007 SP2 in Production environment?
Hi All, Can anyone here share your story/ detailed step in Upgrading your WSS 3.0 and SharePoint 2007 SP1 Enviroment into Service Pack 2 ? It seems to me that SP2 for any of those products could render the current environment useless. Any comments and thought please ? Thanks. /* Windows Infrastructure Support Engineer */
June 5th, 2009 1:29pm

>It seems to me that SP2 for any of those products could render the current environment useless. What do you base that statement on ?WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx
Free Windows Admin Tool Kit Click here and download it now
June 5th, 2009 1:32pm

Hi Mike, I've seen and even tried carefully to upgrade everything that i've got WSS 3.0 SP1 and MOSS 2007 SP1 in a single server and it was failed :-(, thus it rendered my environment useless./* Windows Infrastructure Support Engineer */
June 7th, 2009 1:34am

i install SP2 without comula Update and work very good in proudaction inviroment please can you tell us if you faceing problemshttp://www.waelk.com
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2009 10:09am

Hi wae, Please share your steps in installing it here, I've seen so many error tragedy in installing SP2 for both products and I've tried that as myself without any luck. Thanks./* Windows Infrastructure Support Engineer */
June 7th, 2009 6:01pm

Take a look at this....http://msmvps.com/blogs/shane/archive/2009/04/29/install-guide-sp2-for-sharepoint-wss-v3-and-moss-2007.aspxJohn SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2009 7:03pm

Hi Albert, Here is our official upgrading article for your information: Deploy software updates for Office SharePoint Server 2007 (http://technet.microsoft.com/en-us/library/cc263467.aspx) I followed the processes and upgrade all my test environments without issues. I understand there are many upgrading issues because of various SharePoint environments. If you need further assistance on your upgrading issues, could you please let me know the symptom of your issue? 1. The upgrade process failed at which step? What is the error message? 2. Is there error message logged in Event Viewer? 3. Is there any error message logged in upgrade.log, ULS logs and PSCDiagnostics logs Let me know the result if possible. -lambertLambert Qin | Microsoft Online Support Engineer How to ask a question in the forum (http://support.microsoft.com/kb/555375) Posting is provided "AS IS" with no warranties, and confers no rights.
June 8th, 2009 5:34am

my steps was:1- dowinload sp22- backup my farm3- start install and follwing steps with installation wizard4- he ask me for some updates i dowinload it and installed and start install sp2 again5- finish and restart6- run installation and configrationas i remmber that is allhttp://www.waelk.com
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2009 11:40am

Hi Lambert, I'm having problem of "Server error: http://go.microsoft.com/fwlink?LinkID=96177 " after upgrading the WSS 3.0 SP2 the background of my server is a single server farm which is consist of Windows 2008 Standard SP1 MOSS 2007 SP1 Enterprise SQL 2008 SP1 Standard all in 64 bit environment what i did is that i upgraded SQL Server 2008 SP1 -> OK and then WSS 3.0 SP2 --> OK (wssv3sp2-kb953338-x64-fullfile-en-us.exe) but MOSS 2007 SP2 --> FAILED (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe) here is the following command that i tried but failed. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- C :\ Program Files \ Common Files \ Microsoft Shared \ Web Server Extensions \ 12 \ BIN > STSADM . EXE - o upgrade - inplace - forceupgrade - url http : //mossdev01 The specified SPContentDatabase Name = SharePoint_AdminContent_f632e5bf - cbd9 - 4d9f - a819 - 1811feb4f2b6 Parent = SPDatabaseServiceInstance Name = MOSSDB has been upgraded to a newer version of SharePoint . Please upgrade this SharePoint application server before attempting to access this object . ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- C :\ Program Files \ Common Files \ Microsoft Shared \ Web Server Extensions \ 12 \ BIN > PSCONFIG . EXE - 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 ... 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_f632e5bf - cbd9 - 4d9f - a819 - 1811feb4f2b6 Parent = SPDatabaseServiceIn stance Name = MOSSDB 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_5_27_2009_20_26_50_793_1641045907 . log and the application event log. ---------------------------------------------------------------------------------------------------------------------------------------------- and I've got the following Error logged in the EventViewer: Log Name: Application Source: Windows SharePoint Services 3 Date: 27/05/2009 7:24:39 PM Event ID: 5617 Task Category: Topology Level: Error Keywords: Classic User: N/A Computer: MOSSDEV01.domain.com Description: The schema version (3.1.3.0) of the database MySite_ContentDB on MOSSDEV01\MOSSDB is not consistent with the expected database schema version (3.1.8.0) on MOSSDEV01. 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. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows SharePoint Services 3" /> <EventID Qualifiers="0">5617</EventID> <Level>2</Level> <Task>807</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-05-27T09:24:39.000Z" /> <EventRecordID>216355</EventRecordID> <Channel>Application</Channel> <Computer>MOSSDEV01.domain.com</Computer> <Security /> </System> <EventData> <Data>The schema version (3.1.3.0) of the database MySite_ContentDB on MOSSDEV01\MOSSDB is not consistent with the expected database schema version (3.1.8.0) on MOSSDEV01. 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. </Data> </EventData> </Event>/* Windows Infrastructure Support Engineer */
June 8th, 2009 11:45am

sorry but your invironment is defferant than mei have win server 2003 updatedsql 2005 updatedand moss 2007 with sp2 all in 32 bithttp://www.waelk.com
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2009 11:58am

oh.. no wonder it's all went smoothly :-| but thanks any way in replying my thread./* Windows Infrastructure Support Engineer */
June 8th, 2009 11:59am

I've seen this issue before. Here's the fix I used -- http://blogs.microsoft.co.il/blogs/adlaim/archive/2007/10/26/the-schema-version-3-0-149-0-of-the-database-sps-content-db-on-moss.aspxThe method worked for me but it requires that you modify the tables in SQL which is not recommended!!!!!!!!!!!!!!!! It is really a minor change but do this at your own risk. If you decide to go this route make sure you back all your SP databases in SQL up.I wish their was a safer way to fix this issue but I wasn't able to find anything. Given that the fix came from a blog post from a Microsoft person I decided to take my chances. If you are concerned about this fix it might make sense to contact Microsoft Support.Just to reiterate: Modifying any of the SharePoint SQL databases is not supported by Microsoft!!!John SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2009 3:36pm

The Event 5617 showed the schema version of the databases were not match, I wonder if the SharePoint configuration cache stores the database schema version and causes the error. Please try to clear the SharePoint configuration caches and run SharePoint Products and Technologies Configuration Wizard again. To Clear SharePoint configuration caches, please follow the steps: 1. Stop Windows SharePoint Services Timer in Services. On the computer that is running Microsoft Office SharePoint Server 2007 and on which the Central Administration site is hosted, locate the configuration cache folder in %allusersprofile%\Application Data\Microsoft\SharePoint\Config\GUID In Windows Server 2008, the configuration cache is in the following location: %allusersprofile%\Microsoft\SharePoint\Config\GUID 2. Back up the Cache.ini file. 3. Delete all the XML configuration files in the GUID folder. 4. Edit the Cache.ini file. Change the content to 1, and then click Save the changes. 5. Start Windows SharePoint Services Timer in Services. More detailed step is in KB 939308 (http://support.microsoft.com/kb/939308) Let me know the result if possible. -lambertLambert Qin | Microsoft Online Support Engineer How to ask a question in the forum (http://support.microsoft.com/kb/555375) Posting is provided "AS IS" with no warranties, and confers no rights.
June 9th, 2009 1:23pm

Lambert-Read the link I posted in my reply. You can pop open the database and see where the issue is quite easily.John SharePoint911: SharePoint Consulting Blog: http://www.rossonmoss.com Twitter: JohnRossJr MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2009 11:30pm

Hi John, as per my knowledge, directly editing the MOSS DB in SQL Server is very risky thing to do. CMIIW/* Windows Infrastructure Support Engineer */
June 25th, 2009 1:58am

Hi, Even I have faced same issue during the SP 2 update. We have come to know that, There was a database orphaned link established between Database and wss. We had to deattached that perticular database. check out if you have any orphaned databsae or link available in your database.
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2010 5:38pm

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

Other recent topics Other recent topics