Project Server 2016 Public Updates

This page lists the updates for Project Server 2016.  Initial release was 1/5/2016 and the DB Version was 16.0.4327.1000.

April 2017 and

DB Version – Content DB – 16.0.4522.1000

This update contains the following improvements and fixes for Microsoft Project Server 2016:

  • When you browse PWA pages that have HTML grids either in Internet Explorer standards or enterprise mode, you can’t scroll pages because the scroll bars don’t appear.
  • Screen readers don’t identify that the Delegate Name and the User Name fields on the Add Delegation page are required.

This public update delivers the first feature pack (Feature Pack 1) for SharePoint Server 2016 that contains the following features:

  • Administrative Actions Logging
  • MinRole enhancements
  • SharePoint Custom Tiles
  • Hybrid Auditing (preview)
  • Hybrid Taxonomy
  • OneDrive API for SharePoint on-premises
  • OneDrive for Business modern experience (available to Software Assurance customers)

March 2017 and

DB Version – Content DB – 16.0.4507.1000

SharePoint updates:

  • Adds the Web Service Definition Language (WSDL) proxy files for Project Server 2016.
  • Adds translations for several group membership strings in multiple languages.
  • Adds error messages for the exceptions of taxonomy replication and migration.

This update fixes the following issues:

  • Some database views in the reporting schema such as the pjrep.MSP_EpmProject_UserView are missing and they can’t be recreated.
  • Spelling check does not provide suggestions or correct misspelled words in a calendar app.
  • You can’t add dimensions or measures to an OLAP cube definition if there is more than one PWA instance defined in a given web app.
  • OLAP cube builds times don’t follow the requested pattern. For example, if you set a cube to be built hourly, there are some hours where the cube isn’t built.
  • If you apply a filter that uses the Does not Contain filter test to a project that you are editing in Project Web App, tasks that have the filtered characters are still displayed.
  • Administrative tasks should not be auto approved if the timesheet owner has the Adjust Timesheet permission.
  • On the OLAP Database Management page, you can’t set a new default OLAP database, or enable or disable existing databases if you have more than one PWA instance on the server.
  • Previously, files are copied side-by-side if the EnableSideBySide setting is true. Now, files are copied side-by-side regardless of the EnableSideBySide setting.
  • An issue that occurs when you pipe Set-SPContentDatabase with Get-SPContentDatabase.
  • Adds more logs to diagnose the issue in which a farm server turns to the Upgrade Required status after a successful run of psconfig with the No Action Required server status.
  • It’s difficult for a screen reader to understand the structure between sections on a discussion board. This is because there is only one heading. This update adds h2 and h3 labels to the discussion board for better screen reading.
  • Updates the translations to make sure that the meaning of the word “Drivers” is correct in Project Server.

February 2017 and

DB Version – Content DB – 16.0.4498.1000

This update fixes the following issues in Project Server 2016:

  • Timephased data on material resources may be incorrect if updates come from PWA. For example, you have a material contour that resembles the following:


In PWA, the team member reports the following:


When the update is displayed in Project Professional, the material contour resembles the following:


Instead, the contour should be like:


  • After you edit a project in PWA, formulas that rely on the Now() function and the [Current Date] property aren’t calculated.

January 2017 and

DB Version – Content DB – 16.0.4483.1000

This update includes the following improvements and fixes in Project Server 2016:

  • You can’t use the CSOM API to set the BookingType property for enterprise resources in projects.
  • When you apply status updates in PWA, actual work is added to some assignments unexpectedly. For example, you have an assignment that has 35 hours total work, and the status update is to apply 9 hours. When you view the results in Project Professional, you find that the assignment is unexpectedly completed. Meanwhile, the total work and the actual work have increased to 400 hours.
  • Translates some terms in multiple languages to make sure that the meaning is accurate.
  • Translates some terms in Brazilian for Project Online.

December 2016 and

DB Version (C0ntent DB – 16.0.4471.1000)

