This hotfix package is no longer available. To obtain the fixes that are listed in this article, see the following article in the Microsoft Knowledge Base:
2598251 Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp): March 9, 2012
This article describes the Microsoft Project Server 2010 issues that are fixed in the Project Server 2010 hotfix package that is dated February 28, 2012.
Issues that this hotfix package fixes
Consider the following scenario:
You set the system time zone to a setting between UTC and UTC +12:00 on a Project Server 2010 server.
You set a date period for a project in the Date Range dialog box by using Project Web App (PWA). For example, you set the Date Range when you edit a resource plan.
You view the date value on the Date Range group on the ribbon.
In this scenario, the date value that is displayed does not match the date value that you set. Additionally, the date period is one day earlier than the date period that you set.
When you use the Project Server Interface (PSI) to update an enterprise custom field on a local resource, the values in the enterprise custom field that are associated with the local resource are lost.
Assume that you create a timesheet that contains a task. The task has a Flag enterprise custom field that is set to Roll down. In this situation, the timesheet is not created successfully. Additionally, you receive the following error message:
The Timesheet creation failed, because of problems with the project server or with data validations, such as resources not being valid work resources or users. Check your environment, and then try again.
Then, you delete the timesheet. In this situation, you receive error 24011 for the Reporting (Timesheet Delete) queue job.
When you add a task to a timesheet in a project whose name contains an ampersand (&), you receive the following error message:
An unknown error has occurred.
Assume that a status manager rejects some updates to a user's timesheet and publishes the project plan. Then, the user resubmits the rejected values. In this situation, the timesheet is displayed as approved. However, the re-submitted updates do not appear in the approval center or in the project plan.
When a resource pool is resynchronized with Active Directory, the Exchange Server Synchronize Tasks property flag for users is reset. Therefore, users are not synchronized with the Exchange Server until the Synchronize Tasks settings are re-enabled.
When you try to set actual work for a manually scheduled task on a nonworking day, the actual work values that are displayed in PWA, such as in My Tasks, may not appear. For example, five hours of actual work entered on Sunday may be displayed as zero hours in My Tasks.
The Task Hierarchy field in a timesheet view is not populated until the timesheet is saved. This issue occurs when one of the following conditions is true:
An existing task that is assigned to a resource has no planned or actual work during the period of a newly created timesheet.
A new task is assigned to a resource, and a user opens an existing timesheet period that contains the new assignment.
Assume that you have a fixed duration task that has more than one enterprise resource assigned. Then, a user updates the actual work of a resource in the task by using Project Web Access (PWA). In this case, the task-level % Complete and Actual Duration values are not updated correctly when you view the task in Project Professional.
When you publish projects, you receive the following error message in the queue:
GeneralQueueJobFailed (26000) - ProjectPublish.UpdateSRAMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='<uid>' JobUID='<jobuid>' ComputerName='<computername>' GroupType='ProjectPublish' MessageType='UpdateSRAMessage' MessageId='179' Stage=''. For more details, check the ULS logs on machine <computername> for entries with JobUID <jobuid>.
Assume that you have a multiple-value custom field that is referred from a formula in an enterprise project custom field. In this situation, when the formula is recalculated on the server, you do not receive a list of all selected values. Instead, you receive only the last value. For example, a multiple-value custom field displays the values A1, A1.1, C, C1.1, and C1.2. However, the formula on the server returns the value C1.2 only.
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 installed.
You may 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 resolve the issues that are 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.
Microsoft Windows Installer .msp file information
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: