Export (0) Print
Expand All

Install and configure Windows SharePoint Services for an in-place upgrade

Updated: March 5, 2009

Applies To: Windows SharePoint Services 3.0

Updated: 2009-03-05

When you run an in-place upgrade, all content and configuration data is upgraded in-place, at one time. When you start the in-place upgrade process, the Web server and Web sites remain offline until the upgrade has been installed. When you perform an in-place upgrade, you cannot pause or roll back to the previous version.

Upgrade is a detailed and complicated operation. Even in relatively basic environments, there may be customizations that do not lend themselves to a smooth and simple upgrade. These customizations, and many other variables, are outside of the control of the upgrade process and may cause the in-place upgrade to fail.

We recommend in-place upgrade only for a stand-alone server and even then, in limited situations. In general, this means that you should consider in-place upgrade for environments that meet both of the following conditions:

  • Small installations

  • Environments that have not been customized

In practice, this means that you should only use in-place upgrade in environments where there is minimal impact when a server is down. Examples include development, test, or staging servers where you need a quick upgrade experience and can quickly roll back the entire server to an earlier configuration. For example, in a virtualized environment, if something goes wrong with the upgrade, you can discard the undo disks and, in minutes, be back to your original environment. Another option to avoid having to troubleshoot a failed upgrade is to restore your server from a backup.

NoteNote:

If you have a more complex server farm, we recommend that you perform a gradual upgrade. For more information about performing a gradual upgrade, see Install and configure Windows SharePoint Services for a gradual upgrade. For more information about choosing an upgrade approach, see Determine upgrade approach [Windows SharePoint Services].

When upgrading a server farm, be sure to upgrade all of the servers in the server farm in the following order:

  1. Run Setup to install the new version on all servers in the server farm.

  2. Run the SharePoint Products and Technologies Configuration Wizard on the front-end Web server that contains SharePoint Central Administration.

  3. Run the SharePoint Products and Technologies Configuration Wizard on all other front-end Web servers or search servers in the farm in any order.

In this article:

Before you begin

Before you begin installing Windows SharePoint Services 3.0, make sure that you have installed and configured all the pre-requisite software. For more information, see Install all pre-requisites (Windows SharePoint Services).

Make sure that these are the minimum permissions for the account that you use to run Setup and the SharePoint Products and Technologies Configuration Wizard:

  • The account is a member of the Administrators group on the Web server computer.

  • The account is granted the fixed database role (db_owner) for all SharePoint Products and Technologies databases.

In many IT environments, database administrators (DBAs) create and manage databases. Security policies and other policies in your organization might require that DBAs create the databases needed by Windows SharePoint Services 3.0.

NoteNote:

For information about how to deploy Windows SharePoint Services 3.0 in an environment in which DBAs create and manage databases, see Deploy using DBA-created databases (Windows SharePoint Services) (http://go.microsoft.com/fwlink/?LinkID=86818&clcid=0x409).

  • If you are running an in-place upgrade on a server farm, stop the World Wide Web Publishing Service (W3SVC) on all front-end Web servers to disconnect all the users from the server farm. In server farms with multiple front-end Web servers, if you allow users to connect after the files and databases have been updated on one Web server, and the other Web servers have not been updated, users will not be able to browse the Web sites.

Install Windows SharePoint Services 3.0

  1. Run Setup.exe.

    TipTip:

    As an alternative to installing Windows SharePoint Services 3.0 and then separately deploying the available software updates, you can download a Windows SharePoint Services 3.0 install file that includes the available software updates. You can find the Windows SharePoint Services 3.0 install file that includes the available software updates on the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkID=72322&clcid=0x409).

  2. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue.

  3. On the Upgrade earlier versions page, click Yes, perform an automated in-place upgrade.

  4. On the Server Type tab, select your server type:

    • Choose Web Front End if you are running upgrade on a server farm.

    • Choose Stand-alone if this is a stand-alone server (not part of a SharePoint farm), and you want to use Windows Internal Database for your database.

    NoteNote:

    Your server environment may not detect all of these server types.

  5. Click Install Now.

    NoteNote:

    If you have a custom site definition or custom Web application installed on your server, you will see a Setup Warning box notifying you that there are third-party products installed that integrate with Windows SharePoint Services 2.0. If you are aware of these customizations or applications and are prepared to continue with the upgrade process (for example, if you have created upgrade definition files for any custom templates), click OK. If you want to cancel the upgrade process and investigate these products, click Cancel. For more information about upgrade definition files, see Develop new custom site definitions and create upgrade definition files (Windows SharePoint Services).

  6. The Installation Progress page appears and Setup installs Windows SharePoint Services 3.0 and applies updates.

  7. On the completion page, clear the Run the SharePoint Products and Technologies Configuration Wizard now check box, and then click Close.

Before you run the SharePoint Products and Technologies Configuration Wizard, you should perform the following steps:

NoteNote:

In server farm deployments, all your Web servers must have the same software update version applied. To accomplish, you can create an installation source that contains a copy of the released software product, along with the available software updates (also known as a slipstreamed installation source). When you run Setup from this updated installation source, the Web server will have the same software update version as the rest of the Web servers in your server farm. You can also use the installation source to add a new Web server to an existing server farm. When you run Setup from this updated installation source, the new Web server will have the same software update version as the rest of the Web servers in your server farm. For more information about creating an installation source, see Create an installation source that includes software updates (Windows SharePoint Services 3.0)

Run the SharePoint Products and Technologies Configuration Wizard

  1. Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.

  2. In the SharePoint Products and Technologies Configuration Wizard, on the Welcome to SharePoint Products and Technologies page, click Next.

    A message appears, notifying you that Internet Information Services (IIS), the SharePoint Administration Service, and the SharePoint Timer Service may need to be restarted or reset during configuration.

  3. Click Yes to continue with the wizard.

    A message appears, notifying you that you should download and install new language template packs for the new version.

  4. Click OK to confirm the message and continue with the wizard. Do not install the language template packs until you have completed running the configuration wizard.

    NoteNote:

    If you chose Stand-alone as your server type, the configuration wizard skips the next few steps and starts the configuration process. Skip to step 8 in this procedure.

  5. On the Configure SharePoint Central Administration Web Application page, if you want to use a specific port number for SharePoint Central Administration, select the Specify port number check box, and then type the port number to use.

  6. In the Configure Security Settings section, select either Negotiate (Kerberos) or NTLM, depending on your environment, and then click Next.

    NoteNote:

    To enable Kerberos authentication, you must perform additional configuration. For more information about authentication methods, see Plan authentication methods (Windows SharePoint Services).

  7. In the Completing the SharePoint Products and Technologies Configuration Wizard page, verify the settings, and then click Next.

    The configuration wizard runs and configures the configuration database and Central Administration Web application for Windows SharePoint Services 3.0.

  8. A message appears notifying you that if you have a server farm with multiple servers, you must run Setup on each server to install new binary files before continuing the configuration wizard. Depending on your server farm configuration, and where you are in the process of installing and configuring Windows SharePoint Services 3.0, you have three choices:

    • If this is the only server in your farm, no other actions are necessary. Click OK to continue with the wizard.

    • If you have other servers in your farm, and you have not yet run Setup and the configuration wizard on the other servers, leave this message open on this server, and then run Setup and the configuration wizard on the other servers in the farm. When all of the other servers are at this same stage, you can return to the front-end Web server and click OK to continue with the SharePoint Products and Technologies Configuration Wizard.

    • If you have already run Setup and the configuration wizard on all servers in your server farm and they are all at this stage, on a front-end Web server, click OK to continue with the configuration wizard.

  9. The configuration wizard continues the upgrade process by setting up the configuration database and installing the Central Administration Web application.

  10. On the Configuration Successful page, review the settings that have been configured, and then click Finish.

    The SharePoint Products and Technologies Configuration Wizard closes and the Upgrade Running page opens. You may be prompted to enter your user name and password before the Upgrade Running page will open. The upgrade process might take a while to complete. The Upgrade Running page refreshes every minute.

  11. After the process has completed, click Continue.

    The Central Administration home page opens.

If you stopped the World Wide Web Publishing Service (W3SVC) on all front-end Web servers before the upgrade, make the Web servers available to users by manually starting the World Wide Web Publishing Service on the front-end Web servers.

Install and configure Windows SharePoint Services 3.0 using the command line

If you prefer, you can use the command line to install and configure Windows SharePoint Services 3.0 instead. For more information, see Setup.exe command-line reference (Windows SharePoint Services), Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Windows SharePoint Services), Stsadm command-line tool (Windows SharePoint Services), and Install Windows SharePoint Services 3.0 by using the command line.

NoteNote:

If you started the installation in silent mode, using the /q switch, the SharePoint Products and Technologies Configuration Wizard does not automatically start. To continue the upgrade, you need to force the upgrade by either manually starting the wizard or running the psconfig command with arguments to force an in-place version to version upgrade.

Review the log files and resolve any issues

If upgrade fails or reports issues, you can refer to the log files for more information. The Upgrade.log file is located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS.

CautionCaution:

In some configurations, the SharePoint Timer Service (OWStimer) account—which, by default, is the same account used by the SharePoint Central Administration v3 application pool account—is configured with credentials that do not have permission to access the LOGS folder in %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\. If this is the case, part of the Upgrade.log file is stored in the temporary storage folder of the account that is running the SharePoint Timer service. To avoid the possibility of deleting the upgrade log file when you restart the server computer, copy Upgrade.log to another location.

For information about viewing the upgrade log file, see Verify upgrade (Windows SharePoint Services).

For information about troubleshooting common issues, see Troubleshoot and resume upgrade (Windows SharePoint Services).

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