You cannot submit a project to the next stage of a demand management workflow in Project Server 2010.
When a team resource tries to self-assign a task, the task is still displayed in the task list and is not assigned correctly to the team resource.
When you change a project summary task in Project Server 2010, the timephased budget cost information for cost resources is lost.
When Active Directory Domain Services (AD DS) contains an inactive user, the Project Server security group synchronization process fails.
Timephased remaining costs and actual costs are calculated incorrectly in the report database in Project Server 2010.
When you set a custom date field to NA in Project Server 2010, the date 1/3/84 is displayed unexpectedly in the field.
Values in a custom field are not displayed in Project Professional 2010 or in Project Web App (PWA). This issue occurs when the custom field can contain multiple values. However, the values are displayed in Project Professional 2010 or in PWA after you clear the local project cache.
After you save a value in the cost formula field on a Project Detail Page (PDP), an incorrect value is displayed. This issue also occurs in the percentage formula field.
After you accept status updates for a project in Project Server 2010, the project displays actual work that is submitted through PWA as an incorrect decimal value. For example, a project displays .48h as the actual work even though you submitted .5h as the actual work.
Assume that you self-assign a task in Project Server 2010, and then you open a new timesheet that contains an assignment without any planned work. In this situation, the task enterprise custom field does not populate values as expected.
Assume that you edit a task by using the Schedule Web Part in the Project Center. When you try to close and update the task, you receive the following message:
This project is currently checked out. No edits can be made to it while it is checked out.
When you update the status of certain projects, the status update job fails. Additionally, you receive the following error message:
Status approval internal error: StatusingInternalError (3116)
When you publish a Project Detail Page (PDP) in Project Server 2010, the values in an enterprise custom field are lost. This issue occurs even when you do not change the project schedule in the PDP.
Buttons on the ribbon are disabled for certain tasks in the Approval Center. This issue is caused by a script error that occurs on the Approval Center page.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To install this hotfix package, you must have Project Server 2010 or Project Server 2010 Service Pack 1 (SP1) installed.
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released
To use one of the hotfixes in
this package, you do not have to make any changes to the
This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to resolve the issues that are listed in this article.
global version of this hotfix package uses a Microsoft Windows Installer
package to install the hotfix package. The dates and the times for these files
are listed in Coordinated Universal Time (UTC) in the following table. When you
view the file information, the date is converted to local time. To find the
difference between UTC and local time, use the Time Zone tab
in the Date and Time item in Control Panel.
Collapse this tableExpand this table
Microsoft Windows Installer .msp file information
Collapse this tableExpand this table
After the hotfix is installed, the global version of
this hotfix has the file attributes, or a later version of the file attributes,
that are listed in the following table: