In this article, we will list all the issues, which are fixed in this past May's 2017 CU. This Month MSFT released two versions of it, one includes the Fixes for LPs and others don’t include the Fix for LPs. Now it is irrelevant that what language pack you installed or what the base language of the SharePoint is. You just simply install both exes and it will take care of everything.
What’s Included
This CU includes all the previous CUs since SharePoint 2016 RTM. This CU also includes the Feature Pack 1.
The following features are part of Feature Pack 1.
- Administrative Actions Logging
- MinRole enhancements
- SharePoint Custom Tiles
- Hybrid Auditing (preview)
- Hybrid Taxonomy (preview)
- OneDrive API for SharePoint on-premises
- OneDrive for Business modern experience (available to Software Assurance customers)
Note
This CU also a security update, which means you do not need to apply security updates separately if you apply this CU.
Improvements and fixes
This CU brings SharePoint & Project Server fixes, here is the list of fixes published by MSFT.
Project Server 2016
Security FIx
- When you run an administrative backup and an administrative restore of Enterprise custom fields, the restore fails at 29 percent completion. You also see a DatabaseForeignKeyViolationError (50002) queue error.
- The March 2017 public update provided the necessary WSDL files in order to programmatically access the Project Server Interface (PSI). However, the WDSL files were not completely correct. Therefore, even after the update is installed, it wasn't possible to access the various PSI end points.
SharePoint Server 2016
This update contains the following improvements and fixes for SharePoint Server 2016:
- Enable administrators to change document parsing timeout and memory limit.
- Adds a PreserveDeletedUserMetadataReferences switch to Import-SPWeb. Adding this switch lets references to deleted users who are referenced by the list item author and editor metadata be preserved.
- Translates some terms in multiple languages to make sure that the meaning is accurate.
Security Fix
- When you lose SharePoint sites that are upgraded from SharePoint 2013 to SharePoint 2016, sites fail to load because of multiple web parts are not upgrading and referencing the wrong version. SSRS Web Part and SPListFilter are two examples. After you install this update, the upgrade of such pages will complete without errors.
- When you run an administrative backup and an administrative restore of Enterprise custom fields, the restore fails at 29 percent completion. You also see a DatabaseForeignKeyViolationError (50002) queue error.
- For remote SharePoint calls in hybrid, the query rewrite in the result source is added to the query two times. This could cause an unexpected recall for custom query rewrites
- SharePoint outbound email messages incorrectly try to authenticate to SMTP servers that support Generic Security Service Application Program Interface (GSSAPI), Kerberos, or NTLM authentication. This may prevent email messages from being sent. After you install this update, SharePoint sends email messages anonymously without authentication.
Language-Dependent Fix
- Translates some terms in multiple languages to make sure that the meaning is accurate.
- After you apply an update for a SharePoint language pack, certain performance counters are deleted but are not recreated. This causes the ULS logs to flood with error messages because of the missing performance counters. After you install this update, performance counters are no longer deleted in this case. The previously deleted performance counters will be recreated.
Installation
As we know, this Month MSFT Release 2 CUs (one Include the LPs related fix and Other Non LP related fixes).
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 the SharePoint are running then it will ask you to restart the server. So it depends upon your server.
Schema Change
- This update updates the database schema so that the mean schema and Patch Version will change. You will see the same Patch number and Build Number.
Patch Number
Known Issue with CU
This CU also fixes the longer time issue with Installation of packages.
Reference
See Also
Please check this Wiki for the SharePoint 2016 Build Numbers
Join the conversation! Your thoughts help the community grow.