Upgrade Web applications and site collections (Office SharePoint Server)

  • Article

Applies To: Office SharePoint Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.

 

Before you can upgrade any sites, you must run Setup and the SharePoint Products and Technologies Configuration wizard on all servers in your server farm. You must also install any language packs that you will need.

  1. On the top link bar, click Operations.

  2. On the Operations page, in the Upgrade and Migration section, click Site content upgrade status.

  3. On the Site Content Upgrade Status page, next to the URL you want to upgrade, click Begin upgrade.

  4. On the Set Target Web Application page, in the Web Application to Upgrade section, if the Web application you want to upgrade is not selected, on the Web Application menu, click Change Web Application.

    On the Select Web Application page, click the Web application that you want to upgrade.

  5. In the New URL for Original Content section, in the Port box, type a port for the new URL.

  6. In the Host Header box, type the host header to use (if needed).

  7. In the Application Pool for New Web Application section, select one of the following:

    • Use existing application pool   If you select this option, select the application pool to use.

    • Create new application pool   If you select this option, in the Application pool name box, type a name, and then select either Predefined or Configurable. If you select Predefined, select the account to use. If you select Configurable, type the account name to use, and then type the password for that account.

  8. In the Security Configuration section, under Authentication Provider, select either Negotiate (Kerberos) or NTLM, depending on your environment.

  9. In the Content Databases section, select either Automatic database name selection or Manually set database names.

  10. In the SSP Database Settings section, in the SSP Database Name box, type the name for the Shared Services Provider database.

  11. In the Search Database Name box, type the name for the Search database.

  12. In the Index Server section, in the Index Server list, click the index server to use.

  13. Click OK.

    An Operation in Progress page appears while the new Web application is created.

  14. On the Site Collection Upgrade page, select the check boxes next to the sites you want to upgrade, and then click Upgrade Sites.

  15. On the Sites Selected for Upgrade page, verify the number of site collections, storage used, originating database, and target database, and then click Continue.

    The Upgrade Running page opens, and upgrade runs for the selected site collections. This may take a few minutes, or a few hours, depending on how many site collections you have selected and how large the site collections are.

  16. To see updated status reflected on this page, click Refresh.

    If upgrade fails or reports issues, you can refer to the log files for more information.

    • The Upgrade.log file and the trace log file are located at %windir%\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS.

    • The trace log is named in the following format: Computer_name-YYYYMMDD-HHMM.log, where YYYYMMDD is the date and HHMM is the time, for example, Server1-20061105-1241.log.

  17. When the upgrade process has completed (upgrade is complete when the Status has changed to No job pending), click Continue to return to the Central Administration home page.