In this article, we will list all the issues of SharePoint 2016 that are fixed in the June 2016 CU. This month, MSFT released two versions of it. The first one includes the fixes for LPs while the other one does not.

Improvements and fixes

This CU brings many Project Sever fixes, especially for the Language Packs. Here is the list of fixes published by MSFT

Project Server 2016

Error message "Sorry, something went wrong"

Correlation ID: xxxxx
Date and Time: xxxx.

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

SharePoint Server 2016

  • Update SharePoint PowerShell cmdlet Help files.
  • To install the third-party notice file, it has to be embedded and put it in the top-level installation directory.
  • Update SharePoint Insights strings in multiple languages to make sure the consistency.
  • Translate some terms in multiple languages to make sure that the meaning is accurate.
  • Update translations of PowerPoint Conversion Service strings in multiple languages to make sure that the meaning is accurate.
  • Update translations for My Site strings in Polish in SharePoint Server 2016 to make sure that the meaning is accurate.

Fixes the following issues,

  • After you install this update, each error message displayed on the UI is limited to 2048 characters and an error tag is present at the end of each error message.

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

Language Dependent Fix

Installation

As we know, this Month MSFT Release two CUs (one Include the LPs and Other No LP). It is irrelevant which package you need to install (language independent or Language dependent) because Microsoft recommends installing both packages. Order of installation doesn’t matter, you can install either first. You need to Install the wssloc2016-kb3118295-fullfile-x64-glb.exe and sts2016-kb3118289-fullfile-x64-glb.exeon on all server in the farms. After that, you have to run the Config wizard on all server in the farm one by one.

Prerequisite

Restart information

Schema Change

Patch Number

Reference

See Also

In this PU, we have a couple of known issues so beware before applying it to your SharePoint farm.

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

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

Note

Microsoft confirms this issue fix in November 2016 PU.

See Also

Please check this Wiki for the SharePoint 2016 Build Numbers