August 2016 CU for SharePoint 2013 product family is available for download

27 Comments

1. 

   David
   On 10. August 2016 Permalink

   Great information as usual! Thanks for putting the effort into this blog.

   Reply
2. 

   Scott
   On 11. August 2016 Permalink

   Is there not a SP2010 Aug CU this month, or is it just delayed?

   Reply
   1. 

      Stefan Goßner
      On 11. August 2016 Permalink

      Hi Scott,
      SharePoint 2010 is in extended support since nearly a year now which means that only security fixes will be created.
      In August we did not have any security fixes for SharePoint 2010 which is the reason that no CU was released.
      Cheers,
      Stefan

      Reply
      1. 

         Scott
         On 11. August 2016 Permalink

         Thanks, figured but needed to dbl check.

         Reply
3. 

   Darryn Hatfield
   On 12. August 2016 Permalink

   Sorry if I’m missing something here but we have SharePoint Server 2013 SP1 installed and I have downloaded the cumulative update but it only has the cab file which is about 1.4GB. Isn’t there meant to be an accompanying exe file?

   Reply
   1. 

      Stefan Goßner
      On 12. August 2016 Permalink

      Hi Darryn,
      the fix consists of 3 files: 1 exe and 2 cab files:
      ubersrv_1.cab – 1.4 GB
      ubersrv_2.cab – 304.9 MB
      ubersrv2013-kb3115450-fullfile-x64-glb.exe – 1.4 GB
      You need to select all of them in the download page and store them in the same directory.
      Cheers,
      Stefan

      Reply
      1. 

         Darryn Hatfield
         On 12. August 2016 Permalink

         Thanks for the prompt reply. Yes I just saw that. I had a browser issue so it didn’t show me all of the files, it just downloaded the first cab file. All sorted now. Thanks again.

         Reply
4. 

   JD
   On 15. August 2016 Permalink

   What’s about Language Packs? Which Language should I install? Our System is english with german language pack.
   Thx

   Reply
   1. 

      Stefan Goßner
      On 15. August 2016 Permalink

      Hi JD,
      it does not matter which language you select in the dropdown – the package will always be the same.
      There is only a single patch and this contains fixes for all languages.
      Cheers,
      Stefan

      Reply
5. 

   Chandan
   On 25. August 2016 Permalink

   Hi Stefan, I didnt see any post from you on July 2016 CU for SharePoint Server 2013, are there any known issues to be aware of ?

   Reply
   1. 

      Stefan Goßner
      On 26. August 2016 Permalink

      Hi Chandan,
      here is the blog post about July 2016 CU for SP 2013:
      https://blogs.technet.microsoft.com/stefan_gossner/2016/07/12/july-2016-cu-for-sharepoint-2013-product-family-is-available-for-download/
      No new known issues till now.
      Cheers,
      Stefan

      Reply
6. 

   Jake Jacobsen
   On 1. September 2016 Permalink

   Since installing the SharePoint 2013 August 2016 CU I’ve noticed two things. One, I can no longer hide/show pages in the Navigation Settings. Two, all Managed Metadata Site Columns are no longer connected to the MM Service Application Term set. Has anyone else noticed similar issues? Thank you.

   Reply
   1. 

      Stefan Goßner
      On 2. September 2016 Permalink

      Hi Jake,
      it seems you were upgrading from an older CU level.
      The navigation issue was introduced with June CU – a fix is currently planned to be released for October CU.
      The MMS issue is not (yet) a known issue. I would recommend to open a support ticket with Microsoft to get this issue analyzed.
      Cheers,
      Stefan

      Reply
      1. 

         Sharon
         On 14. September 2016 Permalink

         I am unable to hide/show pages & subsites from the navigation in SharePoint Server 2013 (15.0.4849.1000 August 2016 CU), also looking forward to update in October.

         Reply
      2. 

         Thomas
         On 4. October 2016 Permalink

         Hi Stefan,
         Thank you for the post. We’re experiencing the same issue here. Unable to hide / show elements in the navigation. Looking forward to the bug fix this month.

         Reply
7. 

   FeytensJ
   On 2. September 2016 Permalink

   Hi,
   I believe there is something wrong with this update. When updating our SharePoint 2013 Search farms, the update failed with following error message:
   “There is already an object named ‘domain\someADgroup’ in the database. CREATE SCHEMA failed due to previous errors.”
   To fix this, I need to remove manually all the Schema’s, with the name from the error message, from the Search, CrawlStore, AnalyticsReporting and Linkstore databases.
   When running the psconfig command again, the update is successfully.
   This problem is related to the search db’s and SQL schema’s based on AD groups.
   I did a test on two search farm’s in our test environment and always with the same error message. When updating another farm without a search service application configured, everything goes fine.
   Regards,
   Johan

   Reply
   1. 

      Stefan Goßner
      On 2. September 2016 Permalink

      Hi Johan,
      I haven’t seen this error before – looks to be specific to your environment.
      I would recommend to open a support ticket to get this analyzed as manual changes in SharePoint DBs lead to an unsupported environment.
      Cheers,
      Stefan

      Reply
      1. 

         FeytensJ
         On 6. September 2016 Permalink

         Hi Stefan,
         I did the same in our quality environment with the same error message.
         Meanwhile I found the culprit. The problem occurs because we have assigned a global AD security group as administrator for the search service application.
         My workaround without touching the database:
         Remove this group temporarily in “Central Administration->Service Applications->Search Service Application->Administrators”.
         Run Configuration wizard.
         Add the global security AD group back to the Search Service Application administrators.
         Regards,
         Johan

         Reply
      2. 

         FeytensJ
         On 6. September 2016 Permalink

         Sorry, I posted my workaround too early.
         Adding the AD group to the Search Service Application administrators after running the configuration wizard give me the same error message. I Always need to go directly into the search db’s and delete the schema’s.
         I’m going to open a support ticket.
         Thanks,
         Johan

         Reply
8. 

   Mark
   On 14. September 2016 Permalink

   Stefan,
   as always, thanks for your blog. very helpful.
   We are experiencing an issue after applying the August 2016 CU. The CU that had been applied prior to this was Nov 2015.
   It seems that our search relevance is not working like it had in the past. It was “weighted” on a part number column so when a user searched for part number “400” it returned that first. After the CU, it seems to be returning based on how often “400” shows up in the descriptions or other metadata.
   Do you think any of the CU’s after Nov 2015 could have contributed to this behavior? Has there been any search related problems in the previous CU’s
   Thanks!

   Reply
9. 

   sharon
   On 14. September 2016 Permalink

   Seems to be a bug with this fix in Site Look and Feel / Navigation. Can no longer Show/Hide navigation items. System Admin; Site Collection Admin; Site Owners. Go through the steps, it says it’s hidden or show but does not work.

   Reply
10. 

    Robin
    On 28. September 2016 Permalink

    Has this resolved the following issue for anyone: Unable to open SharePoint documents in local client (rich client) from Chrome due to NPAPI plug-in missing
    This update was supposed to address it but I’m still having the issue after applying it.

    Reply
11. 

    Mark
    On 5. October 2016 Permalink

    HI Stephen,
    we applied the AUG 2016 CU (last one was Nov 15 CU) and noticed an issue with listdata.svc. in the past, when a column name started with numeric (ex: 480VKAICRating), the service prepended a c_ to the name. After the CU, it prepends C_. This broke one of our Windows Services that was using this as web reference. We have confirmed this in our Stage and UAT enviroments. We have not applied the CU to production yet.
    Has anybody else reported this? is this the new standard? we don’t want to change our services and then find out that another CU changes it back.

    Reply
    1. 

       Stefan Goßner
       On 6. October 2016 Permalink

       Hi Mark,
       this has not been reported before. I would suggest to open a support case with Microsoft to get this analyzed in more Detail.
       Cheers,
       Stefan

       Reply
12. 

    Uzma Naz
    On 6. November 2016 Permalink

    Hello, in production environment this patch update broke mirroring for the usage_SA. I had to call Microsoft for support to go through diagnostics and identify this issue.

    Reply
13. 

    Dave Clay
    On 23. November 2016 Permalink

    Stefan,
    Have you been privy to any information regarding the Aug2016 CU changing the Require Check Out setting on a library?

    Reply
    1. 

       Stefan Goßner
       On 23. November 2016 Permalink

       Hi Dave,
       have not heard about such an issue.
       Cheers,
       Stefan

       Reply