Si vous êtes un client Small Business, découvrez des ressources de formation et de résolution de problèmes supplémentaires sur le site de Support pour Small Business.
When you edit a project that contains cross-project links and enterprise custom fields in Project Web App, task durations are changed unexpectedly.
When you edit a custom field from the Assignment Details page in Project Web App, you cannot input more than 50 characters.
Consider the following scenario:
You enable the Protected Actuals feature and then create a task.
A team member reports an actual work, and the actual work is approved.
You edit a work or remaining work of the task in a Project view in Project Web App.
In this situation, you receive the following error message:
Your last edit changes actual work on the project. Currently Project Web App is set up to protect actuals on tasks.
Consider the following scenario:
You create a task that has predecessor relationship, multiple assignments and at least one assignment that has actual work applied.
You report and approve actual work for one of the other assignments.
The work is reported earlier than scheduled and earlier than when the actual work that is already reported on the other assignments.
In this situation, the actual work on the assignment is scheduled incorrectly. Therefore, the start date and duration of the task is calculated incorrectly.
When you use Project Server Interface (PSI) to update a project that contains multiple cost rate table entries in Project Server 2010, resource costs are calculated incorrectly.
Unnecessary user account synchronization occurs and you experience performance issues in Project Web App. For example, you cannot log on the server.
When you use a template that contains a null task to create a project in Project Web App, the project cannot be displayed in Project views. Note A null task is a blank row between rows.
Totals for grouping rows on the Approvals page in Project Web App are not rolled up.
A
supported hotfix is available from Microsoft. However, this hotfix is intended
to correct only the problem that is described in this article. Apply this
hotfix only to systems that are experiencing the problem 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.
Prerequisites
To install this hotfix, you must have Project Server 2010 Service Pack 1 (SP1) installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
List of all SharePoint 2010 and Office Server 2010 SP1 packages
Restart requirement
You do not have to restart the computer after you install this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released
hotfix.
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
File information
This hotfix package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to resolve the issue that listed in this article.
The
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.
