Export (0) Print
Expand All

In-place upgrade to Project Server 2010

 

Applies to: Project Server 2010

Topic Last Modified: 2011-09-10

importantImportant
Upgrading from the Project Server 2010 public Beta to the Project Server 2010 released version is explicitly blocked and not supported. This restriction applies to both the in-place and database-attach upgrade methods.

When you run an in-place upgrade from Microsoft Office Project Server 2007 to Microsoft Project Server 2010, the configuration data for the farm and all the content in the farm is upgraded on the existing hardware, in a fixed order. When you start the in-place upgrade process, Setup takes the entire farm offline and the Web sites and Microsoft Project Web App sites are unavailable until the upgrade is finished, and then Setup restarts the server. After you begin an in-place upgrade, you cannot pause the upgrade or roll back to the previous version.

You can also choose to upgrade only your project data and optionally your Project Web App site data to another server, which would be required if the in-place upgrade requirements mentioned later in this article are not met. For more information about other Project Server 2010 upgrade methods, see Project Server 2010 upgrade overview.

importantImportant
You must be running Office Project Server 2007 with SP2 with the October 2009 Cumulative Update in a 64-bit Windows Server 2008 environment to perform an in-place upgrade to Project Server 2010. You must also be running a 64-bit version of Microsoft SQL Server 2008 Service Pack 1 with Cumulative Update 2, or the 64-bit version of Microsoft SQL Server 2005 Service Pack 3 with Cumulative Update 3.

In this article:

By using the procedures in this article, you install Project Server 2010 and upgrade Project Web App and all the project data in the environment. Microsoft SharePoint Server 2010 Enterprise version is a prerequisite for Project Server 2010 and must be installed on all servers in the farm also. We recommend that you try out the upgrade process on a test environment before you attempt to upgrade your production environment.