This update includes the following improvements and fixes in Project Server 2016:

  • If you apply a new site theme, the timeline which is a part of the tasks app, may continue to use the default theme. For example, suppose that the new site theme displays a blue background. In this case, the timeline would still be displayed with the default white background.
  • An Active Directory group that’s used to synchronize users in Project Web App and that includes disabled accounts does not inactivate those users in Project Web App. Additionally, the Active Directory Sync job may show that it partly failed.
  • When you edit a project in Project Web App, the filter that has been associated to the view that you have applied doesn’t work if the filter uses the “Begins with” test.
  • Consider the following scenario:
    • In Project Professional, you have several tasks, some of which are summary tasks.
    • You have collapsed some detail tasks so that you only see the related summary tasks.
    • You save, publish, close, and check in the project.
    • In Project Web App, you go to the Project Center.
    • You drill into the project so that you can see the details.
    • You choose to edit the project in Project Web App.

    In this situation, you see the expected summary tasks but you can’t expand them in order to see the sub tasks under them.

November 2016 and

One public fix in this release: Self-assigned timesheet lines may display an incorrect TASKUID in the OData feed.

October 2016 and

DB Version (C0ntent DB – 16.0.4432.1003)

The Project Server specific fixes are not in the public articles for this update. The fixes will be posted here when information is made public.

September 2016 and

DB Version (C0ntent DB – 16.0.4432.1003)

In 3118289

Known Issues

  • If you install the September 2016 public update for SharePoint Server 2016 and then perform a license upgrade from Standard to Enterprise, the license upgrade will time out before completing. This causes the license upgrade operation to fail.If you want or need to perform a SharePoint 2016 license upgrade, you must complete the license upgrade before installing the September 2016 public update.This issue will be fixed in a future public update.Patching and upgrading the September 2016 public update for SharePoint Server 2016 may take three times longer than in previous public updates. Please be patient while the patching and upgrading operations are completing.

Fixes (The Project Server ones)

  • When you use a template to create a project in Project Web App, the duration of a fixed duration task is changed unexpectedly.
  • For a task that displays in a timeline on a SharePoint site, when you edit the task’s date range from the callout, the timeline disappears.
  • When you use Internet Explorer or Microsoft Edge, the focus is lost unexpectedly when you move bars up or down from one timeline to another.
  • When you publish certain projects that include timelines in Project Web App, the Schedule Project Detail Page doesn’t load so that you can’t see the schedule view.
  • For tasks that display in a timeline on a SharePoint site, when you click the Edit Date Range button for a task on the timeline, you receive an error that resembles the following:
    Error message “Sorry, something went wrong”
    Correlation ID: xxxxx
    Date and Time: xxxx.
  • If you use the keyboard to select parts of the Project Summary web part, the visual focus may be stuck on the timeline section of the web part when at the same time the focus appears elsewhere. This causes screen readers not to work correctly.
  • When the focus is given to a check box on the Project Web App Resource Center page, nothing is ready by a reader because the column does not have a header.
  • On the Manage Timesheets page, a screen reader can’t determine which cell is selected and therefore it can’t read out the information in the cell to the user.
  • If project sites are created on a different site collection than Project Web App, the Web Admins group is created but user accounts are never synchronized to the group.
  • Consider the following scenario:
    • You have an Administrative Time category that allows multiple lines.
    • You create a timesheet.
    • On the timesheet, you create a new non-project line that uses the category.
    • You save the timesheet.
    • You go to the next timesheet period.

    In this situation, the page fails to load and stays forever on the loading state.

  • You can’t use keyboard to expand or collapse groupings in the grid on the Resource Center page.
  • Assume that you press the Tab key to move the focus on a column header on the Manage Timesheets page. Then, you press the Enter key in order to sort by this field. In this situation, the focus is lost from the column header, and you have to press the Tab key many times in order to return to the column header.
  • In a task list, when you click the Add button to add a new option from the Predecessors section and use the Tab key to navigate away from the Add button, visual focus disappears and you can’t make selections from the Priority or the Task Status drop-down lists.
  • You can’t use the keyboard to move the focus to the column headers in the grid for the Resource Center page. Therefore, you can’t sort the grid by using the keyboard. After you install this update, you can tab to the column header and then press CTRL + SPACE to open the drop-down list. You can also press CTRL + Y to shift the focus to the column header for a grid cell.
  • You don’t have the permission to create a project in Project Web App even if you are a project manager.
  • A server-side correlation cancelation on a save job causes deferred jobs to be canceled. For example, a team member submits time against a task and the status manager approves the update. Then, the project is checked out and the Status Update job state is listed as Skipped for Optimization. If a future save on the given project is canceled for whatever reason, the Skipped for Optimization status update job is also canceled.
  • After you delete a value from a custom field on the My Tasks page, the change isn’t saved and the value comes back when you go to the My Tasks page again.

August 2016 and

DB Version (Content DB) – 16.0.4417.1000

In 3115424:

  • Translates some terms in multiple languages to make sure that the meaning is accurate.

This update includes the following improvements and fixes for Project Server 2016:

  • Improves performance for the CSOM API GetByUser method from the Enterprise Resource Collection when there are thousands resources in Project Server.
  • In the SharePoint Central Administration Health Analyzer, the Missing server side dependencies Configuration rule shows multiple errors that should not be listed. For example, on the Configuration category, the explanation says:

[Upgrade] The number of column pool tables exceeds the database limit. The tables that exceed this limit and should be dropped.

  • Assume that the Single Entry Mode timesheet setting is enabled. When a timesheet user receives status notifications, the link in the received email navigates to the My Tasks page instead of the Timesheet page.
  • SQL Lock escalation is disabled by default for SharePoint content databases. This causes large databases to fail during the migration from Project Server 2013 to Project Server 2016 because of memory constraints.
  • After earned values are calculated in PWA from the schedule project detail page, the values may not be saved. This means the published views of the earned values may not be accurate.

In 3115441:

  • Translates some terms in multiple languages to make sure that the meaning is accurate.
  • This update will allow to remove search results from the index until the next incremental crawl.
  • When you run the SharePoint Products Configuration Wizard (PSConfig), an error occurs. The error message on the result summary page or in the result summary command line output is generic and doesn’t provide enough information to help fix the problem. This update now presents detailed error messages to identify which failures affect critical configuration tasks and which failures affect noncritical configuration tasks in the PSConfig summary. Error messages about missing SharePoint features now include the feature title instead of just the feature GUID. Error messages are displayed when the upgrading or updating has been improved. Finally, the summary message includes instructions for how to retry the configuration tasks that failed.
  • When some products or updates are installed on a SharePoint Server 2016 based computer, the SharePoint configuration database may be unaware of the installed product or update. This can cause a failure when the SharePoint Products Configuration Wizard (PSConfig) is running to do an upgrade. PSConfig will now automatically update the product and update state for the local server in the configuration database to avoid the failure.
  • When you run the PSConfig command tool in GUI or cmdlet mode, informative error messages aren’t provided. After you install this update, you can understand the error easily.

July 2016 and

DB Version (Content DB) – 16.0.4405.1000

In 3115304:

  • Translates some terms in multiple languages to make sure that the meaning is accurate.

In 3115299:

This security update contains improvements and fixes for the following non-security issues:

  • Add new CSOM APIs for getting term set names of all languages, and for getting and setting group managers and contributors.
  • The setCustomFieldValue method can’t set a custom field through Java scripts.
  • Changes in resource properties aren’t propagated to OData until a Reporting Refresh job is started.
  • The planned work is incorrect on the Approval page.
  • When you reduce the work of a fixed work task while editing in Project in the Schedule Web Part, the duration of the task may be reduced unexpectedly.
  • If you have an enterprise custom field that has a formula that references a custom field with a lookup table, the value may not be set correctly.
  • Assume that you are in edit mode of a project with an unassigned task. When you switch from a task view to an assignment view that has a task ID, the view is stuck in loading and you have to refresh the page to get it to work again.
  • You can’t load timesheet if the ASSN_RESPONSE_PENDING field is set to NULL for one of the assignments.
  • When you change the start date and a multiline text custom field on a project detail page, the multiline text custom field can’t be saved and updated.
  • When you save a project detail page, you receive the CustomFieldRowDoesNotMatchCorrespondingDefinitionInDB error.
  • When you change the start date of an assignment through the My Tasks page, or through the Timesheet page in Single Entry mode, the actual work of the assignment may be changed.

June 2016 and

DB Version (Content DB) – 16.0.4393.1000

In 3115184

  • When you’re denied the permissions to open a project, you receive a generic error message instead of the access denied message. This issue also occurs when you have the access to the project but no view is available to the category in which you are added.
  • Exporting resource assignments to Excel fails.

