Hotfix KB 2889959 for Project Server 2013 October 14, 2014 (Projectserverwfe-x-none.msp; Projectservermui-<Language-Code>.msp)

Issues that this hotfix package fixes

• After you install the June 2014 cumulative update for Project Server 2013, the Project Professional Versions setting does not work correctly. Therefore, you may be unable to edit a project, preview updates, or apply status updates in Project Web App.
  

• Assume that you enable the Only allow task updates via Tasks and Timesheets option. When you edit a project in Project Web App, and try to delete a protected task, you receive no error message. Additionally, the task disappear from the list until you refresh the page.
  

• Assume that you set a value for the Maximum Hours per Day setting. The setting is ignored when a user makes use of the Send a progress for... feature from the Timesheets page.
  

• Project Queue service might process jobs slowly when there are many pending jobs.
  

• You may be unable to edit a project, preview updates, or apply status updates through Project Web App. Additionally, if you apply status updates, you may see an error similar to the following in the ULS logs:

  StatusingInternalError. Details: Status approval internal error Attributes: System.TimeoutException: This request operation sent to net.pipe://localhost/pscalc_ef84be5e83f242fa81604afdf9348d52 did not receive a reply within the configured timeout (00:05:00). The time allotted to this operation may have been a portion of a longer timeout.

• Assume that you have a project that contains a resource whose display name contains a colon (:). If the project has an associated SharePoint site, you may be unable to publish the project to a Project Server 2013 server.
  

• When you change the view of the Project Center page and apply a different filter or grouping, the filter option and the grouping option do not change as expected. Instead, the view may still be filtered or grouped based on the previous view.
  

• Consider the following scenario:
  

  • You add a task to a project in Project 2013, and then you add to the task a note that contains a special character such as a vertical tab.

  • You publish the project to a Project Server 2013 server.

  • You log on to the project site through Project Web App, and then you browse to the Task page.

  In this scenario, the Task page is not loaded. 
  

• Consider the following scenario:
  

  • You create a custom field that uses a lookup table, and you allow multiple values to be selected.

  • You insert several tasks into a project, and then you select values from the custom field for the tasks.

  • You save and publish the project.

  • You change the value of the custom field for one of the tasks, and then you save the project.

  • You change the value of the custom field on the other tasks, and then you save the project.

  • You publish the project.

  In this scenario, the value of the custom field for the tasks may be incorrect when you query the value from the reporting database tables. 
  

• Consider the following scenarios:

  • You create a lookup table in Project Web App (PWA), and the lookup table contains multiple values. The total length of the values exceeds 255 characters.

  • You create a custom field that uses the lookup table, and you set the option that requires information in this field.

  • You create a project in PWA for the custom field, you select multiple lookup table values, and the total length exceeds 255 characters.

  • You save, check in, and then close the project.

  • You open the project in Project Professional.

  • You make a change in the project and then save it.

  In this scenario, the project cannot be saved, and you may receive the following error message:
  

  Project cannot save the project to Project Web App. You must first specify values for all required project fields. These fields are indicated with an asterisk in the Project Information dialog box, available from the Project tab.

  In another scenario, you add resources to tasks from PWA.
  

  • You have multiple resources defined in your server, and the combined length of the names exceeds 255 characters.

  • You go to the Project Center in PWA, drill into a project, select the Schedule project detail page, and then you click the Edit button.

  • You go to the Resource Names field for a task and select multiple resources. The total length of the names exceeds 255 characters.

  • You save and then close the project.

  • You open the project.

  In this scenario, some of the resources that you added to the task are not saved. For the resource names that straddle the 255 character limit, only partial resource names are displayed.
  To resolve these issues, you must install both the fixes in this knowledge base article, and you must also install the fix in KB 2889957.
  

• Consider the following scenario:
  

  • You create a custom list, and you add a lookup column to the list, and then you create an item in the list.

  • You log on to the Project Web App site as Project Manager.

  • You browse to the list, and you select the item, and then you click the Create Projects button.

  In this scenario, you may receive the following error message:
  

  Sorry, this site hasn't been shared with you.

• Consider the following scenario:
  

  • You create a custom field, and you check the check box of the Behavior controlled by workflow option.

  • You add the custom field to the Project Details page.

  • You open and edit a project in the Project Details page.

  • You change the value of the custom field, and you change another value for the other field such as the Start Date of the project, and then you save the project.

  In this scenario, when you refresh the page, the value in the custom field is not saved, and the Start Date is reverted to the previous date. 
  

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.