When upgrading a server farm, install and configure the new version to the servers in the following order:

  1. Install SharePoint Server 2010 on all servers in the server farm.

  2. Install Project Server 2010 on all servers in the server farm.

  3. Run the SharePoint Products and Technologies Configuration Wizard on the server that contains the SharePoint Central Administration Web site.

    To determine which server is running SharePoint Central Administration, open the Servers in Farm page (http://server_name:adminport/_admin/farmservers.aspx) and note which server or servers have Central Administration services running. Perform this step before you install SharePoint Server 2010, while SharePoint Central Administration for Office Project Server 2007 is still available.

    noteNote
    If you have multiple servers running SharePoint Central Administration, pick one and use that as the initial server on which to run upgrade. After you have completed the process on that one, you can continue with any other servers running SharePoint Central Administration.
  4. Run the configuration wizard on the remaining front-end Web servers and application servers in the farm in any order.

noteNote
It is important that you only run the SharePoint Products Configuration Wizard after the installation files for both SharePoint Server 2010 and Project Server 2010 are on all servers in the farm. Running it prior to this can cause data inconsistencies on the farm.

It is recommended that you back up your environment before you begin the upgrade process. For more information, see Back up and restore a Project Server 2007 farm.

To deploy Project Server 2010 on a server farm, you must provide credentials for several different accounts.

The following table describes the accounts that are used to install and configure Project Server 2010.

importantImportant
Although it is a good practice to install Project Server 2010 by using the least-privileged administration method, you cannot perform an in-place upgrade by using this method. To run Setup and the SharePoint Products Configuration Wizard, you must have administrator access to the local computer and to Microsoft SQL Server.

 

Account Purpose Requirements

SQL Server service account

The SQL Server service account is used to run SQL Server. It is the service account for the following SQL Server services:

  • MSSQLSERVER

  • SQLSERVERAGENT

If you do not use the default SQL Server instance, these services will be shown as the following:

  • MSSQL$InstanceName

  • SQLAgent$InstanceName

Use either a Local System account or a domain user account.

If you plan to back up to or restore from an external resource, permissions to the external resource must be granted to the appropriate account. If you use a domain user account for the SQL Server service account, grant permissions to that domain user account. However, if you use the Network Service or the Local System account, grant permissions to the external resource to the machine account (domain_name\SQL_hostname$).

Setup user account

The Setup user account is used to run the following:

  • Setup

  • The SharePoint Products Configuration Wizard

  • Domain user account.

  • Member of the Administrators group on each server on which Setup is run.

  • SQL Server login on the computer that runs SQL Server.

  • Member of the following SQL Server security roles:

    • securityadmin fixed server role

    • dbcreator fixed server role

If you run Windows PowerShell cmdlets that affect a database, this account must be a member of the db_owner fixed database role for the database.

Server farm account or database access account

The server farm account is used to perform the following tasks:

  • Configure and manage the server farm.

  • Act as the application pool identity for the SharePoint Central Administration Web site.

  • Run the Windows SharePoint Services Timer service.

  • Domain user account.

Additional permissions are automatically granted for the server farm account on Web servers and application servers that are joined to a server farm.

The server farm account is automatically added as a SQL Server login on the computer that runs SQL Server. The account is added to the following SQL Server security roles:

  • dbcreator fixed server role

  • securityadmin fixed server role

  • db_owner fixed database role for all databases in the server farm

You must have the following software and hardware installed and configured to perform the steps in this article.

 

Requirement Details

Operating System

Windows Server 2008 R2 and Windows Server 2008 with Service Pack 2 (SP2) (64-bit)

For more information about migrating to a 64-bit operating system, see Migrate an existing server farm to a 64-bit environment (Project Server 2007).

Project Server

Project Server 2007 Service Pack 2 with the October 2009 Cumulative Update applied

importantImportant
You must apply both Service Pack 2 and the October 2009 Cumulative update. If you attempt to execute and in-place upgrade without these updates, it can result in an unrecoverable state.
For information about installing Office Project Server 2007 SP2, see Deploy Service Pack 2 for Office Project Server 2007.
For more information about installing cumulative updates, see Deploy cumulative updates (Project Server 2007).

SQL Server

64-bit version of SQL Server 2005 Service Pack 2 with Cumulative Update 3, OR

64-bit version of SQL Server 2008 Service Pack 1 with Cumulative Update 2

Your databases must be hosted on either of these two 64-bit versions of SQL Server. SQL Server 2000 and non-64-bit versions are not supported for Project Server 2010.

For more information about moving databases to a 64-bit version of SQL Server, see Migrate an existing server farm to a 64-bit environment a 64-bit environment (Project Server 2007).

Windows SharePoint Services

Windows SharePoint Services 3.0 with SP2

Although not a requirement, as a best practice, you may want to match the cumulative update level of Office Server 2007 applications.

If you are using the in place upgrade method to upgrade a Office Project Server 2007 farm that is integrated with Office SharePoint Server 2007, then Office SharePoint Server 2007 has this additional requirement:

 

Requirement Details

Service Pack Level

Office SharePoint Server 2007 with SP2

For information about installing Office SharePoint Server 2007 SP2, see Deploy software updates for Office SharePoint Server 2007.

Before you can upgrade, you must run the prerequisite installer successfully on each server that has Office Project Server 2007 installed. A prerequisite installer is available to install software needed to support Project Server 2010.

To run the prerequisite installer
  1. From the product disc, open the installation folder and run splash.hta to open the Start page. On the Start page, click Install software prerequisites to run Prerequisite Installer.

    The SharePoint Products and Technologies 2010 Preparation tool opens.

  2. Click Next.

  3. On the License Terms page, select the I accept the terms of the License Agreement(s) check box, and then click Next.

    The tool runs, installing and configuring required software.

  4. Click Next.

  5. On the Installation Complete screen, verify that each prerequisite is listed as successfully installed or already installed.

  6. Click Finish to close the wizard.

After all of the prerequisites are installed, you can run the SharePoint Server 2010 Setup.exe on all servers in your server farm.

importantImportant
If you are running an in-place upgrade on a server farm, disconnect all the users from the server farm by stopping the World Wide Web Publishing Service (W3SVC) on all front-end Web servers. If you allow users in a server farm to connect after the files and databases have been updated on one Web server, but before the other Web servers have been updated, users will not be able to browse the Web sites. You should also stop the Project Queuing service on all application servers. This action ensures that nothing will be processed by Project Server 2007 while the upgrade is happening.
To install the new version of SharePoint Server 2010
  1. Run Splash.hta to open the Start page. On the Start page, click Install SharePoint Server.

  2. On the Enter your Product Key page, type your product key for SharePoint Server 2010 Enterprise edition, and then click Continue.

  3. 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.

  4. On the Upgrade earlier versions page, click Install Now.

  5. Setup runs and installs SharePoint Server 2010.

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

    importantImportant
    Do not run the SharePoint Products Configuration Wizard at this time. You will be directed to run it later when all installation files for both applications are installed on all Web and application servers in the server farm.

If you require any language template packs for SharePoint Server 2010, install them now. For more information, see Install available language template packs (SharePoint Server 2010).

After SharePoint Server 2010 is installed to all servers in the farm, you can run the Project Server 2010 Setup.exe on all servers in your server farm.

To install the new version of Project Server 2010
  1. Run Splash.hta to open the menu page. Click Install Project Server.

  2. On the Enter your Product Key page, type your product key for Project Server 2010, and then click Continue.

  3. 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.

  4. On the Upgrade earlier versions page, click Install Now.

  5. Setup runs and installs Project Server 2010.

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

If you are upgrading a single server, you can run the SharePoint Products and Technologies Configuration Wizard on only that server and start upgrading content. If you are upgrading a server farm, first run the SharePoint Products and Technologies Configuration Wizard on the server running SharePoint Central Administration. Then go to each server in the farm and run the wizard. It is important to upgrade SharePoint Central Administration before you attempt to upgrade any other content in the farm, and completing the wizard on the server running SharePoint Central Administration allows you to do so.

Be sure that you have installed any language template packs before you run the SharePoint Products and Technologies Configuration Wizard.

CautionCaution
After you run the configuration wizard, Office Project Server 2007 will no longer be available. You cannot pause or roll back the setup and upgrade process. Be sure that you have a current and valid backup of your environment before you proceed with installing Project Server 2010.
importantImportant
When you run the SharePoint Products and Technologies Configuration Wizard, make sure that the wizard completely finishes running before you attempt to run it on another server. The wizard will also start the Upgrade Timer job, and this must completely finish running as well. You should inspect the upgrade logs for completion of the upgrade session on the server before attempting to run the wizard on another server.
To run the SharePoint Products and Technologies Configuration Wizard
  1. Click Start, point to All Programs, click SharePoint Products, and then click SharePoint 2010 Products Configuration Wizard.

  2. In the SharePoint Products 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 Services v4, and the SharePoint Timer Service v4 may need to be restarted or reset during configuration.

  3. Click Yes to continue with the wizard.

  4. On the Specify Farm Settings page, in the Passphrase box, type a passphrase and in the Confirm passphrase box, type the same passphrase.

    The passphrase should be at least 8 characters and should contain at least three of the following four character groups:

    • English uppercase characters (from A through Z)

    • English lowercase characters (from a through z)

    • Numerals (from 0 through 9)

    • Non-alphabetic characters (such as !, $, #, %)

  5. On 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 SharePoint Central Administration for Project Server 2010.

  6. 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.

    • If this is the only server in your farm, or if you have already run Setup on all of the servers in your farm, click OK to continue with the wizard.

    • If you have not yet run Setup on all of the servers in your farm, run Setup on the remaining servers now, and then return to this server and click OK to continue with the wizard.

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

  7. On the Configuration Successful, Upgrade in Progress page, review the settings that have been configured, and then click Finish.

    The SharePoint Products and Technologies Configuration Wizard closes and the Upgrade Status page opens. You might be prompted to enter your user name and password before the Upgrade Status page will open. The upgrade process might take a while to complete, depending on how much data is in your farm.

  8. If you are upgrading a server farm, you can now complete the SharePoint Products and Technologies Configuration Wizard on the other servers in the farm.

  9. After upgrade is completed successfully for all sites, if you stopped the World Wide Web Publishing Service (W3SVC) on all front-end Web servers before the upgrade, manually start the World Wide Web Publishing Service on the front-end Web servers to make the Web servers available to users. Also verify that the Project Queuing service has restarted on all Project application servers in the farm. If it has not, restart it.

If you are upgrading a Office Project Server 2007 farm that is integrated with Office SharePoint Server 2007, you can monitor the upgrade process for each site from the Upgrade Status page in SharePoint Central Administration or by using the localupgradestatus operation in Stsadm.exe. For more information, see Verify upgrade and review upgraded sites (SharePoint Server 2010).

If upgrade fails or reports issues, you can refer to the log and error files for more information. Upgrade logs files are generated to the following default location: C: \Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Logs

Each upgrade log file will be stamped with the date and time that it was generated.

There are two types of possible failures that you might find in the log:

  • Failures in the psconfig portion of the upgrade: You can restart the SharePoint Products and Technologies Configuration Wizard to restart the upgrade.

  • Failures in the SPTimer portion of the upgrade: You can restart upgrade by running the following command in a Command Prompt window:

    Psconfig -cmd -upgrade -inplace v2v -force -wait

After you upgrade to Project Server 2010 by using the in-place upgrade method, you may see the following error if you check for missing server-side dependencies when you run the Health Analyzer tool. The following entry would appear in the Review Problems and Solutions Page of Central Administration Monitoring:

 

Category Title Failing Service

Configuration

Missing server side dependencies.

SPTimerService(SPTimerV4)

You can click the error to display more details:

 

Severity:

1 - Error

Explanation:

MissingSetupFile] File [SiteTemplates\PWA\dwp\OWCViewPart.webpart] is referenced [1] times in the database [WSS_Content], but exists only under Windows SharePoint Services 3.0 setup folder. Consider upgrading the feature/solution which contains this file to the latest version. One or more setup files are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these files.

[MissingSetupFile] File [SiteTemplates\PWA\OWCView.aspx] is referenced [1] times in the database [WSS_Content], but exists only under Windows SharePoint Services 3.0 setup folder. Consider upgrading the feature/solution which contains this file to the latest version. One or more setup files are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these files.

[MissingWebPart] WebPart class [94b5bae7-436c-dcc2-5869-d491181c283b] is referenced [1] times in the database [WSS_Content], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

This error is inconsequential. It appears because the upgraded Content database contains pages and Web Parts that use Office Web Components (OWC), which have been deprecated in Project Server 2010. The presence of OWC Web Parts and pages on the upgraded Content database causes the error message to occur, but it does not prevent your upgrade from completing successfully. Note that most of the OWC features can be found in both the Microsoft Excel client and Excel Services.

For more information about Health Analyzer, see Health monitoring (SharePoint Server 2010).

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