In 3115181

  • The Resource Plan button is removed from the schedule Web Part and Project Center. Project Server 2016 now offers the Resource Engagements and Capacity Planning features to replace resource plans.
  • You can’t set a Resource Assignment view to be filtered by a custom field, and you receive the following error message:
    An unknown error has occurred.
  • When you try to add or delete a user from a project server security group, you experience an error if the project site is a root web and the host header configuration is enabled.
  • After a project manager rejects a task update, you don’t receive an email notification that informs you of the task rejection.
  • When you’re denied permissions to open a project or view a project schedule in Project Center, you receive the generic “An error occurred while opening your project” error message instead of the more specific access denied message.
  • Assume that you save time for a timesheet without submitting. Then, a project manager deletes it from the project of the tasks on which you saved within your timesheet. When you go to submit the timesheet or a status update for that timesheet, it fails and you receive the following error message:
    An error occurred while communicating with the server. Check connectivity with your administrator to determine whether further action is necessary.
  • If the timesheet unit settings are set to weeks, planned work isn’t displayed in timesheets.
  • A summary task may not correctly compute the rollup value of a custom field if the field is configured with the following properties:
    • A date type
    • A minimum rollup
    • A formula where the value may be null (N/A)
  • You can’t edit and save changes to enterprise resources in Project 2016.
  • When an administrator edits the Proposal Summary Project Detail page, the following error message appears on the page:
    Sorry, something went wrong.
  • Assume that a project server administrator creates an enterprise project template. Then, project managers create a project by using the template and specify an owner for the project. When the project is saved, Project Web App ignores the owner information.
  • It takes a long time for the initial project publish and user synchronization jobs to complete. The end result is that a project manager who creates a project in Project Web App waits for a long time before being able to move to other Project Web App pages.
  • Consider the following scenario:
    • You have a project-level enterprise field that’s linked to a lookup table.
    • The custom field is exposed on a project detail page (PDP).
    • You edit a project on the PDP.
    • You change the value of the custom field as well as other fields such as the project description field.
    • You save the project.

    In this situation, you receive the following error message:

    An error has occurred while saving your project to the server. Please contact your administrator for assistance.

    In addition, the queue job error details state GeneralItemDoesNotExist.

  • After you change the booking type of a resource in a project, the booking type of the resource’s assignments aren’t updated to reflect the new booking type.
  • The status update process fails to update actual work on a project when a custom field formula calculation in the project fails.
  • Cost values are displayed incorrectly when you edit a project in Project Web App. For example, 100$ is displayed as 10.000$.
  • Assume that the Project Web App project editing session of a project has timed out. After you select OK to the “Your session has timed out because of inactivity. To continue editing this project, click OK” message and save the changes, the changes aren’t applied to the project.
  • Enterprise Flag fields don’t save a No value unless you explicitly select the value. Therefore, if you’re looking at this value as you move from one Project Detail Page to another, you may find that the value is displayed as blank or NULL instead of the No value that you expect.
  • The Approvals page doesn’t roll up totals on grouping rows for the timephased data.

May 2016

DB Version (Content DB) – 16.0.4378.1000

  • When you change a resource in the resource center in Project 2016, you receive the following error message if the resource has an email language set:
    The e-mail language for this resource is not valid.
  • Consider the following scenario:
    • A project in which tasks have been published to team members is checked out.
    • As a team member, you assign yourself to a task from the project.
    • You add actual work to the task.
    • You submit the task and work for approval.
    • The new task is approved.
    • The task on which the assignment was made, and it’s deleted from the project and the project is then saved, and checked in.

    In this situation, the update transaction is listed as successful even though the update isn’t  applied.

  • When you add an assignment to an existing task on a timesheet, you receive the following error message:
    error loading.

    This issue occurs if the project name has the “&” character.

  • Within the schedule web part, if you apply a filter on an enterprise field that has a lookup, no tasks are displayed for the project.
  • When a team member submits time against an administrative task and the task requires approval, an e-mail notification intended for the approver is sent to the team member.
  • When you switch to a different filter type on the Manage Queue Jobs page, you may receive the following error message if many jobs are present:
    Sorry, something went wrong.
  • Incorrect availability or capacity is displayed on the Capacity Planning page. For example, 7.5h becomes 8h.
  • Resource Engagement data is deleted after a full publish of a project.
  • After you upgrade Project Server 2013 to Project Server 2016, large PWA sites become read-only.
Skip to main content