Export (0) Print
Expand All

Upgrading from Windows SharePoint Services 3.0 Beta 2 Technical Refresh to Release Version

SharePoint 2007

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2006-12-04

Follow the instructions in this article carefully when you upgrade from Microsoft Windows SharePoint Services 3.0 Beta 2 Technical Refresh to the release version.

During upgrade, your farm will be offline for a period of time while the databases are upgraded to the release version of the product. Be sure to notify your customers in advance.

In this article:

Perform the procedures in this section on every server computer in your farm.

Delete failed timer jobs
  1. Open SharePoint 3.0 Central Administration.

  2. On the top navigation bar, click Operations.

  3. In the Global Configuration section, click Timer job definitions.

  4. On the Timer Job Definitions page, look for backup and restore or upgrade timer jobs in the list. If any exist, delete them by clicking the timer job and then clicking Delete on the page that appears.

Record current server information
  1. Record the name of every server computer that hosts SharePoint 3.0 Central Administration.

  2. Record the following information for each server computer:

    • Server type   When you install the release version, you will need to specify the same server type that you have currently installed for each server computer in your farm.

      NoteNote:
      The server type of a computer is located in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\ServerRole registry subkey. The values are singleserver for Basic installations or WFE for Advanced (farm) installations.
    • Central Administration account and password   You will need to use the same account and password when you install the release version.

Stop Windows SharePoint Services Search in a Basic installation
  1. Open SharePoint 3.0 Central Administration.

  2. On the top navigation bar, click Operations.

  3. In the Topology and Services section, click Services on Server.

    Stop Windows SharePoint Services Search.

Stop Windows SharePoint Services Search in an Advanced (farm) installation
  1. On the Start menu, click Run. In the Open box, type

    cmd

    and then click OK.

  2. At the command prompt, type

    cd %Programfiles%\Common Files\Microsoft Shared\web server extensions\12\bin

  3. At the command prompt, type

    stsadm -o spsearch -action list > SearchServerList.txt

  4. Open SharePoint 3.0 Central Administration.

  5. On the top navigation bar, click Operations.

  6. In the Topology and Services section, click Services on Server.

  7. On every server, stop Windows SharePoint Services Search if it is not already stopped.

    To easily check the status of the search service on each server, click the server name in the Server list.

Modify the registry setting for the configuration database connection
  1. On the Start menu, click Run. In the Open box, type

    regedit

    and then click OK.

  2. In the Registry Editor, navigate to and click the following subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDB

  3. On the File menu, click Export, and in the File name box, type
    SharePointRegKeyBackup
    This backs up the subkey so you can restore it to your registry later, if necessary.

  4. Under the registry subkey, right-click the dsn value, and then click Rename.

  5. Type

    dsn2

    for the name, and then press ENTER to save your changes.

    CautionCaution:
    Be sure to check that you have renamed the registry key to dsn2. If you fail to perform this step, upgrade will fail and you will have to manually upgrade the content databases to a new installation. This step is required for the installation process to detect and upgrade Beta 2 Technical Refresh to the release version.
  6. Close the Registry Editor.

Delete existing SharePoint Products and Technologies Configuration Wizard logs
  1. Open a command window.

  2. At the command prompt, type

    cd "%programfiles%\common files\microsoft shared\web server extensions\12\logs"

    and then press ENTER.

  3. At the command prompt, type

    del psc*.log

    and then press ENTER.

Perform the procedure in this section on all server computers in your farm. You can perform the steps in parallel across all server computers, or complete the procedure on each computer before moving to the next. You do not need to uninstall .NET Framework or Windows Workflow Foundation from these computers.

Uninstall Beta 2 Technical Refresh
  1. In Control Panel, double-click Add or Remove Programs.

  2. Uninstall all Microsoft Windows SharePoint Services 3.0 Language Packages.

    CautionCaution:
    You must uninstall all language packs before you uninstall Windows SharePoint Services 3.0 Beta 2 Technical Refresh. If you do not uninstall all language packs at this point, you will be unable to install the release version of Windows SharePoint Services 3.0.
  3. A message box appears to remind you to run the SharePoint Products and Technologies Configuration Wizard after uninstalling the language packs. You can ignore this reminder; click OK.

  4. Select Microsoft Windows SharePoint Services 3.0, and then click Remove.

  5. In the first message box that asks you to confirm that you want to uninstall, click Yes.

  6. In the second message box that asks you to confirm that you want to uninstall, click OK.

  7. If you are prompted to restart the computer, do so.

The procedure in this section must first be performed on a front-end Web server that hosted the Central Administration Web application in your Beta 2 Technical Refresh installation, which you noted under "Record current server information," earlier in this article. After you successfully complete this procedure on that server computer, perform it on all the other server computers in the farm, one at a time.

