October 2019 CU for SharePoint Server 2016 is available for download

The product group released the October 2019 Cumulative Update for SharePoint Server 2016 product family.

This CU also includes Feature Pack 1 which was released with December 2016 CU and Feature Pack 2 which was released with October 2017 CU.

The KB articles for October 2019 CU are available here:

  • KB 4484111 – October 2019 Update for SharePoint Server 2016 (language independent) – This is also a security update!
  • KB 4484115 – October 2019 Update for SharePoint Server 2016 (language dependent)

The download for October 2019 CU is available here:

Important: It is required to install both fixes (language dependent and independent) to fully patch a SharePoint server. This applies also to servers which do not have language packs installed. The reason is that each SharePoint installation includes a language dependent component together with a language independent component. If additional language packs are added later (only) the language dependent fix has to be applied again.

It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.

After installing the fixes you need to run the SharePoint 2016 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct options.

SharePoint 2016 October 2019 CU Build Numbers:

Language independent fix: 16.0.4912.1000
Language dependent fix: 16.0.4912.1000

To understand the different version numbers please have a look at my article which explains the different SharePoint build numbers.

Related Links:

10 Comments


  1. Hi Stefan,

    We are upgrading to October 2019 CU and while running configuration wizard we got below error –

    Failed to upgrade SharePoint Products.

    This is a critical task. You have to fix the failures before you can continue. Follow this link for more information about how to troubleshoot upgrade failures: http://go.microsoft.com/fwlink/?LinkId=259653

    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:
    Feature (Name = [WorkflowActionSiteProperty Feature1], Id = [******************], Description = [], Install Location = [WorkflowActionSiteProperty_WorkflowActionSitePropertyFeature]) is referenced in database [Wss_Content], but isn’t installed on the current farm. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade. (EventID:ajxkh)

    Feature (Name = [******************], Id = [******************], Description = [This feature deploys the assets specific to the ***site.], Install Location = [******************]) is referenced in database [Wss_Content], but isn’t installed on the current farm. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade. (EventID:ajxkh)

    Feature (Name = [******************], Id = [******************], Description = [This feature deploys the assets specific to the *** site.], Install Location = [******************]) is referenced in database [WSS_Content_People02d], but isn’t installed on the current farm. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade. (EventID:ajxkh)

    Upgrade completed with errors. Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS\Upgrade-20191014

    Can you please help/suggest how to resolve this, you’re quick help would be highly appreciated since I need to complete this on priority.

    Thank.

    Reply

    1. Hi Samir,
      the errors are pretty self explaining: the specific content databases in the farm are referencing custom features which are not installed on the farm.
      Either you moved the databases from a different farm where these features were installed or you uninstalled the features from the farm without removing the features from the sites and site collections inside your content database.
      To fix this you should evaluate the purpose of the missing features and install them if required. Alternatively you can try to remove the features from the referenced sites and site collections using PowerShell.

      If you need assistance with these steps I would suggest to open a support ticket with Microsoft.
      Cheers,
      Stefan

      Reply

  2. I’ve noticed on the content database properties for the farms I’ve applied the October CU, the following —

    Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: 16.0.4912.1000, Maximum Schema Version: 16.0.4909.1000

    How can the current version be higher than the maximum version? The current # matches the build number of the update.

    Reply

    1. Hi Lee,
      I would suggest to open a ticket with Microsoft support to get this investigated.
      Cheers,
      Stefan

      Reply

  3. After this PU, unable to click on Calendar Overlay links

    Reply

    1. Hi Jeff,
      we have received a support case on this matter and the PG is currently investigating the issue.
      If you need a fix you should open a support case for this.
      Thanks,
      Stefan

      Reply

  4. We’ve just had our first reports of this issue so curious if anyone knows if a fix will be in the Nov. CU’s out next week? If not we’ll open a support ticket.

    Thanks

    Reply

    1. Hi Allison,

      in case you are talking about the calendar overlay issue: the fix will not be in November CU.

      Cheers,
      Stefan

      Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.