SharePoint 2016, Sharepoint 2013, Sharepoint 2010, Windows Server 2012, Sql Server 2012,2014,IIS, Active Directory,User Profile Service, Managed MetaData Service, Search Service, Topology, Web Application, IIS, Site collection, List, Library, PowerShell, office web app, Windows Authentication, NTLM, Kerberos, Saml, ADFS, Active Directory Import, MIM, SharePoint 2016 : August 2016 CU Issue Fixed – SharePoint

SharePoint 2016 : August 2016 CU Issue Fixed

    • In this article, we will list all the Issues which is fixed in this August 2016 CU. This Month MSFT released two versions of it, One include the Fixes for LPs and others dont include the Fix for LPs,

      Improvements and fixes:

      This CU brings a lot Project Sever Fixes and also bring the fixes for the Language Packs. here is the list of fix published by MSFT

      SharePoint Server 2016:


      1. Translates some terms in multiple languages to make sure that the meaning is accurate.
      2. Adds a new public API for getting all terms in a term set. This API always includes children of deprecated terms.
      3. Other people’s queries are available to users in the QLogClickedText managed property. The QLogClickedText managed property isn’t displayed in the default search results but is returned from the search engine. The QLogClickedTextmanaged property has changed its default from being retrievable to not being retrievable. The past default can be restored by making the QLogClickedText managed property retrievable in the Search Schema management.
      4. This update will allow to remove search results from the index until the next incremental crawl.
      5. When you run the SharePoint Products Configuration Wizard (PSConfig), an error occurs. The error message on the result summary page or in the result summary command line output is generic and doesn’t provide enough information to help fix the problem. This update now presents detailed error messages to identify which failures affect critical configuration tasks and which failures affect noncritical configuration tasks in the PSConfig summary. Error messages about missing SharePoint features now include the feature title instead of just the feature GUID. Error messages are displayed when the upgrading or updating has been improved. Finally, the summary message includes instructions for how to retry the configuration tasks that failed.
      6. When you create a Visual Studio workflow and use the WaitForItemEvent activity against an item, the item ID is ignored.
      7. When you try to refine a search by using the blank text box and enter the quotation mark, or enter several letters and use the auto-complete quotation marks, you receive the following error message:
                    Property doesn’t exist or is used in a manner inconsistent with schema settings.
      8. When some products or updates are installed on a SharePoint Server 2016 based computer, the SharePoint configuration database may be unaware of the installed product or update. This can cause a failure when the SharePoint Products Configuration Wizard (PSConfig) is running to do an upgrade. PSConfig will now automatically update the product and update state for the local server in the configuration database to avoid the failure.
      9. If you write a custom refiner that inherits the RefinementCategory class, the created query isn’t scoped correctly.
      10. When you try to add a source or location to an E-discovery set or an E-discovery case, you receive an exception if E-Discovery on-premises is connected by using a Cloud Search Service Application (SSA).
      11. A Compliance Policy Center isn’t provisioned completely when the server time zone isn’t set to UTC+0. No error is visible for the end-user, the ULS log contains the following event:
        Information Policy Management asv22 Unexpected Error creating Dar Task Aggregate items for policy center.
        When you set up the DLP scenario, the DAR task list stays empty. This prevents the DLP functionality to work.
      12. PSConfig may throw an exception when it’s logging error messages for its summary if the error string is null.

      Project Server 2016:


      1. Improves performance for the CSOM API GetByUser method from the Enterprise Resource Collection when there are thousands resources in Project Server.
      2. In the SharePoint Central Administration Health Analyzer, the Missing server side dependencies Configuration rule shows multiple errors that should not be listed. For example, on the Configuration category, the explanation says:
        [Upgrade] The number of column pool tables exceeds the database limit. The tables that exceed this limit and should be dropped.
      3. Assume that the Single Entry Mode timesheet setting is enabled. When a timesheet user receives status notifications, the link in the received email navigates to the My Tasks page instead of the Timesheet page.
      4. SQL Lock escalation is disabled by default for SharePoint content databases. This causes large databases to fail during the migration from Project Server 2013 to Project Server 2016 because of memory constraints.
      5. After earned values are calculated in PWA from the schedule project detail page, the values may not be saved. This means the published views of the earned values may not be accurate.

      Language Dependent Fix:


      1. Translates some terms in multiple languages to make sure that the meaning is accurate.
      2. This update will allow to remove search results from the index until the next incremental crawl.
      3. When you run the SharePoint Products Configuration Wizard (PSConfig), an error occurs. The error message on the result summary page or in the result summary command line output is generic and doesn’t provide enough information to help fix the problem. This update now presents detailed error messages to identify which failures affect critical configuration tasks and which failures affect noncritical configuration tasks in the PSConfig summary. Error messages about missing SharePoint features now include the feature title instead of just the feature GUID. Error messages are displayed when the upgrading or updating has been improved. Finally, the summary message includes instructions for how to retry the configuration tasks that failed.
      4. When some products or updates are installed on a SharePoint Server 2016 based computer, the SharePoint configuration database may be unaware of the installed product or update. This can cause a failure when the SharePoint Products Configuration Wizard (PSConfig) is running to do an upgrade. PSConfig will now automatically update the product and update state for the local server in the configuration database to avoid the failure.
      5. When you run the PSconfig command tool in GUI or cmdlet mode, informative error messages aren’t provided. After you install this update, you can understand the error easily.

      Installation:

      As we know, this Month MSft Release 2 CUs( one Include the LPs and Other No LP). As a recommended way, you should install both patches

      • Patch with Language Packs  wssloc2016-kb3115441-fullfile-x64-glb.exe
      • Patch without Language Packs  sts2016-kb3115437-fullfile-x64-glb.exe 

      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’s mean schema will and Patch Version will be change.You will see the same Patch number and Build Number.

      Patch Number:

      • 16.0.4417.1000

      Reference:

      See Also:

      Please check this Wiki for the SharePoint 2016 Build Numbers

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *