Description of the Project Server 2010 hotfix package (Pjsrvwfe-x-none.msp): 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:
  
  Queue Error:
  
  General
  
  Microsoft.Office.Project.Server.BusinessLayer.Queue.Message:
  
  ProjectPublishFailure (23000). Details: id='23000' name='ProjectPublishFailure' uid='<uid>' projectuid='<projectuid>' messagetype='Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.UpdateSRAMessage: projectUid = <projectuid>' messageID='179' stage='' blocking='Block'.
  
  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.
  

Back to the top | Give Feedback

Hotfix information

Prerequisites

Restart requirement

Hotfix replacement information

Registry information

File information

Back to the top | Give Feedback