Export (0) Print
Expand All
2 out of 4 rated this helpful - Rate this topic

Deploy Service Pack 1 for Project Server 2010

Project Server 2010

Published: June 28, 2011

This article contains guidance for IT professionals managing the deployment of the Microsoft Project Server 2010 Service Pack 1 (SP1) update to a Project Server 2010 deployment.

In this article:

Overview of Microsoft Project Server 2010 Service Pack 1

The Microsoft Project Server 2010 Service Pack 1 (SP1) package contains updates that are specific to Project Server 2010 and also SP1 updates for Microsoft SharePoint Server 2010 (which is an installation requirement for Project Server 2010).

The Microsoft Project Server 2010 SP1 package contains the following:

  • Previously unreleased SharePoint Server 2010 fixes that were made specifically for this service pack. In addition to general product fixes, these fixes include improvements in stability, performance, and security.

  • Previously unreleased Project Server 2010 fixes that were made specifically for this service pack. In addition to general product fixes, these fixes include improvements in stability, performance, and security.

  • All the SharePoint Server 2010 cumulative updates that have been released through April 2011.

  • All the Project Server 2010 cumulative updates that have been released through April 2011.

To download the Microsoft Project Server 2010 SP1 package, see Description of Project Server 2010 Service Pack 1 (http://go.microsoft.com/fwlink/p/?LinkId=220028).

For detailed information about the Windows Installer .MSP files that are available in the Microsoft Project Server 2010 SP1 package, see the "Microsoft SharePoint and Project Server 2010 SP1" section of Technical details about the SharePoint 2010 and Office Server 2010 SP1 releases. This KB article also includes information about each SharePoint Server 2010 and Office Server 2010 SP1 package.

For a detailed overview of the Service Pack 1 updates for Project Server 2010 and Microsoft Project 2010, see the TechNet Webcast: Information about Project 2010 and Project Server 2010 Service Pack 1 on the Microsoft World Wide Events site.

For detailed information about features and fixes that are available in SharePoint Server 2010, see the white paper Service Pack 1 for SharePoint Foundation 2010 and SharePoint Server 2010 (http://go.microsoft.com/fwlink/p/?LinkId=221773).

note Note:

The June 2011 Project Server Cumulative Update was released the same date as the Project Server 2010 Service Pack 1 update. We recommend that you install both. The June 2011 Project Server Cumulative Update contains several fixes and improvements that are not contained in the Project Server 2010 Service Pack 1 update. You can install the June 2011 CU before or after you install the Service Pack 1 Update. For more information about the June 2011 Cumulative Update, see Description of the Project Server 2010 cumulative update refresh package (Project server-package): June 30, 2011 (http://support.microsoft.com/kb/2536600). For more information about other Project Server 2010 cumulative updates, see the Updates for Project Server 2010 Resource Center (http://go.microsoft.com/fwlink/p/?LinkID=209620).

Important Important:

If you installed a version of the Project Server 2010 June 2011 cumulative update that you downloaded prior to June 30, 2011, you must download and install the June 30, 2011 version of this cumulative update. The build number of the Project Server 2010 June 30, 2011 cumulative update package is 14.0.6106.5002. See Description of the Project Server 2010 cumulative update refresh package (Project server-package): June 30, 2011 (http://support.microsoft.com/kb/2536600) to download this cumulative update. After installing the cumulative update, ensure that you run the SharePoint Products Configuration Wizard as you typically would when installing a cumulative update. For more information about installing Project Server 2010 cumulative updates, see Deploy cumulative updates (Project Server 2010).

note Note:

Because SharePoint Server 2010 Service Pack 1 is installed with the Project Server 2010 Service Pack 1 package, we also recommend that you install the SharePoint Server 2010 June 30, 2011 cumulative update. For a download and for more information, see Description of the SharePoint Server 2010 cumulative update refresh package (SharePoint server-package): June 30, 2011. For more information about SharePoint Server 2010 updates, see the Updates for SharePoint 2010 Products Resource Center.

Update Project 2010 desktop clients to Service Pack 1

For information about how to update Microsoft Project Professional 2010 and Project 2010 desktop clients to Service Pack 1, see the Office Resource Kit TechNet article, Apply Office 2010 Service Pack 1 (SP1). For a description of Project 2010 Service Pack 1, see the knowledge base article, Description of Project 2010 SP1.

Key Project Server 2010 fixes and improvements for Microsoft Project Server 2010 Service Pack 1

In total, over 200 issues are fixed in the Service Pack 1 updates for both Project 2010 and Project Server 2010. Additionally, the Service Pack 1 updates contain a rollup of all fixes that were shipped in all previous cumulative updates. The following are four frequently requested improvements that were included with the Service Pack 1 updates for Project Server 2010 and Project Professional 2010.

  • Additional supported browsers for Project Web App team member pages

  • Improvements to project scheduling in Project Web App

  • Time-phased support for manually scheduled tasks

  • Enhancements for synchronizing Project tasks to SharePoint task lists

  • Support for the use of Microsoft SQL Server 2012 to host farm databases

To see a complete list of all fixes that are included in Microsoft Project Server 2010 Service Pack 1, see the Microsoft SharePoint 2010 and Office Servers Service Pack 1 Changes.xlsx package.

Additional supported browsers for Project Web App team member pages

An important improvement included in Microsoft Project Server 2010 Service Pack 1 is the support of additional browsers for team member pages in Project Web App. This improvement enables team members to view the tasks to which they are assigned, submit their status, and submit timesheets not only through the supported Internet Explorer browsers, but also through Firefox, Apple Safari, and Google Chrome browsers. After you apply Microsoft Project Server 2010 Service Pack 1, team members' pages will be supported in all of the following browser environments:

  • Internet Explorer 9 (32-bit) on Windows 7, Windows Vista, and Windows Server 2008

  • Internet Explorer 8 (32-bit) on Windows 7, Windows Vista, and Windows Server 2008

  • Internet Explorer 7 (32-bit) on Windows Vista, Windows XP, and Windows Server 2003

  • Firefox 3.6.8+ on Mac OS X v10.6, Windows 7 (32-bit/64-bit), Windows Vista SP2, Windows XP SP3, Windows Server 2003 and UNIX/Linux

  • Google Chrome 6.0 on Windows 7

  • Apple Safari 5 on Mac OS X v10.6

The team member pages that are supported with these additional browsers include the following:

  • Project Web App (PWA) main default page (default.aspx)

  • All pages in the "My Work" section in the Quick Launch. This includes the following:

    • Tasks

    • Timesheets

    • Issues and Risks

note Note:

Additional pages in Project Web App (for example, Project Center, Portfolio Analysis) are only accessed through the Internet Explorer browsers listed earlier. If you are using a Macintosh-based computer, see Accessing Project Web App and Project Professional from a Macintosh-based computer for more information about how to access these Project Web App pages.

For more information, see the Microsoft Project Team blog post, Project 2010 SP1 – Multi-Browser Support.

Improvements to project scheduling in Project Web App

Applying Microsoft Project Server 2010 Service Pack 1 enables Project Web App users to edit projects that contain Fixed Work or Effort Driven tasks. In the original release of Project Server 2010, Project Web App users are able to create and edit project plans. However, one limitation with this new capability was that projects that contained Fixed Work or Effort Driven tasks could not be edited through Project Web App. Projects that contained these kinds of tasks could only be edited through Project Professional 2010. Service Pack 1 removes this limitation.

For more information, see the Microsoft Project Team blog post, Project 2010 SP1 – Improvements to Project Scheduling in Project Web App.

Time-phased support for manually scheduled tasks

Applying Microsoft Project Server 2010 Service Pack 1 lets users edit time-phased data for manually scheduled tasks in Project Web App. Manually scheduled tasks are part of the new “User-Controlled Scheduling” feature that was introduced in Project Server 2010 to provide users more control over how tasks are scheduled. Manually scheduled tasks are not affected by the scheduling engine and only move if you manually update them, providing you more control over you schedule. However, until now, users were unable to edit time-phased data within manually scheduled tasks. For example, in manually scheduled tasks, you could not edit work values in the Task Usage View in Project Web App, or report time-phased data in task statusing. Unlike Auto Scheduled tasks, the fields are read-only for manually scheduled tasks. In Project Server 2010, the SP1 update enables all tasks (Auto and manually scheduled) to use time-phased tracking (hours of work done per period) in My Work or Single Entry Mode.

note Note:

This functionality is also available in Project 2010 clients through the Office 2010 Service Pack 1 update.

For more information, see the Microsoft Project Team blog post, Project 2010 SP1 – Time-phased Support for Manually Scheduled Tasks.

Enhancements for synchronizing Project tasks to SharePoint task lists

Updating Project Professional 2010 to Service Pack 1 enables client users to synchronize automatically scheduled tasks when they are using the Synchronize to SharePoint feature. The Sync to SharePoint feature lets you synchronize tasks from a project file with a SharePoint task list in Project Professional 2010. One of the caveats of the feature has been that you are limited to synchronizing only with manually scheduled tasks. When you apply the Service Pack 1 update to Project Professional 2010, you are able to synchronize both manually scheduled and automatically scheduled tasks.

For more information, see the Microsoft Project Team blog post, Project 2010 SP1 – Enhancements to Synch to SharePoint Task List.

note Note:

Note that this feature is available to Project Professional 2010, and will only be enabled if you apply the Service Pack 1 update to the Project Professional 2010 desktop client. For more information about how to update Project Professional 2010 with the Service Pack 1 update, see the Office Resource Kit TechNet article, Apply Office 2010 Service Pack 1 (SP1).

SQL Server 2012 support

Applying both the Project Server 2010 Service Pack 1 and the SharePoint Server 2010 Service Pack 1 updates to the Project Server 2010 installations in your farm allows you to use the 64-bit version of SQL Server 2012 to host your Project Server 2010 databases. Without the updates, only the 64-bit versions of SQL Server 2005 and SQL Server 2008 are supported.

note Note:

For more information about SQL Server 2012, see the SQL Server 2012 home page on Microsoft TechNet.

Before you begin

Before you install Microsoft Project Server 2010 Service Pack 1, take these recommended actions:

  • Back up the farm before you start the installation. Microsoft Project Server 2010 Service Pack 1 cannot be uninstalled, so if you have to return to your previous deployment, you will have to restore the farm backup. For more information about how to perform backups, see Back up and restore databases (Project Server 2010).

    Important Important:

    The Project Server 2010 Service Pack 1 update cannot be uninstalled.

  • Stop the World Wide Web Publishing Service on all the Web servers to disconnect all the users from the server farm. In server farms with multiple front-end Web servers, end-users will be unable to browse the Web sites when files and databases have been updated on the first front-end Web server while the other Web servers still contain previous files and databases.

  • As a best practice, stop the Microsoft Project Server Queue Service 2010 before you install an update. This ensures that nothing processes while the update is being installed.

Install Service Pack 1 on a Project Server 2010 basic installation

To install Microsoft Project Server 2010 Service Pack 1 on a basic installation of Project Server 2010 (that is, the single-server installation that has Microsoft SQL Server 2008 Express), do the following:

  1. Disconnect users from the server by stopping the World Wide Web Publishing service on the server.

  2. Stop the Microsoft Project Server Queue Service 2010.

  3. Download the Microsoft Project Server 2010 Service Pack 1 update file. Run the file. On the Microsoft Software License Terms page, read the terms and then click Click here to accept the Microsoft Software License Terms. Click Continue to install the update files.

  4. When installation of the files is finished, on the confirmation page, click OK.

  5. Run the SharePoint Products Configuration Wizard to complete the installation. To do so, click Start, click All Programs, click Microsoft SharePoint 2010 Products, and then click SharePoint Products Configuration Wizard and complete the steps in the wizard.

  6. On the Configuration Successful page, click Finish.

  7. Make the server available to users by manually starting the World Wide Web Publishing Service.

Update a Project Server 2010 farm installation with Service Pack 1

For Project Server 2010 farm deployments, use the following procedures to install Microsoft Project Server 2010 Service Pack 1 on each server in your farm.

Installation steps

To update a Project Server 2010 farm deployment with Microsoft Project Server 2010 Service Pack 1, you must follow these general steps:

  1. On each server in the farm, install the Microsoft Project Server 2010 Service Pack 1 files.

  2. After installation of the Service Pack 1 update files is completed on all servers on the farm, on one server in the farm (preferably the one hosting the SharePoint Central Administration Web site), run the SharePoint Products Configuration Wizard to complete the installation on that server.

  3. Run the SharePoint Products Configuration Wizard on each remaining server on the farm, one at a time.

We recommend that you use the farm administrator account to install the update and run the SharePoint Products Configuration Wizard. If you use a different account to install the update, that account must be a domain account that has the following rights and permissions:

  • Member of the Administrators group on the Web server computer

  • Member of the Administrators group on the Microsoft SQL Server computer

You can install the update by logging on to the server directly or by connecting through a terminal services console session.

Install Microsoft Project Server 2010 Service Pack 1 in a farm deployment

  1. Disconnect users from the server farm by stopping the World Wide Web Publishing Service on all Web servers.

  2. Go to each application server and stop the Microsoft Project Server Queue service 2010 (if available).

  3. Download Microsoft Project Server 2010 Service Pack 1.

  4. On a server in the farm, run the Microsoft Project Server 2010 Service Pack 1 update file. At the Microsoft Software License Terms page, read the terms and then click Click here to accept the Microsoft Software License Terms. Click Continue to search for files that have to be updated, and to install the update files.

  5. When installation of Microsoft Project Server 2010 Service Pack 1 finishes, on the “The installation is complete” message box, click OK.

  6. You must run setup to install new Microsoft Project Server 2010 Service Pack 1 update files for every server in your server farm. If you have multiple servers in your server farm, move to each server in your Project Server farm and repeat steps 2–5 to install the files.

    note Note:

    Do not run the SharePoint Products Configuration Wizard on any of the servers at this point.

  7. After installing the Project Server 2010 Service Pack 1 binary files on all servers on the farm, you will have to run the SharePoint Products Configuration Wizard on each server on the farm to complete the installation.

    note Note:

    We recommend that you complete the Microsoft Project Server 2010 Service Pack 1 installation first on the application server that is hosting the Central Administration Web site, then on the other application servers, and then on the front-end Web servers.

    If you host your Central Administration Web site on a front-end Web server, finish the Microsoft Project Server 2010 Service Pack 1 update installation instead on that front-end Web server, then the application servers, and finally on the remaining front-end Web servers.

    On the server that you selected in the previous step, run the SharePoint Products Configuration Wizard to complete the installation. To run the SharePoint Products Configuration Wizard, click Start, click All Programs, click Microsoft SharePoint 2010 Products, and then click SharePoint Products Configuration Wizard and complete the steps in the wizard.

    Important Important:

    All Microsoft Project Server 2010 Service Pack 1 installation files should be installed to all servers in the farm before you run the SharePoint Products Configuration Wizard.

  8. On the Configuration Successful page, click Finish.

    Important Important:

    It is important that the SharePoint Products Configuration Wizard perform its configuration procedures on only one computer at a time. The only exception is if you have detached your content databases and upgraded them before you reattach them to the server farm.

  9. When the Microsoft Project Server 2010 Service Pack 1 installation and configuration is complete on all the servers in the server farm, make the Web servers available to users by manually starting the World Wide Web Publishing Service on each server on which you manually stopped the service.

Considerations when you are updating a Project Server 2010 farm deployment to Service Pack 1

It is important to remember that Project Server 2010 Service Pack 1 also contains Service Pack 1 updates for SharePoint Server 2010, and both are applied automatically during the installation process. For Project Server 2010 Service Pack 1 to be applied successfully, the following two processes have to occur:

  • Patching process: This process updates the SharePoint Server 2010 and Project Server 2010 binary files on the server.

  • Upgrade process: This process upgrades the SharePoint Server 2010 and Project Server 2010 databases. The upgrade process is executed only when you run the SharePoint Products Configuration Wizard.

    Important Important:

    The Project Server 2010 Service Pack 1 update does not prompt you to run the SharePoint Products Configuration Wizard after the patching process. After the patching process (installation of the Service Pack 1 binary files) has completed on all servers in your farm, you can then run the SharePoint Products Configuration Wizard on each server.

However, a scenario may exist where administrators want to first have the Project Server 2010 Service Pack 1 features and fixes available in their environment, and temporarily bypass updating SharePoint Server 2010. For example, this can occur if the administrator has to schedule a longer down-time period to upgrade the SharePoint Server 2010 databases (which can be very large) to SP1.

This scenario can be achieved if you install Project Server 2010 Service Pack 1 binary files and upgrade only the Project Server 2010 databases. This can be done through the following steps.

  1. On the server, in the Administrative Tools Services page, stop all of the following services:

    • SharePoint 2010 Timer

    • SharePoint 2010 Administration

    • SharePoint 2010 Tracing

    • Microsoft Project Server Queue Service 2010

    • Microsoft Project Server Events Service 2010

  2. Stop Internet Information Services (IIS) on the server.

  3. On the server, run the Project Server 2010 Service Pack 1 update to install the Project Server 2010 and SharePoint Server 2010 Service Pack 1 binary files.

    Important Important:

    Do not run the SharePoint Products Configuration Wizard. Running the wizard at this point upgrades both the SharePoint Server 2010 and Project Server 2010 databases.

  4. Restart the services on the server:

    • SharePoint 2010 Timer

    • SharePoint 2010 Administration

    • SharePoint 2010 Tracing

    • Microsoft Project Server Queue Service 2010

    • Microsoft Project Server Events Service 2010

  5. Restart IIS on the server.

  6. On the remaining servers in your farm, repeat steps 1-5.

  7. Now that you have installed the Project Server 2010 Service Pack 1 binary files on all servers in the farm, you have to upgrade the Project Server 2010 databases by using a Windows PowerShell cmdlet. On an application server on the farm, open Windows PowerShell and run the following cmdlet: Upgrade-SPProjectWebInstance. This cmdlet creates upgrade changes to the specified Project Web App site in a Microsoft SharePoint Server 2010 farm. You can use the required -URL option to specify the location of the Project Web App instance that performs the database upgrade. For example, Upgrade-SPProjectWebInstance –URL http://Contoso/pwa. After running the cmdlet, wait for the confirmation message “Upgrade of single project site complete”. For more information about this Windows PowerShell cmdlet, see Upgrade-SPProjectWebInstance.

    note Note:

    The Upgrade-SPProjectWebInstance Windows PowerShell cmdlet is only required to be run on a single application server in your farm. You are not required to run this command on any additional servers in your farm.

  8. On the application server on which you ran the Windows PowerShell cmdlet, in a Command Prompt window, run IISreset /noforce to restart IIS.

Note that, although the SharePoint Server 2010 binary files are updated to SP1, the farm will still function even if the SharePoint Server 2010 databases are not upgraded to SP1 (running in "compatibility mode"). SharePoint Server 2010 features and fixes that are available in SP1 are not available until the SharePoint Server 2010 databases are upgraded to Service Pack 1 (by running the SharePoint Products Configuration Wizard).

You can verify that SharePoint Server 2010 is running in backward compatibility mode by looking at the Manage Database Upgrade Status page. This page shows you the status of databases used in your server farm. If the SharePoint Server 2010 environment is running in backward compatibility mode, the SharePoint Configuration database, and additional content databases, shows a status of “Database is in compatibility range and upgrade is recommended”. Once the SharePoint Server 2010 databases are upgraded to match the SharePoint Server 2010 binaries, the status for these databases should be “No action required”.

note Note:

Running an environment in backward compatibility mode is only intended to be a temporary convenience to help administrators when they deploy the Service Pack 1 update. We suggest that you not run in backward compatibility mode for a long time.

For more information about updates and Backwards Compatibility mode, see Install a software update (SharePoint Server 2010).

Update Project Server 2010 Language Packs with Service Pack 1

The Microsoft 2010 Office Servers Language Pack Service Pack 1 package contains SP1 updates for Office Server 2010 language packs, including SharePoint Server 2010 and Project Server 2010 language packs.

Running the Microsoft 2010 Office Servers Language Pack SP1 package detects any language packs (Project Server 2010 or SharePoint Server 2010) on the server and installs them as needed. For example, your Project Server 2010 English-US installation on the server contains the SharePoint Server 2010 French-France Language Pack, and the Project Server 2010 French-France Language Pack. You will have to install the Microsoft 2010 Office Servers Language Pack SP1 package to update the SharePoint Server 2010 French-France Language Pack and the Project Server 2010 French-France Language Pack.

To download the Microsoft 2010 Office Servers Language Pack SP1 package, see Description of Microsoft 2010 Server Language Pack Service Pack 1 (SP 1) (http://go.microsoft.com/fwlink/p/?LinkId=220137).

The following is the recommended order for installing the Service Pack 1 updates (the Microsoft Project Server 2010 SP1 package and the Microsoft 2010 Office Servers Language Pack SP1 package) on a Project Server 2010 farm with language packs.

  1. On all servers in the farm, install the Microsoft Project Server 2010 SP1 package, but do not run the SharePoint Products Configuration Wizard.

  2. On all servers in the farm, install the Microsoft 2010 Office Servers Language Pack SP1 package, but do not run the SharePoint Products Configuration Wizard.

  3. On one server on the farm (preferably the server hosting the Central Administration site), run the SharePoint Products Configuration Wizard to complete the installation on that server.

  4. Run the SharePoint Products Configuration Wizard on all remaining servers on the farm.

Verify the Service Pack installation

To verify the success of the installation, you can use any of the following methods after you install the service pack update:

  • View the currently installed updates in Control Panel   In Control Panel, click Programs, and then click View installed updates. Look under Microsoft Project Server 2010 for ”Microsoft SharePoint and Project Server 2010 Service Pack 1 (SP 1)” to verify that the update has been installed. The same update information should be listed under Microsoft SharePoint Server 2010.

    note Note:

    If you are running SharePoint Server 2010 in backward compatibility mode and your SharePoint Server 2010 databases are not upgraded to Service Pack 1, the View Installed Updates page still shows “Microsoft SharePoint and Project Server 2010 Service Pack 1 (SP 1)” as an installed update. You can determine whether the SharePoint Server 2010 databases are running in compatibility mode by checking the Manage Database Upgrade Status page on the Central Administration Web site.

  • Check the upgrade status in SharePoint Central Administration   In Central Administration, click Upgrade and Migration, and then click Check upgrade status. Look for a Status of Succeeded at the time when the update was installed.

  • Review the upgrade log file and verify that the updates to the Web applications were successful. The location of the upgrade log file is shown on the Upgrade Status page in the Selected upgrade session details section.

note Note:

Checking the database version is not a reliable method of determining whether an update was installed correctly. If no database updates are included in the update, the database version does not change.

Known Issue: Page cannot load when you attempt to edit an existing rule

After you apply the Project Server 2010 SP1 update, a known issue may occur in your environment if you have defined approval rules. After you apply the SP 1 update, if you attempt to edit an existing rule, the page cannot load, and a message box displays a general error message: Error – An unexpected error has occurred.

If you view the ULS logs, a corresponding error message appears: ‘RULE_AUTOMATIC_PUBLISH’ in table ‘Rules’ is DBNull.

This error occurs because the Project Server 2010 Service Pack 1 update adds a new column, RULE_AUTOMATIC_PUBLISH, to the MSP_Rules table, and all existing rows are left with a null value.

New rules created after you apply the Project Server 2010 Service Pack 1 update are not affected. (They can be edited.)

This error is fixed in the June 2011 Cumulative Update for Project Server 2010. This update is currently available for download and installation. For more information about Project Server 2010 Cumulative Updates, see the Updates for Project Server 2010 Resource Center (http://go.microsoft.com/fwlink/p/?LinkID=209620).

note Note:

We recommend that you install the June 2011 Project Server 2010 cumulative update. It will be available the same date as the Project Server 2010 Service Pack 1 update.

As a workaround for this issue, you can delete and then re-create the approval rule.

Another workaround is to resolve the issue by making an update directly to the MSP_RULES table in the Project Server 2010 Published database that holds the rules definitions. Running the following SQL query on the Project Server 2010 Published database changes the null values in the column to false.

Update MSP_Rules 
Set RULE_AUTOMATIC_PUBLISH=’False’

For more information about additional known issues that you may encounter when you install the Project Server 2010 Service Pack 1 package, see the Knowledge Base article, #2532126 Known issues that you may experience when you install the Microsoft Office 2010 Service Pack 1 and Microsoft SharePoint 2010 Service Pack 1 (http://support.microsoft.com/kb/2532126).

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.