- The issues that the hotfix package fixes.
- The prerequisites for installing the hotfix package.
- Whether you must restart the computer after you install the hotfix package.
- Whether the hotfix package is replaced by any other hotfix packages.
- Whether you must make any registry changes.
- The files that the hotfix package contains.
Issues that this hotfix package fixes
- Assume that you have an Enterprise custom field that has a lookup table associated with a task. If you save a project, rows are added to the database unexpectedly. This increases the size of the database and causes slow performance.
- The Task Updates page shows no updates when updates are pending.
- Timesheet actuals are not populated in the Reporting database if an initial save or submit operation fails.
- Consider the following scenario. You have an enterprise custom field in the project level. The custom field contains a formula. You log on Project Web Access (PWA) and a user accepts a task update from a resource. Then, you publish a plan to the project server. In this scenario, the record for this custom field is deleted unexpectedly from the database of the project server. Additionally, the record cannot be reported against the custom field.
- Consider the following scenario. In the Timesheet feature, a resource uses the Add Lines feature to add the project summary task to the timesheet and to enter time. However, the time is not imported to My Tasks.
- Assume that you have a task that starts on 2/22/2010, 2/24/2010 or 3/30/2010. When status updates are accepted for that task, the start date changes to a date in the past unexpectedly even though the status update does not require a start date change. This problem may also occur for tasks that start on other dates.
- Assume that you synchronize a project between Microsoft Dynamics AX 2009 and Project Server 2007. When you edit the project in Project Professional 2007, the project is changed in a way that breaks integration with Dynamics AX 2009.
- When you publish a project in Office Project Server 2007, the publishing job may take a long time to be completed. This is caused by an assignment exception that is defined in a way that results in an infinite loop.
- The Task Updates page shows no update event when updates are pending.
- When you use project server interface (PSI) to publish a project plan, the resource availability changes to 3 months later than expected.
Hotfix informationA recently discovered issue affecting Project plans that contain baselines was fixed and included in the Project Server 2007 February 2011 cumulative update package. This issue was traced back to have originated in the Project Server 2007 April 2010 cumulative update package. As our cumulative updates are incremental, this issue also affected the June, August, October, and December server updates.
We recommend that customers install the latest cumulative update packages that are described in KB953878. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Article ID: 2276475 - Last Review: Mar 29, 2017 - Revision: 3