In this article, we will list all the issues which are fixed in this January's 2017 CU. This month, MSFT released two versions of it, one includes the fixes for LPs and the other one doesn't. Now it is irrelevant which language pack you installed or the base language of SharePoint. You just simply install both the .exe files and it will take care of everything. Security updates are also part of the packages.
What’s Included
This CU includes all the previous CUs since SharePoint 2016 RTM. This CU also includes the Feature Pack 1.
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)
Improvements and fixes
This CU brings a lot of SharePoint & Project Server fixes, here is the list of fixes published by MSFT.
Project Server 2016
When you apply status updates in PWA, actual work is added to some assignments unexpectedly. For example, you have an assignment that has 35 hours total work, and the status update is to apply 9 hours. When you view the results in Project Professional, you find that the assignment is unexpectedly completed. Meanwhile, the total work and the actual work have increased to 400 hours.
SharePoint Server 2016
Fixes
- Some terms are translated into multiple languages to make sure that the meaning is accurate.
- You can't access the Shortcuts link through the keyboard in grid edit mode of a SharePoint task list. Additionally, screen readers can't read or access information panels in SharePoint Server 2016.
- The PSConfig tool may recommend incorrect cmdlets.
- Sometimes, the PSConfig tool shows the upgrade as 100 percent completed even though it still takes some time before the tool moves to the next status. This problem occurs because the tool must complete some minor steps after it upgrades the products. Progress messages are displayed in these steps.
- Fixes the following cmdlet legacy issues of the Administrative Actions Logging feature:
- Support partial execution for the cmdlet and update the help document correspondingly.
- Refine the messages for some exceptions and logs.
- After you try to configure and use the Lotus Notes connector for SharePoint Server, the crawl fails.
- You can't use the CSOM API to set the BookingType property for enterprise resources in projects.
- A system access control list (SACL) isn't read correctly for large file paths that exceed the Windows limitation of 260 characters. This causes the SACL to be discoverable by any user in the query results even if the user doesn't have the appropriate permissions.
- After you make multiple changes to the same user in quick succession in SharePoint Server 2016, the Quick Sync job can't be completed successfully.
- When you configure hybrid taxonomy, the specified Local Term Store Name parameter is now case-insensitive even though it was previously case-sensitive.
- You can't restore site collection that has site URLs. Additionally, you receive the following error message:
- Error: Violation of PRIMARY KEY constraint 'PK_SiteUrlMap'. Cannot insert duplicate key in object 'dbo.SiteUrlMap'
- When you add a subtask to an existing subtask of a SharePoint task list, multiple subtasks are created instead of just one subtask, in certain conditions.
- When you copy and paste subtasks in grid edit mode of a SharePoint task list, multiple subtasks are created unexpectedly.
- SharePoint Server 2016 becomes unresponsive and the server experiences high CPU usage that requires a restart. Additionally, you can't access sites, or you get extremely slow page load times.
Language-Dependent Fix
- Translates some terms in multiple languages to make sure that the meaning is accurate.
- Translates some terms in Brazilian for Project Online.
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 Component of the SharePoint is running then it will ask you for the Restart the server. So its depend upon your server.
Schema Change
- This update will update the database schema so that the mean schema will 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.