In this article, we will list all the issues of SharePoint 2016 that are fixed in the October 2016 CU. This month, MSFT released two packages and we should install them both.
Improvements and fixes
This CU brings a lot of SharePoint Server fixes. Here is the list of fixes published by MSFT -
Project Server 2016
In this CU, there is no fix included for the Project server 2016.
SharePoint Server 2016
- Translates some terms in multiple languages to make sure that the meaning is accurate.
- The update defaults the Site.GetChanges method to 1000 changes instead of 0 when you use client-side object model (CSOM).
- If you insert comments to a document in SharePoint Server 2016 that has Visio Services, the time in the comments is displayed incorrectly if you view it on the same day at least 2 hours later. For example, 2 hours ago is displayed as 2 minutes ago.
- Assume that a SharePoint farm is configured so that team sites are on web application "A" and personal sites are on web application "B." When you try to view document libraries for a followed team site from the OneDrive for Business library through the Site Folders feature, you receive the following error message,
- This site doesn't have any document libraries. If you want to have documents associated with this site, just add a document library to it.
- When you update the background page, data-connected shapes on the background page aren't updated with the new data.
- After you switch views in an InfoPath form in Internet Explorer 11, the People Picker control displays the following error message:
a. JSON IS UNDEFINED
- When you check the data through the decomposition tree on a PerformancePoint dashboard, a loading screen is displayed and never goes away.
- The title of .vsdx documents is erased or deleted during the approval workflow execution in SharePoint Server 2016.
- Even though there are some products and updates missing on a local server, PSConfig doesn't stop joining the server to a farm. Additionally, there's a .Net framework error when you join the server to a farm.
- Provides client-side object model (CSOM) API to obtain information for web applications and site collections.
- Intermittent failure when you mount and upgrade a content database from SharePoint Server 2013.
- The license upgrade time-out issue documented in the September 2016 public update is fixed. SharePoint Server 2016 license upgrade operations will no longer fail from timing out.
- User information is corrupted because of the timing issues with Windows SharePoint Services (WSS) synchronization and site migration.
Language Dependent Fix
Translates some terms in multiple languages to make sure that the meaning is accurate.
Installation
As we know, this month, MSFT released 2 CUs (one includes the LPs and the other one with no LP).
Prerequisite
- To apply this update, you must have Microsoft SharePoint Server 2016 installed.
Restart information
- If during the Installation of the Updates certain Component of the SharePoint is running then it will ask you for the Restart the server. So it depends upon your server.
Schema Change
- This update will update the database schema so that the schema and patch version will be changed. You will see the same Patch number and Build number.
Patch Number
- 16.0.4444.1000 or 16.0.4444.1004
Known Issue with CU
This CU also includes improvements related to the installation of packages but still, installation time is a bit higher.
Reference
See Also
Please check this Wiki for the SharePoint 2016 Build Numbers.