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


The product group released the August 2017 Cumulative Update for the SharePoint 2013 product family.

For August 2017 CU we have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.

As this is a common question: Yes, August 2017 CU includes all fixes from August 2017 PU.

ATTENTION:

Be aware that all Updates for SharePoint 2013 require SharePoint Server 2013 SP1 to be installed first.

Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled (see below).

Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.

This CU includes all SharePoint 2013 fixes (including all SharePoint 2013 security fixes) released since SP1. The CU does not include SP1. You need to install SP1 before installing this CU.

The KB articles for August 2017 CU should be available at the following locations in a couple of hours:

  • KB 4011073 - SharePoint Foundation 2013 August 2017 CU
  • KB 4011076 - SharePoint Server 2013 August 2017 CU
  • KB 4011074 - SharePoint Server 2013 with Project Server August 2017 CU
  • There was no fix released for Office Web Apps Server 2013 in August 2017

The Full Server Packages for August 2017 CU are available through the following links:

Important: If your farm has been on a patch level lower than July 2015 CU: July 2015 CU and later contains a breaking change compared to earlier builds which requires running the SharePoint 2013 Products Configuration Wizard on each machine in the farm right after installing the CU.
If you don't run PSCONFIG after installing this CU (on a farm which had a lower patch level than July 2015 CU) crawl might no longer work - so ensure to schedule a maintenance window when installing this CU which includes PSCONFIG runs.
See here for detail: https://blogs.technet.microsoft.com/stefan_gossner/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013/

Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation CU. And the SharePoint Server 2013 with Project Server CU contains Project Server CU, SharePoint Server CU and SharePoint Foundation CU.

Related Info:

Comments (9)

  1. DCConsultant says:

    Has anyone experienced issues with the execute permissions for stored procedures used for Central Admin database after installing this update?

    1. DCConsultant says:

      Looks like it was just my dev environment that had the issue. everything looks good so far.

  2. Zivko Sudarski says:

    Hi,
    After update, Has anyone experienced issues with crawl search result as bellow ? Any other other issue with search.
    1) Full crawl on default content source
    2) Search query issue from public zone
    3) result return with URL path from default zone

    Many thanks,
    Zivko

  3. After installing CU, when running psconfigui, the below error is thrown. I have executed get-spproduct -local and cleared sharepoint cache. Error stills happens. Don’t know what web config could not be found as all apps have their web.config file in place.

    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
    Application Web Config for this IIS site (1) could not be found
    Action 4.0.17.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. (EventID:ajywk)
    Exception: Object reference not set to an instance of an object. (EventID:ajywk)
    (EventID:ajywk)
    Upgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed. (EventID:ajxnm)
    Inner Exception: Object reference not set to an instance of an object. (EventID:ajxnm)
    (EventID:ajxnm)
    Exception: Action 4.0.17.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. (EventID:ajxnm)
    (EventID:ajxnm)
    Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 4.0.17.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. —> System.NullReferenceException: Object reference not set to an instance of an object. — End of inner exception stack trace —

    1. Hi Gregory,
      the error indicates that a web.config file that SharePoint thinks exists does not exist.
      This can happen if the web.config file was deleted or if the whole IIS website was deleted without deleting the associated SharePoint web application in the central admin.
      I would suggest check all SharePoint web applications and verify that for each an IIS web site exists.
      In case that you have extended a web application to multiple IIS websites you would have to verify also each of these.
      Cheers,
      Stefan

      1. Thanks Stefan. No sites or Web Apps have been deleted. we have 8 servers (4 Webapps and 4 WFE) I have executed Config Wizard in 2 Webapps and it failed. Then I have executed this command stsadm -o provisionservice -action start -servicetype spwebservice and now I have been able to execute Config Wizard with no issues. Farm was working fine before applying CU and now we are having this inconvenient. I will keep trying and digging into errors. Thanks.

  4. Andy says:

    Hi Stefan,
    Could you please let me know what is the support lifectycle for SharePoint 2013 SP1 + Latest CU ?
    When will SharePoint 2013 SP1 + latest CU be out of support/extended support ?

    Thanks a lot,
    Andy

  5. Amaresh says:

    I also have trouble after installing the August 2017 in our sharepoint 2013 environment.
    The PSCONFIG is coming back with errors as the patch is missing from other WFE’s, which I have already installed.
    I did run the get-spproduct -local on all the servers.
    fyi – Somehow the (get-spserver $env:ComputerName).NeedsUpgrade returns false on the app server.

Skip to main content