Hotfix KB2889856 for Project Server 2013 September 9, 2014 (Projectserverwfe-x-none.msp; Projectservermui-<Language-Code>.msp)

Issues that this hotfix package fixes

• Assume that you edit the resource plan of a project in Project Web App by using Windows Internet Explorer 10 or Windows Internet Explorer 11. When you save and close the resource plan, it is still in a checked-out state.
  

• Assume that you enable multiple authentication providers for a Project Server 2013 server. Then, you create a user account in Project Web App. When you try to edit the user from the Edit User or Edit Resource page, you may receive the following error message:

  Multiple entries matched, please click to resolve.

  In addition, there is a red squiggly line in the people picker field.
  

• When you use a Project Server Interface (PSI) application to update a project level enterprise field that uses formulas, the values of the field may be lost.
  

• Assume that you set the date format to "dd/mm/yyyy" for a Project Server 2013 server. The Custom Date Range filter on the Timesheet page may change unexpectedly when you click the Apply button.
  

• The resource name that is written to the dbo.MSP_TimesheetResource reporting table becomes different after the approval of a timesheet or a status update. Therefore, it is difficult to do a report that is correlated by resource name.
  

• Assume that you create a project level custom field that uses a formula, and the formula refers to other custom fields. Then, you change the values of the other custom fields and then click the Save button in the Project Details page in Project Web App. In this situation, the project level custom field does not always calculate as expected.
  

• A project reporting publish job may fail. Additionally, the Reporting (Project Publish) queue job error resembles:

  The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignmentBaselineByDay_ProjectUID_AssignmentUID". The conflict occurred in database "PWA", table "dbo.MSP_EpmAssignmentBaseline". The statement has been terminated.

• Consider the following scenario:
  

  • You create an Active Directory group and add a user to the group.

  • You sync the Active Directory group to a group in Project Web App (PWA).

  • You delete the user from the Active Directory group.

  • You execute the sync operation again.

  In this scenario, the user is still active in PWA.
  
  

• Consider the following scenario:
  

  • You select the Allow users to choose option in the Project Site Provisioning Settings page.

  • You create a rule that enables Automatically run this rule option, and the Automatically publish the updates option is selected in the Edit/Create Rule page.

  • You create a project, assign a task to an enterprise resource in Project 2013, and then you publish the assignment.

  • The user who owns the assignment enters progress against the task.

  In this scenario, when the user sends an update for approval by clicking the Send Status button in the Tasks page, there is an error message in the queue resembles the following:

  Queue:?GeneralQueueJobFailed (26000) - CreateWssSite.CreateWssSiteMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='c2cd523c-9ec1-e311-beee-00155d4a810b' JobUID='bfc3b935-9ec1-e311-beee-00155d4a810b' ComputerName='1c1a4290-cfc3-40a9-981b-bfe9e25c9982' GroupType='CreateWssSite' MessageType='CreateWssSiteMessage' MessageId='1' Stage='' CorrelationUID='ed3f869c-4723-1009-c998-2ee8b732a4c4'. For more details, check the ULS logs on machine 1c1a4290-cfc3-40a9-981b-bfe9e25c9982 for entries with JobUID bfc3b935-9ec1-e311-beee-00155d4a810b.

  Additionally, the job owner is listed as the user who sent the update.
  

• Consider the following scenario:
  

  • You enable single entry mode on a Project Web App (PWA) site on a Project Server 2013 server.

  • You delete the default My Work view for the Timesheet page.

  • You create a project and assign a task to a resource.

  In this scenario, the resource cannot create a new timesheet.
  
  

Hotfix information

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:

http://support.microsoft.com/contactus/?ws=supportNote 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

You must install the following public update before you apply this hotfix package:

2768001 Description of the SharePoint Server 2013 and Project Server 2013 update: March 12, 2013

Restart requirement

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.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

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.