A new cumulative update for SharePoint Server 2016 has been released (May 2017 CU).
This CU also includes Feature Pack 1, which has been included since the November CU (November 2016 CU).
SP Build: 16.0.4534.1000
SharePoint 2016 CU – KB articles describing the CU:
- KB 3191880 – May 2017 Update for SharePoint Server 2016 (language independent)
- KB 3191884 – May 2017 Update for SharePoint Server 2016 (language dependent fixes)
- KB 3191915 – May 2017 Update for Office Online Server 2016
SharePoint Server 2016 CU – CU download link:
- Download May 2017 Update for SharePoint Server 2016 (language independent)
- Download May 2017 SharePoint Server 2016 (language dependent fixes)
- Download May 2017 Office Online Server 2016
After installation, remember to run the SharePoint 2016 Products Configuration Wizard (SharePoint 2016 Products Configuration Wizard), or the following command:
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install
Notice
Always install both packages in this order:
- language independent (updates language-independent components and increases the SP Build version)
- language dependent (updates language-dependent components)
For language-dependent packages, it does not matter which language you select, as each package contains updates for all languages.
If you install a new language pack on your SharePoint Server 2016 farm, you must then reinstall the language-dependent update package.
Remember that Distributed Cache must also be updated alongside SharePoint; see How to update Distributed Cache correctly.
Included fixes and improvements
This CU includes the following fixes and improvements.
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.
- When you lose SharePoint sites that are upgraded from SharePoint 2013 to SharePoint 2016, sites fail to load because of multiple web parts 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.
- 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.
- Translates some terms in multiple languages to make sure that the meaning is accurate.
Project Server 2016
- 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.
- 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.
Komentáře