This article has been archived. It is offered "as is" and will no longer be updated.
This article describes the Microsoft Office Project Server 2007 issue that is fixed in the Project Server 2007 hotfix package that is dated March 6, 2009.
This article describes the following items about the hotfix package:
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.
This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:
When you synchronize two or more users who have the same display name from different domains, the Active Directory sync fails in Project Server 2007. Additionally, the status is "Partial Fail."
The values in the following fields are different in Project Professional 2007 and in the OLAP cube. For timephased assignments:
For a task:
In Project Web Access (PWA), you receive the following error message when you click My Tasks:
An unexpected error has occurred.
This issue may occur if an assignment uses an enterprise calendar that is no longer available.
You use the Project Server Interface (PSI) to update the timephased actual work. After you publish the project, the timephased work and the timephased actual work are not added to the MSP_EpmAssignmentByDay table in the reporting database. However, the MSP_EpmAssignment table shows the correct timephased work and actual work.
In Project Professional 2007, inactive work resources are changed to inactive material resources. However, the resources are displayed correctly as inactive work resources in PWA.
When a PWA site is provisioned, the site provisioning status is "Waiting for Resources." This issue may occur if the Project Server synchronization timer job is missing.
You set the My Timesheet view to display work in hours. However, on the My Timesheets page, the remaining work values are in days.
You apply the Project Server 2007 Infrastructure Update. When you update the % Complete field on the Assignment Details page in PWA, the field is not updated in Project Professional 2007.
In PWA, you use the timesheet to update actual work. However, the remaining work may not be updated as expected on the My Tasks page. Therefore, the remaining work is also not updated in Project Professional 2007.
If you set the regional setting to Danish or Norwegian, certain values of a custom resource field are blank for some resources on the Resource Center page in PWA.
In a Norwegian version of Project Server 2007, the word "fullfør" is displayed incorrectly in the Group by list or in the Then by list on the My Tasks page.
If you change Project custom fields in PWA, the Title property is changed unexpectedly.
If you submit actual work that is at least one year from the actual start date of an assignment, the actual work is not displayed in the task updates approval grid. If the updates are accepted, the work is applied to the assignment.
The duration calculation for work that is entered on nonworking time is not calculated as expected.
You cannot send updates to the duration custom field from the My Tasks page in PWA. Instead, you receive the following error message:
Your updates were not saved because of the following reasons:
Note No reasons are listed.
You apply hotfix 957696. When you publish a project, you may receive the following error message on the Manage Queue Jobs page:
Failed but not blocking Correlation.
This hotfix also fixes the following issue:
963024 Description of the Windows SharePoint Services 3.0 hotfix package (Sts.msp): January 27, 2009
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 Web site:
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.
There are no prerequisites for installing this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
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 correct the issue that is 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.