다음을 통해 공유


SharePoint 2016 : May 2016 CU Issue Fixed

In this article, we will list all the issues which is fixed in this May 2016 CU. This month MSFT released two versions of it. One includes the fixes for LPs and others don't include the fix for LPs,

Improvements and Fixes:

This CU brings a lot of Project Sever fixes and also brings the fixes for the Language Packs. Here is the list of fixes published by MSFT.

Project Server 2016

  1. 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.

  2. Consider the following scenario:

    1. A project in which tasks have been published to team members is checked out.
    2. As a team member, you assign yourself to a task from the project.
    3. You add actual work to the task.
    4. You submit the task and work for approval.
    5. The new task is approved.
    6. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. Incorrect availability or capacity is displayed on the Capacity Planning page. For example, 7.5h becomes 8h.

  8. Resource Engagement data is deleted after a full publish of a project.

  9. After you upgrade Project Server 2013 to Project Server 2016, large PWA sites become read-only.

SharePoint Server 2016

  1. Follow sites function fails in the multiple farm topology.
  2. SharePoint help content isn't displayed by using a fallback language for some languages, such as ca-es (Catalan), eu-es (Basque), gl-es (Galician), sr-cyrl-rs (Serbian (Cyrillic)), bs-latn-ba (Bosnian (Latin)), cy-gb (Welsh), mk-mk (Macedonian), ga-ie (Irish), prs-af (Dari), az-latn-az (Azeri (Latin)).

Installation:

As we know, this Month MSFT Released 2 CUs ( one includes the LPs and other no LP).

  • If you have Language Packs Installed in your Farm then you need to Install the sts2016-kb2920721-fullfile-x64-glb.exe on all servers in the farms. After that, you have to run the Config wizard on all server in the farm one by one.
  • If you don't have Language Packs Installed in your Farm then you need to Install the sts2016-kb3115088-fullfile-x64-glb.exe on all servers in the farms. After that, you have to run the Config wizard on all server in the farm one by one.

Prerequisite:

  • To apply this update, you must have Microsoft SharePoint Server 2016 installed.

Restart Information:

  • If during the Installation of the Updates certain components of SharePoint is running then it will ask you to restart the server. So it depends upon your server.

Schema Change:

  • This will update the database schema so that means schema and Patch Version will change. You will see the same Patch number and Build Number.

Patch Number:

  • 16.0.4378.1000

Reference: