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


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

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

  • KB 4011173 - SharePoint Foundation 2013 October 2017 CU
  • KB 4011177 - SharePoint Server 2013 October 2017 CU
  • KB 4011175 - SharePoint Server 2013 with Project Server October 2017 CU
  • KB 4011231 - Office Web Apps Server 2013 October 2017 CU

The Full Server Packages for October 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 (22)

  1. Brad says:

    Hi Stefan,

    I’m working through applying the October Cumulative updates for SharePoint and in both my SharePoint Farms I am seeing bizarre issues. On one I am consistently receiving the error below, I’ve tried a bunch of the suggestion on the web with no luck. Any thoughts on this, I’ve never had an issue like this applying updates.

    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
    Upgrade [SPContentDatabase Name=SP2013DEV_CONTENT] failed. (EventID:ajxnm)

    Exception: Object reference not set to an instance of an object. (EventID:ajxnm)

    (EventID:ajxnm)

    (EventID:ajxnm)

    Upgrade Timer job is exiting due to exception: System.NullReferenceException: Object reference not set to an instance of an object.
    … (EventID:aj0ur)

    1. Hi Brad,
      if you need assistance to analyze the issue ensure to open a ticket with Microsoft Support.
      Cheers,
      Stefan

  2. Andreas says:

    Hi Brad,

    starting the following services at “configurationtask 8” of “SharePoint Products Configuration Wizard” solved the problem for me.

    $foo = get-service “SPTimerV4”
    $foo.start()
    $bar = get-service “IISSVCS”
    $bar.start()

    1. Brad says:

      Hi Andreas,

      Yep that’s what did it for me after many hours of reading. Thanks for the tip.

  3. iamgeorgem says:

    Hi Stefan, which Sharepoint 2013 CU will support SP4 for SQL 2012?

    1. There is no specific CU required.

  4. Jatin says:

    Hi Stefan,
    After installing this CU we are unable to create any sites. This issue is also mentioned at http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=346 that multiple people have had this issue.

    The error is

    Application error when access /_layouts/15/newsbweb.aspx, Error=Common Language Runtime detected an invalid program.
    at Microsoft.SharePoint.WebControls.TemplatePicker.RegisterWebTemplateClientScript()
    at Microsoft.SharePoint.WebControls.TemplatePicker.OnPreRender(EventArgs e)
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) e041269e-de3e-802d-746e-7d3742eb2725

    System.InvalidProgramException: Common Language Runtime detected an invalid program.
    at Microsoft.SharePoint.WebControls.TemplatePicker.RegisterWebTemplateClientScript()
    at Microsoft.SharePoint.WebControls.TemplatePicker.OnPreRender(EventArgs e)
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) e041269e-de3e-802d-746e-7d3742eb2725

    Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.InvalidProgramException: Common Language Runtime detected an invalid program.
    at Microsoft.SharePoint.WebControls.TemplatePicker.RegisterWebTemplateClientScript()
    at Microsoft.SharePoint.WebControls.TemplatePicker.OnPreRender(EventArgs e)
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Control.PreRenderRecursiveInternal()
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    at System.Web.UI.Page.HandleError(Exception e)
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    at System.Web.UI.Page.ProcessRequest()
    at System.Web.UI.Page.ProcessRequest(HttpContext context)
    at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) e041269e-de3e-802d-746e-7d3742eb2725

    Cheers
    Jatin

      1. Hi Jatin,
        please ensure to open a support ticket for this to request a fix.
        Cheers,
        Stefan

    1. Tim B says:

      Sounds like this is an issue with just Foundation: https://thesharepointfarm.com/2017/10/october-2017-cu-site-creation-error-sharepoint-foundation-2013/

      Standard, Enterprise, and Project builds aren’t experiencing the problems.

    2. Prasad says:

      I’m seeing this issue as well – cannot create sites anymore. More reports of this issue:

      https://thesharepointfarm.com/2017/10/october-2017-cu-site-creation-error-sharepoint-foundation-2013/

  5. John says:

    Hi Stefan,

    I couldn’t help but notice that with this CU the size of ubersrv_2.cab suddenly dropped to 277.9 MB, after staying in a range of 335 to 340 MB for the previous year of updates. That was a real red flag for me! Where these are cumulative, I always assumed the CAB files would stay around the same size or grow in size from month to month.

    1. Hi John,

      everything is fine here!
      The packaging team identified some packages being included in our previous CUs which contained fixes which were released between RTM and SP1. As our patches can only be installed on SP1 the packaging team decided to remove the additional unnecessary packages.

      Cheers,
      Stefan

  6. Pradeep says:

    Hello Stefan,

    We have installed October 2017 Cu on our Farm, The DB configuration Version is Showing as 1001 instead of 1002 .

    Is this an issue ?

    Thanks,
    Pradeep

    1. Hi Pradeep,
      the database schema version is not always identical with the build number the most recent SharePoint component in a fix.
      These are different things and you should not use the DB Config version to verify patch installations.
      See here for details:
      https://blogs.technet.microsoft.com/stefan_gossner/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/
      Cheers,
      Stefan

  7. SNJ says:

    Hi Stefan,
    We have Sharepoint Server 2013 with SP1 installed (version 15.0.4571.1502).
    If I now want to reach the latest version (this from October 2017), can I just install the latest Full Server Packages for Sharepoint Server 2013?

    The link in your text, [Download SharePoint Server 2013 October 2017 CU], says CU but isn’t it a Server/Uber Packages?
    Because if I have understood it correct; a Server/Uber Packages not only include patches for the components updated in the current CU but also all patches released for other components of the product.
    CU, on the other hand, only contain cumulative update for the components in that specific CU.

    Should I go for latest patch, 2017-Oct, or should I step through all patches from May 2015?

    Best Regards
    Stefan

    1. Hi Stefan,
      if not stated otherwise the links in my SharePoint 2013 blog posts always point to the full server packages of the current CU.
      You can see that also from the following sentence in the blog post: “The Full Server Packages for October 2017 CU are available through the following links:”
      Cheers,
      Stefan

      1. SNJ says:

        Thank you for your answer. I read the blog post to fast so I missed that sentence ;-).
        From your experience, should I go for this Full Server Update from 2017-October or should I take step by step from May-2014 (as I said earlier we only have version 15.0.4571.1502)?
        /Stefan

        1. Hi Stefan,
          installing all the fixes in between is just wasting time. The full server packages is all you need.
          Cheers,
          Stefan

  8. S. M. Rabiul Islam says:

    Hi Stefan,

    After updating October 2017, CU. We are having issue like deployment getting stuck.
    When we did run configuration wizard, it run fine in app-server. In web-server configuration wizard failed at step9 with error
    “Failed to add the service connection point for this farm”
    The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=robi,DC=com,DC=bd doesn’t exist in the directory.

    However, we run configuration wizard in web-server using command psconfig -cmd upgrade -inplace b2b -wait -force
    It was successful then. But since patch applied wsp-deployment hangs on.
    This is a major issue for client, please advice.

    1. Hi,
      this is not an issue I have seen so far. My suggestion would be to open a support ticket with Microsoft to get this analyzed.
      Cheers,
      Stefan

    2. RN says:

      Hello Rabiul,

      First run the below command on your SharePoint server and check if you see any timer service instance disable.
      $farm = Get-SPFarm
      $farm.TimerService.Instances | where {$_.Status -ne “Online”}

      IF you find it disable, then you need to start it using below command.

      $farm = Get-SPFarm
      $disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne “Online”}
      if ($disabledTimers -ne $null)
      {
      foreach ($timer in $disabledTimers)
      {
      Write-Host “Timer service instance on server ” $timer.Server.Name ” is not Online. Current status:” $timer.Status
      Write-Host “Attempting to set the status of the service instance to online”
      $timer.Status = [Microsoft.SharePoint.Administration.SPObjectStatus]::Online
      $timer.Update()
      }
      }
      else
      {
      Write-Host “All Timer Service Instances in the farm are online! No problems found”
      }

Skip to main content