Description of the Project 2010 hotfix package (Project-x-none.msp): August 28, 2012

Summary

This article describes the issues that are fixed in the Microsoft Project 2010 hotfix package that is dated August 28, 2012.

INTRODUCTION

• Assume that you add a resource to the plan of a project in Project Professional 2010 and then save the plan. After you publish the project to a Project server, you cannot open the plan from the server. This issue occurs because there are duplicate RES_OPTINDX values in the MSP_PROJECT_RESOURCES table.
  

• Duplicate project names are displayed for summary resource assignments under the Other Projects and Commitments section in Resource Usage view.
  

• After you apply the hotfix package that is described in Microsoft Knowledge Base (KB) article 2536590 to the French version of Project Professional 2010, tasks in an .mpp file are scheduled incorrectly. This issue occurs because Project Professional 2010 uses a wrong calendar.
  
  Note For more information about KB article 2536590, click the following article number to view it:
  

  2536590 Description of the Project 2010 hotfix package (project-x-none.msp): June 28, 2011

  
  

• Assume that you view a plan in Resource Usage view and apply a grouping on the view. When you select the Maintain Hierarchy in Current Group option, Project 2010 crashes.
  

• When you view the baseline work field for an unassigned resource by using Resource Usage view, incorrect values are displayed in the baseline work field.
  

• When you publish a project that contains defined enterprise flag fields, the number of records in the MSP_TASK_CUSTOM_FIELD_VALUES_SHADOW table doubles in the published database.
  
  Note To resolve this issue, you should apply the update that is described in this article and then apply the update that is described in KB article 2687390 on the Project server. For more information about the update, click the following article number:
  

  2687390 Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none): August 28, 2012
  

• When you set the list separator in Regional Settings to a character other than a comma (,), the following issues occur:
  

  • You cannot use Form view to create task dependencies.

  • You cannot assign resources to a task. For example, you cannot assign resources to a task by using the Assign Resources dialog box.

• A resource in a summary field that shows summary resource assignments is displayed as overallocated unexpectedly. 
  

• Consider the following scenario:
  

  • You schedule a project from the project finish date.

  • You create a task in the project and assign two resources to the task.

  • You start one of the assignments.

  • You click the Reschedule uncompleted work to start after: button to update the project.

  In this scenario, the scheduled work for an assignment that is not started is reduced.
  

• Assume that you enable the Keep local with base calendar optionon resources when you use the import wizard to import a project from Project Professional 2010 to a Project server. When the import wizard finishes and you view the Resource Center through Project Web App, resources that are supposed to be local to the imported project are displayed unexpectedlyas enterprise resources.
  

• When an assignment has a protected actual work field that contains a zero value in Project Professional 2010, the assignment cannot be completed.
  

• When you enter timephased actual work for a period of time on an assignment in a manually scheduled task, the actual work value is divided and displayed in two periods of time.
  

Resolution

References

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates