Share via

Upgrading to Windows Server 2008 for Windows SharePoint Services 3.0 with SP1

  • Article

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2010-04-09

If you have Windows SharePoint Services 3.0 with Service Pack 1 (SP1) installed on a computer running Windows Server 2003, and you are planning to upgrade to Windows Server 2008, use the procedures in this article to prepare Windows SharePoint Services 3.0 for the upgrade.

Before you begin

Address any installation issues

The Windows Server 2008 installer will block the upgrade if any one of the following applies to the computer running Windows Server 2003:

  • Windows SharePoint Services 2.0 is installed.

  • FrontPage 2002 Server Extensions from Microsoft are installed.

  • Windows Internal Database SP1 is installed.

  • Windows SharePoint Services 3.0 SP1 is not installed.

You will need to address any installation issues on the computer running Windows Server 2003 before preparing Windows SharePoint Services 3.0 for the upgrade.

Install Windows Internal Database SP2

If this is a basic or stand-alone Windows SharePoint Services 3.0 installation that uses Windows Internal Database (MICROSOFT##SSEE) as the default back-end database, you must install Windows Internal Database SP2 before you begin the Windows Server 2008 installation. Windows Internal Database uses SQL Server technology as a relational data store for Windows roles and features only, such as Windows SharePoint Services, Active Directory Rights Management Services, UDDI Services, Windows Server Update Services, and Windows System Resources Manager.

For more information about Windows Internal Database SP2, and to download the service pack for either x86 or x64 architecture, see the following links:

Stop the Search service

If the Windows SharePoint Services Search service (Spsearch) is running while you are installing Windows Server 2008, the search index might become corrupt. To avoid this, you should perform the following procedure.

To stop the Windows SharePoint Services Search service

  1. Open a command prompt window.

  2. Change the Startup type for the Windows SharePoint Services Search service to disabled by running the following command:

    sc config spsearch start=disabled

    The message [SC] ChangeServiceConfig SUCCESS is displayed.

  3. Stop the Windows SharePoint Services Search service by running the following command:

    net stop spsearch

    The message The Windows SharePoint Services Search service was stopped successfully is displayed.

    Note

    The search index might be corrupt if the SharePoint Products and Technologies Configuration Wizard cannot start or if the wizard seems to be stalled while trying to start the Windows SharePoint Services Search service after the upgrade. For more information, see the "Reset the Windows SharePoint Services Search service index" section in this article.

Install Windows Server 2008

You can now proceed with the Windows Server 2008 installation. For more information about installing Windows Server 2008, see the Windows Server 2008 Technical Library (https://go.microsoft.com/fwlink/?LinkId=106547&clcid=0x409).

Perform post-installation procedures

After the Windows Server 2008 installation is complete, you must perform a binary repair to configure Windows SharePoint Services 3.0.

To configure Windows SharePoint Services on Windows Server 2008

  1. Perform a binary repair. In Windows Server 2008, click Start, click Control Panel, open Programs and Features, select Windows SharePoint Services 3.0, and then click Change.

    If Least User Access (LUA) is enabled on this computer, you can follow either of the following steps:

    • Turn off LUA and then repeat the instructions in this step.

    • Run Setup.exe from an installation point (where you have extracted the SP1 files to the Updates folder). When Setup prompts you to choose an action, choose Repair.

  2. Run the SharePoint Products and Technologies Configuration Wizard.

If you installed Windows SharePoint Services 3.0 as a stand-alone installation or if you installed it on a Web server in a server farm but the farm account is not an administrator on the computer, you must grant the Windows SharePoint Services Timer (SPTimerV3) service permission to read from Internet Information Services (IIS) 7.0. Examples of symptoms that you might experience if the SPTimerV3 service does not have the appropriate permissions include:

  • Future installations of software updates might fail.

  • Web application creation could fail in server farms with more than one Web application.

  • Operations that use the timer job to query for IIS Web site properties could fail.

To grant the SPTimerV3 service permission to read from IIS 7.0

  1. Log on to the computer with a domain account that is a member of the Administrators group on the local computer.

  2. Open an elevated command prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  3. Change directory to %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\BIN.

  4. Run the command:

    stsadm -o grantiis7permission

    The following messages confirm the changes:

    Granting permission to SPTimerV3 service to read from IIS 7.0 or above.

    Operation completed successfully.

Configure Windows Server Backup

If you want to use Windows Server Backup with Windows SharePoint Services 3.0, you must configure certain registry keys. If you do not configure these registry keys, Windows Server Backup will not work properly with Windows SharePoint Services 3.0. For information about configuring the registry keys for Windows Server Backup, see the "Configure Windows Server Backup" topic in Install a stand-alone server on Windows Server 2008 (Windows SharePoint Services) (https://go.microsoft.com/fwlink/?LinkId=106802).

Known issues

Repair not allowed when Least User Access is enabled

After the Windows Server 2008 installation is complete, when you open Programs and Features to repair Windows SharePoint Services 3.0 or language template packs, you will not be able to run the repair operation if LUA is enabled (the default setting). Before running repair, make sure LUA is disabled.

Fixing problems after upgrading without Windows Internal Database Service Pack 2

The Windows Server 2008 installer will block the upgrade if you have Windows Internal Database SP1 installed. A potential problem is that, after the upgrade is blocked, the user removes Windows Internal Database SP1, but does not install Windows Internal Database SP2. If this is the situation, and Windows Server 2008 installed successfully after Windows Internal Database SP1 was removed, install Windows Internal Database SP2 and then use the following procedure to make sure your sites and the Search service work properly.

To fix sites and the search function after upgrade

  1. Stop all Windows SharePoint Services 3.0 services:

    • Windows SharePoint Services Timer

    • Windows SharePoint Services Administration

    • Windows SharePoint Services Tracing

    • Windows SharePoint Services Search

  2. Open a command prompt window and restart IIS with the following command:

    restartiis

  3. To install Windows Internal Database, included with Windows Server 2008, open Server Manager, click Features, click Add Features, select the Windows Internal Database check box, and then click Install to complete the Add Features Wizard.

  4. Use the Microsoft SQL Server 2005 Command Line Query Utility (sqlcmd) to start the Windows Internal Database:

    sqlcmd -S \\.\pipe\mssql$microsoft##ssee\sql\query -E

    Note

    The sqlcmd utility is a free download, but because sqlcmd requires Microsoft SQL Server Native Client, we recommend that you download the entire Feature Pack for Microsoft SQL Server 2005 (https://go.microsoft.com/fwlink/?LinkId=70728). For more information about the sqlcmd utility, see sqlcmd Utility (https://go.microsoft.com/fwlink/?LinkId=81183).

  5. Run the following command for each Windows SharePoint Services 3.0 database (*.mdf) and log file (*_log.ldf). By default, all files will be in the following folder:

    %Windows%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data

    EXEC sp_attach_db @dbname = '<dbname>', @filename1 = '<drive:\path\Data>\<dbname>.mdf', @filename2 = <drive:\path\Data>\<dbname>_log.ldf'

    Go

    Note

    You should see, at a minimum, these databases: configdb, contentdb, admin contentdb, and searchdb.

  6. Start the following Windows SharePoint Services 3.0 services:

    • Windows SharePoint Services Timer

    • Windows SharePoint Services Administration

    • Windows SharePoint Services Tracing

    Note

    Make sure you do not start the Windows SharePoint Services Search service.

  7. Restart the Windows Internal Database service:

    1. Click Start, point to Administrative Tools, and then click Services.

    2. In the list of services, right-click Windows Internal Database (MICROSOFT##SSEE), and then click Stop.

    3. Right-click Windows Internal Database (MICROSOFT##SSEE), and then click Start.

    Note

    If the Windows SharePoint Services Search service was running before you started this step, you must restart it by running the following command:
    stsadm -o spsearch -action start -databaseserver %_be% -databasename wsssearch

  8. If you completed a binary repair in the "Perform post-installation procedures" section you can skip this step. Otherwise, to perform a binary repair, click Start, click Control Panel, click Programs and Features, select Windows SharePoint Services 3.0, and then click Change.

  9. Run the SharePoint Products and Technologies Configuration Wizard to configure Windows SharePoint Services 3.0.

Reset the Windows SharePoint Services Search service index

If you did not stop the Windows SharePoint Services Search service while the upgrade was running, you might need to reset the search index for the Windows SharePoint Services Search service by performing the following procedure.

Note

If you ran the SharePoint Products and Technologies Configuration Wizard while the Windows SharePoint Services Search service was running, the wizard could have corrupted the search index. In this case, you should follow the "To reset a corrupt Windows SharePoint Services Search service index" procedure in this article.

To reset the Windows SharePoint Services Search service index

  1. Open SharePoint Central Administration. Click Start, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.

  2. On the Operations tab, click Services on server.

  3. In the list of services, click Stop to stop the Windows SharePoint Services Search service.

  4. In the warning dialog box, click OK.

    Wait for the operation to complete.

  5. On the Services on Server page, click Start to start Windows SharePoint Services Search.

    The Windows SharePoint Services Search service settings page opens.

  6. On the Windows SharePoint Services Search service settings page, scroll to the Search Database section and rename the Database Name with a new, unused name. Scroll down and click Start.

    Wait for the operation to complete.

  7. In SharePoint Central Administration, on the Application Management page, click Content databases.

  8. On the Manage Content Databases page, click the name of the content database for the site.

  9. On the Manage Content Database Settings page, in the Search Server section, on the menu, click the Windows SharePoint Services search server that you just started, and then click OK.

If the SharePoint Products and Technologies Configuration Wizard cannot start the Spsearch service, the search index might be corrupt. In this situation, you can use Central Administration to open the Operations Web page and the Services on Server Web page, and then you will see that the status for Spsearch is starting. However, because the service will not respond to a stop request from Central Administration, you must use the following procedure.

To reset a corrupt Windows SharePoint Services Search service index

  1. Close the SharePoint Products and Technologies Configuration Wizard manually:

    1. Open Task Manager, and then click the Process tab.

    2. Select Psconfig, and then click End Process.

  2. To stop the Spsearch service, open a command prompt window and enter the command:

    stsadm -o spsearch -action stop

  3. Open Central Administration. Click Start, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.

  4. On the Operations tab, click Services on server.

  5. On the Services on Server page, click Start to start Windows SharePoint Services Search.

    The Windows SharePoint Services Search service settings page opens.

  6. On the Windows SharePoint Services Search service settings page, scroll to the Search Database section and rename the Database Name with a new, unused name. Scroll down and click Start.

  7. Wait for the operation to complete.

  8. In SharePoint Central Administration, on the Application Management page, click Content databases.

  9. On the Manage Content Databases page, click the name of the content database for the site.

  10. On the Manage Content Database Settings page, in the Search Server section, on the menu, click the Windows SharePoint Services search server that you just started, and then click OK.

  11. Start the SharePoint Products and Technologies Configuration Wizard.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Downloadable books for Windows SharePoint Services.