NoteNote:
If upgrade fails on any server computer, do not run this procedure on any other computer in the farm until you have fixed the problem. After you have fixed the problem, run the SharePoint Products and Technologies Configuration Wizard again to resume upgrade.
Install Windows SharePoint Services 3.0 release version
  1. Run Setup for the release version of Windows SharePoint Services 3.0.

  2. Follow the steps to install the product. If the Upgrade Earlier Versions dialog box is displayed, choose No, do not upgrade at this time, and then click Install Now.

  3. On the welcome page of the SharePoint Products and Technologies Configuration Wizard, click Cancel, and then click Yes in the dialog box that appears.

  4. If you are using a Basic installation, perform the following steps:

    1. In Control Panel, double-click Administrative Tools, and then double-click Services.

    2. Double-click SQL Server 2005 Embedded Edition (MICROSOFT##SSEE).

    3. In the Startup type list, click Automatic, and then click OK.

    4. Click Start the service.

    5. On the Start menu, click Run. In the Open box, type

      regedit

      and then click OK.

    6. In the Registry Editor, navigate to the following subkey:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS

    7. Under the registry subkey, double-click the Server Role value, change the value to SINGLESERVER, and then click OK.

    8. Close the Registry Editor.

  5. Install any Microsoft Windows SharePoint Services 3.0 Language Packages. At the end of every language pack installation, cancel the SharePoint Products and Technologies Configuration Wizard when it opens.

  6. Run the SharePoint Products and Technologies Configuration Wizard. Use the Central Administration account and password that you noted under "Record current server information," earlier in this article. Be sure you select the same server type you previously used for this server, which you also noted under "Record current server information."

    A message box appears to remind you that services will be started; click Yes.

    A message box appears to remind you to run the wizard on each server in the farm; click OK.

    NoteNote:
    Upgrade may only be run on one server computer in the farm at a time.

    Ignore the warning that is briefly displayed in the wizard that reads Failed to start search service SPSearchServiceInstance on this server after completing upgrade. Please start it manually. You will start this service in step 10.

  7. If you are performing a Basic installation and the SharePoint Products and Technologies Configuration Wizard fails with the error message …is blocked because the signature is not valid, do the following:

    1. On the Start menu, click Run. In the Open box, type

      regedit

      and then click OK.

    2. In the Registry Editor, navigate to the following subkey, and then delete it:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\Services\Microsoft.SharePoint.Search.Administration.SPSearchService

    3. Run the SharePoint Products and Technologies Configuration Wizard again.

  8. Wait until upgrade has been completed successfully on this server computer before you start upgrade on any other server computer.

  9. Open the file SearchServerList.txt, which you created in step 3 of "Stop Windows SharePoint Services Search in an Advanced (farm) installation," earlier in this article.

  10. On every server listed with Status:Online, do the following:

    1. On the Start menu, click Run. In the Open box, type

      cmd

      and then click OK.

    2. At the command prompt, type

      cd %Programfiles%\Common Files\Microsoft Shared\web server extensions\12\bin

    3. At the command prompt, type

      stsadm -o spsearch -action start -farmserviceaccount DoMAIN\name -farmservicepassword password -databaseserver searchdatabaseserver -databasename WSS_Search_NewDB

  11. After starting search, you need to associate content databases to search servers. If a content database is not associated with a search server and you attempt a search on a site in the content database, the following message will be displayed: Your search cannot be completed because this site is not assigned to an indexer. Perform the following steps:

    1. Open SharePoint 3.0 Central Administration, click Application Management, and then click Content Databases.

    2. Click the content database for a Web application, and for Search Server choose a Windows SharePoint Services Search Server.

    3. Repeat these steps for each content database for each Web application.

If the Search service is not functional, perform the following procedures for both Basic and Advanced (farm) installations.

On each and every server that has an online ("started") Windows SharePoint Services Search service, do the following:

  1. Open a command prompt window on the server, and change directory to Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN.

  2. Type

    stsadm -o spsearch –action list

    This will output the current association of content databases to search servers.

  3. Type

    stsadm -o spsearch -action stop

    This stops the Windows SharePoint Services Search service (this action throws away the search index).

If you encounter a problem or error, do the following:

  1. Type

    net stop sptimerv3

    net stop spsearch

If the service does not stop, do the following:

  1. Open a command prompt window, and type

    run tasklist /svc

  2. Find "SPSearch" in the output and note the process ID <pid>.

  3. At the command prompt, type

    run taskkill /f /pid <pid>

  4. At the command prompt, type

    stsadm -o spsearch -action stop

    net start sptimerv3

After you have successfully installed the release version and verified that the search service is functional, perform this procedure on every server computer in your farm.

Uninstall and reinstall Microsoft .NET Framework 3.0
  1. In Control Panel, click Add or Remove Programs, select Microsoft .NET Framework 3.0, and then remove it.

  2. Install Microsoft .NET Framework 3.0 (http://www.microsoft.com/downloads/details.aspx?FamilyId=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en).

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft