Export (0) Print
Expand All

Deploy Service Pack 2 for Project Server 2010

 

Applies to: Project Server 2010

Topic Last Modified: 2013-12-09

Summary: Deploy the Project Server 2010 SP2 update to an existing Project Server 2010 deployment. This package includes cumulative updates and previous unreleased fixes since June 2011.

In this article:

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

The Project Server 2010 SP2 package contains the following:

  • All cumulative fixes for Project Server 2010 and SharePoint Server 2010 since Service Pack 1, starting with the June 2011 Cumulative Update (CU) and the July 2011 Public Update (PU) all the way through the corresponding April 2013 CU and May 2013 PU.

    importantImportant
    See the “Known Issues with installing Project Server 2010 Service Pack 2” section of this article if you currently have the June 2013 Cumulative Update deployed in your environment.
  • Previously unreleased fixes. In addition to general product fixes, these fixes include improvements in stability, performance, and security.

The Project Server 2010 Service Pack 2 package can be downloaded from the Service Pack 2 for Microsoft SharePoint and Project Server 2010 (KB2687452) page in the Microsoft Download Center.

To view a description of Project 2010 Service Pack 2, see the knowledge base article: Description of Project 2010 SP2. The article also provides you links from which you can download the 32-bit or 64-bit versions of the Project 2010 SP2 update.

The major enhancement provided through the Project Server 2010 Service Pack 2 package is Windows Server 2012 and Windows Server 2012 R2 support for SharePoint Server 2010 and Project Server 2010. Without this service pack, Project Server 2010 was supported only on the Windows Server 2008 and Windows Server 2008 R2 server operating systems.

importantImportant
Due to required changes to the SharePoint Prerequisite Installer, Service Pack 2 cannot be slipstreamed into installation media for use with installation on Windows Server 2012 systems. Installation of SharePoint Server 2010 with Service Pack 2 on Windows Server 2012 systems requires integrated Service Pack 2 installation media, which will be available after Service Pack 2 is released.

The following are key fixes that are included for Project Server 2010 through the Service Pack 2 update:

When tasks are inserted in the middle of the tasks list, renumbering of the work breakdown structure (WBS) codes doesn't update the WBS correctly.

Project Professional may crash when copying and pasting in master project.

If the "Actual costs are always calculated by Project" option is disabled in Project 2010, remaining cost data at the task level can behave unexpectedly when the task is partially complete.

Custom fields not totaling correctly.

In the resource usage view, the timephased section of the grid doesn't always change color correctly to indicate when a resource is over-allocated.

If you have a server project and on the server you have the "Restrict updates to Project Web Access" option enabled, if you reduce work on a task such that it makes a milestone task and then if you set the task to 100% complete and save the project, the task's Start Date is set to NA and work is added to the task. This will also impact correctly publishing the project to the server.

When used in Russian language, Project Enterprise Custom Fields of type Text don't show the value properly in Project Professional.

The locally defined custom fields values appear in the enterprise custom fields.

If any assignment in the project plan has actual exceptions where the start date and the finish date are the same, publishing the project plan may get stuck indefinitely stuck at "93% completed" state.

The number of overdue status report items is incorrect if the system time changes.

Time-phased views of cost resources not displaying correctly.

Pending task updates are not shown on the Task Updates page.

Using the PSI call "QueueAddtoProject" to programmatically add a task to a project can fail if the project plan contains has empty task rows.

If there is a cross-project link between two projects, then custom field values for those tasks are not shown correctly.

When a user attempts to import timesheet data, the import will fail due to an exception which occurs when trying to apply the timephased data.

If you select the option to 'Disable all macros except digitally signed macros' and then restart Project Client, the registry options are set incorrectly, and users are unable to enter task names or update task details.

Late Tasks in Project Professional will not appear correctly in the print preview and in the printed output.

Actual Costs may not be updated correctly in certain situations.

Milestone tasks with non-zero duration can lose their % complete data when other tasks have their % complete changed and the project plan is published.

When editing an assignment with a long contour using the PSI or in Project Web App, the project data could become corrupted, preventing future edits to the project plan.

A user submits actual overtime work through statusing and subsequently the PM approves it. However when the project is opened in WinProj the remaining work is converted to actual work.

The option to create timesheets with "Current Projects" includes all projects, regardless of status. All Completed, Current and Future plans that a user was ever the owner of or had an assignment in, are added to the timesheet.

Using the My Tasks page, a user provides actual work updates for a material resource. However after being applied to the project plan, the actual work value for the assignment is incorrect.

Booting Project 2010 when connected to a Project 2013 server generates a confusing error message.

For months with five Fridays, creating a recurring calendar exception on the last Friday of every month can select the fourth Friday instead of the fifth Friday.

If the report contains a custom field with a look up table and the look up table has values which contain the single quote character " ' " then if the user generates a visual report containing this custom field, Project may crash.

When you build the Earned value Over Time report in Project Client, the AC values (which should be the same as ACWP) are not correct.

Applying updates causes assignments to lose work and tasks to lose duration.

When status updates are accepted, the status update job will show that the job completed successfully; however, the update apply process failed and the submitted actuals do not show up in the project plan and subsequent downstream reports.

If the "Actual costs are always calculated by Project" option is disabled in Project 2010, for tasks with their finish date before the status date of the project and with resources that have associated cost, the actual cost data can be incorrect.

When using Project 2010 to open a file with a timeline from Project 2013, the timeline doesn't display correctly (background timeline bar doesn't show up, and default task color is too light).

Time-phased views of cost resources not displaying correctly.

When attempting to create yearly recurring calendar exceptions in Project 2010, creation may fail if multiple exceptions occur after the 28th day of the month.

When changing the constraint on a milestone task in Project 2010, baseline cost data that had previously been set for that task may be lost.

If a user self-assigns a team task and subsequently PM rejects the pending updates when opening the affected plan into Project Professional, any subsequent edits to the plan tasks and assignments will cause publishing of that plan to fail.

After accepting status updates into a project plan in Project 2010, tasks linked from external projects can lose their start date data.

Costs are not calculated correctly if there are multiple cost rate tables and if actual work entered exceeds the work that was scheduled.

When editing a project using the PSI or in Project Web App with greater than 1000 calendar exceptions, scheduling tasks could fail with an InvalidOperationException error.

noteNote
For a complete listing of issues fixed by Service Pack 2, see Issues Fixed by Service Pack 2 (SP2) in Office and SharePoint 2010.

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

  • Back up the farm before you start the installation. Microsoft Project Server 2010 Service Pack 2cannot 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).

    importantImportant
    The Project Server 2010 Service Pack 2 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.

To install Microsoft Project Server 2010 Service Pack 2 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 2 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.

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

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

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

  2. After installation of the Service Pack 2 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.

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

  4. On a server in the farm, run the Microsoft Project Server 2010 Service Pack 2 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 2 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 2 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.

    noteNote
    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 2 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.

    noteNote
    We recommend that you complete the Microsoft Project Server 2010 Service Pack 2 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 2 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.

    importantImportant
    All Microsoft Project Server 2010 Service Pack 2 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.

    importantImportant
    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 2 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.

It is important to remember that Project Server 2010 Service Pack 2 also contains Service Pack 2 updates for SharePoint Server 2010, and both are applied automatically during the installation process. For Project Server 2010 Service Pack 2 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.

    importantImportant
    The Project Server 2010 Service Pack 2 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 2 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 2 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 SP2.

This scenario can be achieved if you install Project Server 2010 Service Pack 2 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 2 update to install the Project Server 2010 and SharePoint Server 2010 Service Pack 2 binary files.

    importantImportant
    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 2 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.

    noteNote
    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 SP2, the farm will still function even if the SharePoint Server 2010 databases are not upgraded to SP2 (running in "compatibility mode"). SharePoint Server 2010 features and fixes that are available in SP2 are not available until the SharePoint Server 2010 databases are upgraded to Service Pack 2 (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”.

noteNote
Running an environment in backward compatibility mode is only intended to be a temporary convenience to help administrators when they deploy the Service Pack 2 update. We suggest that you not run in backward compatibility mode for an extended time.
For more information about updates and Backwards Compatibility mode, see Install a software update (SharePoint Server 2010).

The updates from the June 2013 Cumulative Update (KB 2855357) will not install on Project Server 2010 Service Pack 2. You will be able to install the August 2013 Cumulative Update to Project Server 2010 SP2. Note that the June 2013 Cumulative Update includes some changes that are not available in Project Server 2010 SP2. If you need those changes, and Project Server 2010 SP2 is already deployed, you will need to wait until the August 2013 Cumulative Update is released and install it to obtain the changes from the June 2013 Cumulative Update. If the June 2013 Cumulative Update is already deployed but Project Server 2010 Service Pack 2 is not, you should wait until the August 2013 Cumulative Update is available and then install the updates from it and Project Server 2010 SP2, in any order.

The Microsoft 2010 Office Servers Language Pack Service Pack 2 package contains SP2 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 SP2 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 SP2 package to update the SharePoint Server 2010 French-France Language Pack and the Project Server 2010 French-France Language Pack.

To more information about the Microsoft 2010 Office Server Language Pack Service Pack 2, see Description of Office Servers 2010 Language Pack SP2. To download the Microsoft 2010 Office Servers Language Pack SP2 package, see the knowledge base article: Service Pack 2 for Microsoft 2010 Server Language Pack (KB2687462).

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

  1. On all servers in the farm, install the Microsoft Project Server 2010 SP2 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 SP2 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.

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 2 (SP 2)” to verify that the update has been installed. The same update information should be listed under Microsoft SharePoint Server 2010.

    noteNote
    If you are running SharePoint Server 2010 in backward compatibility mode and your SharePoint Server 2010 databases are not upgraded to Service Pack 2, the View Installed Updates page still shows “Microsoft SharePoint and Project Server 2010 Service Pack 2 (SP 2)” 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.

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

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