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


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

For March 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, March 2017 CU includes all fixes from March 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 March 2017 CU should be available at the following locations in a couple of hours:

  • KB 3172456 – SharePoint Foundation 2013 March 2017 CU
  • KB 3172497 – SharePoint Server 2013 March 2017 CU
  • KB 3172462 – SharePoint Server 2013 with Project Server March 2017 CU
  • KB 3172457 – Office Web Apps Server 2013 March 2017 CU

The Full Server Packages for March 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 (10)

  1. Johan says:

    FYI…
    When installing this update I get following message in the health analyzer. (In all our environments!)
    “Verify that the critical User Profile Application and User Profile Proxy Application timer jobs are available and have not been mistakenly deleted.”

    The ‘Repair automatically’ action fixed this problem.

    Regards,

    Johan

    1. Sikander says:

      Have also got the same Error on Health Analyzer Pst March’17 CU install and “Repair Automatically” fix the error

        1. uzma says:

          This reference is for SP2016, are you stating that this issue is seen in both SP2013 and SP2016?

  2. Neville says:

    After applying this CU when I click on the EDIT link provided for a document in the document’s context menu, it doesn’t open in Office Web Apps but instead opens in the Office client. The document library is set to ‘Use the server default (Open in browser)’. Prior to applying this CU the document would open in Office Web Apps.

    1. Hi Neville,
      you might want to open a support case with Microsoft to get this analyzed.
      Cheers,
      Stefan

  3. After install this CU on my DEV environment ( last installed CU is from July 2016 ) i have this problem :

    Failed to upgrade SharePoint Products.

    An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.
    Additional exception information:
    CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed. (EventID
    :ajxme)

    Exception: The system cannot find the path specified. (EventID:ajxme)

    (EventID:ajxme)

    Cannot upgrade [Microsoft.SharePoint.Administration.SPIisWebSite]. (EventID
    :ajxnf)

    CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed. (EventID
    :ajxme)

    Exception: The system cannot find the path specified. (EventID:ajxme)

    (EventID:ajxme)

    Upgrade completed with errors. Review the upgrade log file located in D:\LogFil
    es\ULS\Upgrade-20170323-101737-45.log. The number of errors and warnings is lis
    ted at the end of the upgrade log file.

    Follow this link for more information about how to troubleshoot upgrade failures
    :
    http://go.microsoft.com/fwlink/?LinkId=259653

    Total number of configuration settings run: 8
    Total number of successful configuration settings: 7
    Total number of unsuccessful configuration settings: 1
    Successfully stopped the configuration of SharePoint Products.
    Configuration of SharePoint Products failed. Configuration must be performed be
    fore you use SharePoint Products. For further details, see the diagnostic log l
    ocated at D:\LogFiles\ULS\PSCDiagnostics_3_23_2017_10_17_29_185_255806164.log an
    d the application event log.

    and I do not really know what I can do now especially when now 5 of 7 sharepoint web application do not work any more

    1. OK I have manage to solve the problem however mysites web app not work any more and it looks like after this CU mysites lost permission levels. None of the users and event site admins cant open the web site of mysites.

      1. Hi Michal,
        I would recommend to open a support case with Microsoft to get this issue analyzed.
        Cheers,
        Stefan

        1. Thanks for advice Stefan

Skip to main content