Issues that are fixed in Project 2007 by the Project 2007 Infrastructure Update

This article has been archived. It is offered "as is" and will no longer be updated.
This article describes the Microsoft Office Project 2007 issues that are fixed in the Infrastructure Update that is dated July 15, 2008.
For more information about the Project 2007 Infrastructure Update, click the following article number to view the article in the Microsoft Knowledge Base:
951547 Description of the Project 2007 Infrastructure Update: July 15, 2008

List of issues fixed and improvements made

This update fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

Note For additional details on the improvements in this update, read the "Project 2007 Infrastructure Update Release for Server and Client" white paper at the following Microsoft Web site:

Cost resources

  • Made sure that time-phased calculations equal sheet calculations.
  • Made sure that no additional data is added to the cost resource user interface (UI) during calculations.
  • Made sure that cost resource calculations are consistent with the Project scheduling calculations.
Specific issues that are fixed:
  • If the cost contour results contain zero cost days, the days that have nonzero costs will display incorrect cost values.
  • You save a project template that has cost resource assignments. If the cost resource assignments have a Work complete value that totals zero percent, the day level cost is reduced.
  • When you add actual costs to a cost resource assignment on a day that has no scheduled cost, the cost amounts on the time-phased side do not equal the cost amounts on the sheet side.
  • Cost contours that have zero daily totals inside an assignment's start dates and end dates could generate incorrect results when you enter actual cost for this assignment.
  • When you edit time-phased actual costs, a different behavior occurs in the following circumstances:
    • If the cost resource assignment that contains the costs was assigned in isolation, the cost data appears under the day in which it was assigned.
    • If the cost resource assignment, together with a work resource, was assigned to a task, the cost data appears under the wrong day. Additionally, the start day of the task may change.
  • When you enter actual cost for a task, the task's finish date changes. Additionally, the new date differs from the assignment's finish date.
  • Random costs are added to the planned cost contour when you enter actual costs at the end of the established contour.
  • The cost contour is not distributed correctly at the month level when either of the following situations is true:
    • Actual costs are entered before the contour.
    • The duration changes and crosses a monthly boundary.
  • When you enter actual costs outside the end of the cost resource assignment dates, the Total Cost value incorrectly increases.
  • When you enter Actual cost on the sheet, Cost and Actual Cost values are reduced on a task or on an assignment.
  • When you add actual cost to a cost resource assignment, any increase over the planned cost results in an increase in the total cost on the time-phased side. However, the sheet side is not increased.
  • When you assign cost resources to the end dates of a fixed duration task, the duration does not reduce in value. Additionally, the duration amount differs from the number of days between the start date and the finish date of the task.

    Note The update makes this process behave in a manner similar to those that involve work or material resources.

Custom fields stability (Client)

  • Improved support for copy and paste when you edit lookup table values.
  • Addressed issues in which graphical indicator information is lost after you save and then reopen a project plan.
  • Addressed issues in custom field formula calculations.
  • Fixed issues that occur when you save projects with multilevel outline code values.
Specific issues that are fixed:
  • When you assign the task Flag2, the task behaves differently from other fields.
  • When you try to open a project that contains a custom field, Project 2007 stops responding if the custom field contains scalar data and was modified to use a lookup table. Additionally, you cannot save this project to Project Server 2007. The save fails.
  • When you save a project, multilevel outline code data in the project is not preserved.
  • When you save a project as XML, negative values are converted to positive values.
  • When you save a plan to Project Server 2007 and then reopen the plan, all graphical indicators in the Duration field and in the Start field are lost.
  • A local custom field that has more than 998 values cannot be added as an enterprise custom field. Additionally, when you add a local custom field to an enterprise custom field, you may receive error code 9000. This is true if the enterprise custom field uses a lookup table that has more than 998 values.
  • It is now possible to paste text into Project 2007 lookup tables from other sources, such as Notepad.

Project Server local cache resiliency

  • Addressed top issues that relate to active cache data resiliency.
  • Added a dialog box that notifies users to make sure that you save all pending project data to the Project Server Queue before they exit Project Professional.
Specific issues that are fixed:
  • When you receive an error message in Project 2007, you may receive a check-in request message.
  • When you save a project, a plan, a resource, or another Project Professional 2007 file, you may receive a blank error dialog box.
  • When you use the Project Server 2007 migration tool that is called P12MigrationTool.exe, the tool may fail. Additionally, you may receive the return code of "0x80004005."

Excel import problem

  • Task predecessor links are not preserved when work is imported into Excel.
More information


The following list contains prerequisites for the update:
  • We strongly recommend that you install Project 2007 Service Pack 1 (SP1), the Windows SharePoint Services 3.0 Infrastructure Update, and the Microsoft Office Servers Infrastructure Update before you install this update. For more information about how to obtain the Project 2007 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
    949584 How to obtain the latest service pack for Project 2007
    For more information about how to obtain the Infrastructure Updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:
    951695 Description of the Windows SharePoint Services 3.0 Infrastructure Update: July 15, 2008
    951297 Description of the Microsoft Office Servers Infrastructure Update: July 15, 2008

Restart information

You do not have to restart the computer after you apply this update.

Hotfix replacement information

This update does not replace a previously released update.

Registry information

To use one of the updates in this package, you do not have to make any changes to the registry.

Known issues

  • Cost value on a cost resource is zeroed out when a non-milestone task becomes a milestone.
  • Cost resource contour is always stored at day precision.
  • Cost resources should not be assigned to the same task as other kinds of resources if you plan to track the status of those resources by using Project Web Access.

Obtain and install the update

The Project 2007 Infrastructure Update 32-bit package, installation instructions, and deployment strategies can be found at the Microsoft Download Center. To download this update from the Microsoft Download Center, visit the following Microsoft Web site:
prjsvr12 prjsvr2007 prj12 prj2007 PSRV2007 ProjectServer2007

Article ID: 953751 - Last Review: 01/16/2015 02:32:49 - Revision: 2.0

Microsoft Office Project Professional 2007, Microsoft Office Project Standard 2007

  • kbnosurvey kbarchive kboffice2007presp2fix kbexpertiseinter atdownload kbqfe kbhotfixserver KB953751