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 April 30, 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:
When you edit a custom field through PWA for a project plan that has in-progress tasks, and then you reopen the project in Project 2007, the duration and percentage complete for these tasks are unexpectedly changed.
After you accept updates for assignments, Project 2007 shows different contours for actual work and for actual overtime work. If you save and publish the project, the resource's timesheet on the My Tasks page shows the same incorrect contours.
By default, the booking type for all resources is Proposed. This may cause issues. For example, assume that the resource booking type is set to Proposed for the enterprise resource. However, in the project, the same resource’s booking type is set to Committed. After you change the details about the resource and then publish the project plan, the booking type in the project changes back to Proposed. Therefore, resource pending updates for that project are lost. Additionally, resources cannot see their work on the My Tasks page.
Milestone becomes 100-percent completed if one of the following conditions is true:
You use the QueueUpdateProject Project Server Interface (PSI) method two times to update the task constraint date.
An update is made to a predecessor task.
On the approvals page, the timephased view starts at the beginning of the affected tasks instead of the date range where the new updates are at. For example, assume that you have a task that begins January 1 and ends December 31. Also assume that it is now May, and when you visit the updates page, you see the timescale starting in January instead of in May. This means that you have to scroll to the new May updates.
On the My Tasks page in Project Web Access (PWA), you perform grouping on one or two fields. In the list of tasks or assignments, if the leaf on which the grouping is performed is clicked, no tasks or assignments are displayed. Additionally, you receive the following error message:
The indicated project is not available in Project Center.
After you accept updates and periods on the My Tasks page, an actual work contour of 0 hours is added to dates after the last date that has actual work for some assignments. This causes actual work to redistribute across the period.
When you set the site regional settings as Swedish, Norwegian, or Finnish in PWA, the sorting order in the Select Task – Webpage Dialog box is incorrect if one or more of the Å, Ä, or Ö characters is included in a project name.
In this situation, the sorting order in the Select Task – Webpage Dialog box starts by listing all the projects first, followed by all tasks.
When you visit the Assignment Details page directly from the My Tasks view, the Gantt Chart is always set to use the date range of the current date instead of the range that is set in My Tasks view.
On some assignments, when a task update that has actual work hours is submitted from PWA and accepted by the project manager, additional hours of actual work are incorrectly added to that assignment.
On the My Tasks page in PWA, if the data is displayed as being timephased, and any grouping is applied, you may receive the following error message when you try to print the view:
The "TaskPart" Web Part appears to be causing a problem. Object reference not set to an instance of an object. Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator. Troubleshoot issues with Windows SharePoint Services.
If an enterprise resource task assignment has 0 hours of work associated with it, the values that you see for the summary resource assignments under the Other Projects and Commitments in the Resource Usage view may not match.
When you search specific Korean characters on the Edit Project Properties page, you may receive the following error message:
This project is currently checked out. No edits can be made to it while it is checked out.
Note This issue does not occur on the Manage User page when you search the same characters. The same issue also occurs in an English-language environment if you search some Chinese characters.
On the My Tasks page, you enter time on the Gantt Chart for a multiple-week task. However, after you click Save All, some time may not be saved.
When you delete a timesheet line in PWA and then add another line, the added line is empty. Additionally, you receive the following error message:
While communicating with the project server an error occurred. Check connectivity with your administrator to determine if further action is necessary.
The Resource Assignment page returns no data when the filter that is applied is based on an enterprise custom field.
When you delete resources in PWA or through the PSI, the deletion fails, but no error is returned to tell you why the deletion failed.
Note To resolve these issues, you have to install both hotfix package 969957 and hotfix 968860. For more informationabout hotfix 969957, click the following article number to view the article in the Microsoft Knowledge Base:
969957 Description of the Project Server 2007 hotfix package (Pjsrvmui.msp): April 28, 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.