SharePoint 2007: Updating MOSS Beta 2 to Beta 2 Technical Refresh (Beta 2TR)
Because the process for updating MOSS Beta 2 to the Beta 2TR might appear tricky to some, I have written the following step by step instructions for applying the update to an existing install.
For those looking to print these instructions off, I have created a PDF that you can download here. Since I realize sometimes it is easier to print such documentation off and read as you go through the steps.
Update: You can find the direct links to all TR Downloads on the Microsoft SharePoint Team weblog.
Anyhow…let’s get started!
Step 1: Confirm Appropriate Version of Microsoft Office SharePoint Server
Confirm the version of Microsoft Office SharePoint Server 2007 is the appropriate number (12.0.0.4017). This can be checked under the Site Settings panel of the Central Administration site or under the site settings of any standard site.
- Log into the SharePoint Central Administration
- From the Site Actions menu, select Site Settings
The version number is listed just below the mobile url.
Step 2: Stop the Search Service
The search service should be disabled on all servers within the server farm prior to installing the TR update. To disable the search service:
On each of the application servers:
- Select Start, Programs, Administrative Tools and then Services
- From the listing of services, select the Office SharePoint Search Service and select Stop the service.
Disabling the WSS Search Service
- Log into the SharePoint Central Administration
- Select the Operations tab
- From the Topology and Services section, select Services on Server
- From the list of running services, select the Stop action for Windows SharePoint Services Search
- Click OK on the popup window to continue.
Step 3: Uninstall Windows Workflow Foundation Build 2.2
- Click Start, Settings, Control Panel, and select Add or Remove Programs
- From the list of installed programs, select Windows Workflow Foundation and click the Remove button
- Select the Yes button from the pop-up window to confirm the removal request
Step 4: Install the .NET Framework 3.0
Download and install the .NET Framework 3.0 from the following location:
- Accept the End User License Agreement and click the Install button
- The installation process will commence and a message window will appear in bottom right of the screen. During this time, any required components for the installation will be downloaded. This process will take several minutes to complete. To view progress, select the balloon window.
- A message will appear once the setup has been completed successfully.
Step 5: Run the WSS Beta 2 Technical Refresh Update
- Run the WSS Beta 2 TR file.
- Accept the End User License Agreement and click the Continue button
- You will receive a warning that several key services will be stopped which will affect the availability of the service to others. Click the Yes button to continue.
- The files will then be extracted and installation of the update will continue. This operation will take several minutes to complete. When the operation has finished, a message window will appear advising that additional components will require updating.
- Click the OK button to continue.
- Another message window will appear advising that installation of the Beta 2 Technical Refresh for Windows SharePoint Services is complete.
Step 6: Run the MOSS Beta 2 Technical Refresh Update
- Run the MOSS Beta 2 TR Update
- Accept the End User License Agreement and click the Continue button
- You will receive a warning that several key services will be stopped as part of the operation. Click the Yes button to continue.
- The files will then be extracted and installation of the update will continue. This operation will take several minutes to complete. When completed, a message window will appear. Click the OK button to continue.
The SharePoint Configuration Wizard will be automatically started upon clicking the OK button from previous step. If you have installed language packs or are running Microsoft Office SharePoint Server in a standalone installation, cancel the wizard and complete Steps 7 and/or 8. Also if there are multiple servers within the environment, ensure that the updates are applied to each server.
Step 7: (Optional) Install Language Packs
If you are running any language packs on your server farm, you should now install the WSS language pack updates and then the MOSS language pack updates. This will require stopping the automatic running of the SharePoint Configuration Wizard. This operation can be restarted manually after the required components have been run.
Step 8: (Optional) Remove Registry Entries on Standalone Server
- If you are updating a standalone server, you will need to make some changes to the registry settings on the server. To do this select Start, Run and enter “regedit” and click the OK button.
- Browse to and delete the following registry nodes:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\Services\Microsoft.Office.Server.Search.Administration.SearchService
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\Services\Microsoft.SharePoint.Search.Administration.SPSearchService
Step 9: (Automatic) Run the SharePoint Configuration Wizard
1. Unless you had to complete steps 7 or 8, the SharePoint configuration wizard will run automatically after the completion of Step 6. To run the configuration wizard manually, select Start, then Programs, Administrative Tools and SharePoint Products and Technologies Configuration Wizard.
2. When the wizard begins, click the Next button.
3. A window will appear advising of the services that will be reset during the configuration process. Click the Yes button to continue.
4. You will receive a reminder warning to ensure that the update has been applied to all servers in the server farm. Click the OK button to continue.
5. This process will update all deployed sites to the Beta 2 Technical Refresh. You may be notified that the search service is not running. This is expected and will be restarted manually in an upcoming step. When the configuration wizard ends, you will receive a notification that the process has completed successfully. Click the Finish button.
Step 10: Update Existing Form Services Templates
In order to upgrade any form services or workflow form templates to the technical refresh update, run the following operation from the command line using the stsadm.exe tool.
%windir%\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin\stsadm.exe -o reconvertallformtemplates
Step 11: Restart the Search Service
On each of the application servers:
- Select Start, Programs, Administrative Tools and then Services
- From the listing of services, select the Office SharePoint Search Service and select Start
Enabling the WSS Search Service
- Log into the SharePoint Central Administration
- Select the Operations tab
- From the Topology and Services section, select Services on Server
- From the list of services, select Windows SharePoint Services Search and select Start
- You will be required to create a new database for search. To do so rename the existing search database to something else.
- When the new search database has been created, you will be returned to the services screen.
September 14th, 2006 at 1:48 pm
[...] Amanda has great set of instructions for this burning question!MOSS 2007WSS v3 [...]
September 15th, 2006 at 3:39 pm
[...] Community enhanced SharePoint 2007 B2TR installation guides and additional download components For those of you having trouble fully comprehending the installation guides referenced in Richard’s “Read this first” blog entry, I have some good news.
A few people within the SharePoint community have created enhanced installation guides that contain very helpful screenshots and even a video screencast. Here are the ones that I have reviewed and would highly recommend: · Amanda Murphy: MOSS 2007 Beta 2 to B2TR Patching Procedure (with screenshots) and WSS 3.0 Beta 2 to B2TR Patching Procedure (with screenshots) · Steve Smith (SharePoint MVP): MOSS 2007 B2+B2TR Slipstream Clean Installation Procedure (with screenshots) · Dustin Miller (SharePoint MVP): MOSS 2007 B2+B2TR Slipstream Clean Installation Procedure (screencast) · Joris Poelmans (SharePoint MVP): WSS 3.0 B2+B2TR Slipstream Clean Installation Procedure (with screenshots) IMPORTANT: If you have a specific question about MOSS 2007 and WSS 3.0 B2TR, please do not use this blog’s e-mail feedback mechanism because you’ll have a much better chance of getting a response by leaving a comment here or posting the inquiry to the appropriate newsgroup or other online Q&A and discussion resources listed on the SharePoint Community home page. In addition to the B2TR SKUs and Language Packs referenced in a previous blog entry, here are the B2TR updates of the SDKs and MOM Management Packs: · Software Development Kits · Windows SharePoint Services 3.0 SDK · Microsoft Office SharePoint Server 2007 SDK o Online version: http://msdn2.microsoft.com/en-us/library/ms550992.aspx o New/updated sections include: § Business Data Catalog – object model § Business Data Catalog – warnings and error messages § Metadata Model and “How to” topics § Custom Caching Overview: 4 new topics dedicated to caching in MOSS. The “How to: Extend Caching by Using the VaryByCustom Event Handler” topic has also been revised and expanded. § Web Content Management (WCM) “How to” topics, including “How To: Create a Minimal Master Page” and “How to: Customize Page Editing Toolbar Components” § ~370 member topics in the Microsoft.SharePoint.Publishing.* namespace § Field Controls and Control Templates § And so much more! · MOM Management Packs · Windows SharePoint Services 3.0 Beta 2 Technical Refresh Pack for Microsoft Operations Manager 2005 · Microsoft Office SharePoint Server 2007 Beta 2 Technical Refresh Pack for Microsoft Operations Manager 2005 · Project Server 2007 Beta 2 Technical Refresh Pack for Microsoft Operations Manager 2005 <Lawrence /> [...]
September 18th, 2006 at 7:42 am
Brilliant instructions, thank you, after struggling with the rubbish MS provided ones your’s were a walk in the park
September 18th, 2006 at 4:46 pm
Great job Amanda!
September 18th, 2006 at 11:25 pm
[...] Finally got round to downloading the new B2TR patches for MOSS and Office client. An awesome set of screenshots for installing WSS 2007 B2TR…very impressed, must have taken a while…but every man and his dog will be linking to it…good way of getting traffic
From reading blogs over the last week, there appears to be a lot of new stuff in there. Be good to have a good look round it all. Published Tuesday, September 19, 2006 7:16 AM by JeremyThake Filed under: Sharepoint 2007 / MOSS 2007 Anonymous comments are disabled [...]
September 19th, 2006 at 2:23 am
Thanks very much for this Amanda. Had some teething problems as shown on my blog post but all seems okay now.
http://made4the.net/blogs/c_net_tales/archive/2006/09/19/Sharepoint-2007-B2TR-upgrade-error.aspx
September 19th, 2006 at 8:58 am
It’s ROCKs Amanda, great job !!
September 19th, 2006 at 9:19 am
Shane and Gustavo – Thanks!
Jeremy – Glad you were able to work through your issue and thanks!
September 20th, 2006 at 6:58 am
[...] [...]
September 21st, 2006 at 7:00 am
Great Job! A quick note: After reviewing the ‘read first’ documentation along with your blog, it may be good to note that early beta adopters may have a unique install, using the Microsoft Pre-Release Software WinFX Runtime Components – (February Community Technology Preview (CTP)) as a rollup for .NET Framework 2.0 and Windows Workflow Foundation Build 2.2, then you will need to remove this as well. In Add-Remove programs, it is displayed as WinFX runtime components 3.0 – Beta 2.
September 21st, 2006 at 12:08 pm
By far one of the best step by step instruction sets I have seen for B2TR. I went ahead and linked to your posting.
Thanks
September 22nd, 2006 at 1:10 am
[...] Hallo zusammen,wer bis dato noch Probleme mit dem Update seiner B2 -> B2TR oder Installation des B2TR hat, für den hat Jason eine super Übersicht erstellt: ***One very important side note is make sure you have the JULY (NOT THE JUNE) 2006 CTP of the .NET Framework 3.0 or when you try to upgrade WSS/MOSS to TR it will not recognize that you have .NET 3.0 and will tell you to install. I personally went through this because I accidentally downloaded the JUNE CTP and installed that instead of the latest one…..took awhile to figure that one out! Below is a comprehensive list of download resources that pertain to all things Beta 2 Technical Refresh.· Amanda Murphy: MOSS 2007 Beta 2 to B2TR Patching Procedure (with screenshots) and WSS 3.0 Beta 2 to B2TR Patching Procedure (with screenshots)· Steve Smith (SharePoint MVP): MOSS 2007 B2+B2TR Slipstream Clean Installation Procedure (with screenshots)· Dustin Miller (SharePoint MVP): MOSS 2007 B2+B2TR Slipstream Clean Installation Procedure (screencast)· Joris Poelmans (SharePoint MVP): WSS 3.0 B2+B2TR Slipstream Clean Installation Procedure (with screenshots)Technical Refresh Download linksServerWindows SharePoint Services 3.0 x86 Windows SharePoint Services 3.0 (x64) MOSS 2007 x86 MOSS 2007 x64 Forms Server x86 Forms Server x64 Project Server 2007 x86 Project Server 2007 x64 Groove Server 2007 x64 .NET Framework 3.0 (JULY CTP) Client Downloads2007 Microsoft Office system Beta 2 Technical Refresh Visio 2007 SharePoint Designer 2007 x86 Groove 2007 SDK’sVisio 2007 SDK Project 2007 SDK Office SharePoint Server 2007 SDK Windows SharePoint Services 3.0 SDK Groove 2007 SDK Windows SDK for .NET Framework 3.0 July CTP Install Guides· MOSS 2007 B2TR Install Instructions· WSS v3 B2TR Install Instructions· Office Forms Server 2007 B2TR Install Instructions· Readme for .NET Framework 3.0 July CTPQuelle: http://www.sharepointblogs.com/jasonmedero/archive/2006/09/21/12500.aspxGrußDaniel Veröffentlicht Freitag, 22. September 2006 10:07 von danield [...]
September 26th, 2006 at 3:31 am
[...] MOSS 2007 Beta 2 to B2TR Patching Procedure (with screenshots)WSS 3.0 Beta 2 to B2TR Patching Procedure (with screenshots) Published Tuesday, September 19, 2006 7:28 PM by rrr Filed under: Sharepoint 2007 [...]
September 28th, 2006 at 6:38 pm
Bravo…brilliant instructions..
had a problem with the install of .net framework 3.0.
It didn;t install the workflow foundation with .net framework 3.0.
I had to apply the .net hotfix to get it to work…
October 2nd, 2006 at 12:37 am
Thanks Amanda – extremely helpful. Cheers.
October 3rd, 2006 at 12:08 am
Hi
After updating the B2TR patches, i tried crawling the local sharepoint server and sites, but the crawl seems to be going on and on forever.Is crawling and searching working fine after the update? Also I am unable to check in an item in a document library.
October 5th, 2006 at 11:33 pm
Thank you, with these instructions I managed to do the upgrade without any problems. By the way if the download manager for the .NET Framework 3.0 gives you grief try to download the complete package at: http://download.microsoft.com/download/D/C/0/DC09D14E-494D-4E5A-A1BA-783554D9D8FE/dotnetfx3.exe
October 8th, 2006 at 6:28 pm
If you receive this error during, let’s say a custom search:
Your search cannot be completed because this site is not assigned to an indexer. Contact your administrator for more information.
You’ll find a setting in SCAW->Application Management->Content databases->(click on your database)
Third line down:
“Select Windows SharePoint Services search server ”
Select one, and now you have assigned your site to an indexer.
on to the next error…
October 9th, 2006 at 12:54 am
Hi Amanda, Thanks a lot for this great article. I have a small problem, I hope I did not miss out anything, kindly help: -
After installing the B2TR, when I try to open a layout page in Sharepoint Designer 2007, I get the following error: -
“The server could not complete your request. Contact your Internet provider or web server administrator to make sure that the server has FrontPage Server Extensions or SharePoint Services Installed.”
N.B. I get the above error only when I try to open the toolbox of Sharepoint Designer 2007. Also, I am opening a remote site with Sharepoint Designer 2007, which is installed on my local system. I was not getting this error before B2TR. I have updated Sharepoint Designer 2007 also. Your help will be greatly appreciated.
Thx.
October 20th, 2006 at 8:18 am
Thanks for the great guide. I was able to upgrade on a standalone config fine but when I tried with SQL 2005 on a different server I can’t open the site or Cent Admin. This error message throws
Server Error in ‘/’ Application.
——————————————————————————–
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a “web.config” configuration file located in the root directory of the current web application. This tag should then have its “mode” attribute set to “Off”.
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the “defaultRedirect” attribute of the application’s configuration tag to point to a custom error page URL.
Anyone else have this problem?
November 16th, 2006 at 12:22 pm
Hi Amanda,
Really……….Greatwork
Thanks a Lot!!!!
February 3rd, 2007 at 6:45 pm
[...] Running SharePoint Server 2007 Beta 2 and Encountered Expiration? We love our beta testers and hope you listened to our advice about not running this in production environments. From an ease of use standpoint, if your environment is not very large you may just want to wipe and reload with RTM after you backup your server. The content is still in the database and there are tools you can use to extract files. Otherwise, if you are running beta 2 and need to find a path to RTM, we have put together some steps and resources to help you get there. Product support don’t support Pre-RTM code, and are busy supporting RTM customers, so please be patient with us. Upgrading from an Expired SharePoint Server Beta 2 Trial 1. Perform a complete Server and SQL backup of the SharePoint databases. 2. If at all possible follow the “How to install the Beta 2 Technical Refresh update in a new installation” instructions from http://technet2.microsoft.com/Office/en-us/library/f49862ab-e067-4723-bb90-7eb1182c65ce1033.mspx?mfr=true to install Beta2TR on a different server. (Note: You will need to have access to the Beta2 installation bits to do this. We are working on making the bits available. More to come later.) 3. If an additional server is not available, if you have the beta 2 bits, you will need to uninstall and follow the rest of the steps in step 2. 4. Follow the steps to setup the new farm for the first time (setup services on server, create SSP, etc) then attach the Beta 2 content database to force an upgrade on the content. 5. Start planning the Beta 2 TR to RTM upgrade as Beta 2 TR will expire on May 15th. (See Beta 2 TR Resources below) Key Beta 2 to Beta 2 TR Resources: Installing Microsoft Office SharePoint Server 2007 for Beta 2 Technical Refresh Download: SharePoint Server 2007 Beta 2 Technical Refresh Microsoft® Windows® Workflow Foundation Runtime Components Beta 2.2 and Visual Studio® 2005 Extensions for Windows Workflow Foundation Beta 2.2 Microsoft .NET Framework 3.0 Redistributable Package Microsoft Pre-Release Software Microsoft .NET Framework 3.0 – Release Candidate Beta 2 TR to RTM Upgrade Resources · SharePoint Server 2007 B2TR Update Guide – This includes all of the update steps, known issues, workarounds and planning guidance. · SharePoint Server 2007 B2TR Readme – This includes workarounds and fixes for less common issues for specific configurations. · Upgrading from Office SharePoint Server 2007 Beta 2 Technical Refresh to Release Version · Step by Step Instructions (with Screenshots) Office SharePoint Services B2TR to Release by Shane Young (SharePoint MVP) · Upgrading from Windows SharePoint Services 3.0 Beta 2 Technical Refresh to Release Version Related Resources: · Build to Build Supportability · Version to Version Supported Paths · Features comparison, Edition comparison, and Differences Community Enhanced Related Articles: · MOSS 2007 Beta 2 to B2TR Patching Procedure (with screenshots) and WSS 3.0 Beta 2 to B2TR Patching Procedure (with screenshots) — by Amanda Murphy · MOSS 2007 Beta 2 to B2TR Patching Procedure (with screenshots) – in French — by Renaud Comte (SharePoint MVP) · MOSS 2007 B2+B2TR Slipstream Clean Installation Procedure (with screenshots; in Word format) — by Steve Smith (SharePoint MVP) · MOSS 2007 B2+B2TR Slipstream Clean Installation Procedure (screencast; in Flash format) — by Dustin Miller (SharePoint MVP) · MOSS 2007 B2+B2TR Slipstream Clean Installation Procedure (with screenshots; in PDF format) – in French — by Etienne Legendre (Windows Server MVP) and Erol Giraudy (SharePoint MVP) · WSS 3.0 B2+B2TR Slipstream Clean Installation Procedure (with screenshots) — by Joris Poelmans (SharePoint MVP) · SPS 2003 to OSS 2007 B2TR Gradual Upgrade Procedure (with screenshots) — by Shane Young (SharePoint MVP) Published Sunday, February 04, 2007 1:40 AM by joelo Filed under: B2TR, Beta 2, Upgrade [...]
June 26th, 2007 at 7:57 am
[...] SharePoint 2007: Updating MOSS Beta 2 to Beta 2 Technical Refresh (Beta 2TR) [...]
August 6th, 2007 at 7:57 am
Hi,
My customers would like to know if there is a limit (in # of entries, size of entries or length of page) to amount of blog entries that can fit on one page. I can’t find that information. Thanks
September 5th, 2007 at 1:38 pm
[...] 9/19/2006 Sharepoint 2007 B2TR upgrade errorI followed Amanda’s instructions to the letter and got results as described, but for some reason got this error on Step 11!"Windows could not start the Office Sharepoint Server Search on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -2147467262." Oh yeah…"-2147467262"…I remember that one! Where do they come up with these codes?!? [:@] Anyway, I checked the System Event Log and found this little gem:"Job ‘Distribution List Import Job’ failed after 3 tries and 180 second(s). Will not try again.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp." I tried starting it again and got this:"Job ‘Distribution List Import Job’ failed. It will be re-tried again in 60 second(s). Reason: Failed to obtain crawl status.Techinal Details:Microsoft.Office.Server.UserProfiles.UserProfileException: Failed to obtain crawl status. at Microsoft.Office.Server.UserProfiles.SRPSite.IsImportInProgress(String contentSourceName) at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.IsProfileImportInProgress() at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.IsImportInProgress() at Microsoft.Office.Server.UserProfiles.DLImportJob.Execute() at Microsoft.Office.Server.Administration.JobHandler.Execute(Object state, Boolean timedOut)For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."and again:"Starting up database ‘SharedServices1_Search_DB_6550d16c-23b6-493c-a92c-21c810deeed4′.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.""Job ‘Distribution List Import Job’ failed. It will be re-tried again in 60 second(s). Reason: Failed to obtain crawl status.Techinal Details:Microsoft.Office.Server.UserProfiles.UserProfileException: Failed to obtain crawl status. at Microsoft.Office.Server.UserProfiles.SRPSite.IsImportInProgress(String contentSourceName) at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.IsProfileImportInProgress() at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.IsImportInProgress() at Microsoft.Office.Server.UserProfiles.DLImportJob.Execute() at Microsoft.Office.Server.Administration.JobHandler.Execute(Object state, Boolean timedOut)For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."and then it appears to loop round these errors.I tried starting up the Sharepoint Home and first time it came up with an error, but after I did the bits above it seemed to then work ok.I tried starting up the Sharepoint 3.0 Central Administration and that appears to come up fine. I checked the version in Site Settings and it’s Version 12.0.0.4407. So all seems well….the rest of Step 11 failed when I tried to Start the Search Service in the Operations page. I get:"The service did not respond to the start or control request in a timely fashion"Is this a "Microsoft timely fashion"? Anyway, the second time I tried to start it it worked. Seems like everything takes two goes! [:D]Honestly, I’m really impressed with the new Sharepoint 2007, as with any product, especially in Beta I expect problems. From experience with RedDot, Hummingbird, M$ MCMS, M$ TFS etc. It’s the joys of being in the software business!Posted at 12:00 AM by Jeremy Thake | Category: Sharepoint: Portal | Permalink | Email this Post | Comments (0) [...]
September 11th, 2007 at 9:40 am
[...] http://blog.funknstyle.com/?p=542 [...]
September 25th, 2007 at 2:55 am
[...] [...]
May 15th, 2008 at 6:57 pm
Sharepoint 2007 B2TR upgrade error…
I followed Amanda’s instructions to the letter and got resul ……
September 16th, 2008 at 8:45 am
I did not see any search server in the services on server list.
How can i make appear it? y tried to start the Sharepoint Services Search service on the windows services but it gets me back the followin error:
The handle is invalid.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 9/16/2008
Time: 10:44:09 AM
User: N/A
Computer: COMPUTERNAME
Description:
The Windows SharePoint Services Search service terminated with the following error:
The handle is invalid.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.