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


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

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

  • KB 3118361 - SharePoint Foundation 2013 October 2016 CU
  • KB 3118366 - SharePoint Server 2013 October 2016 CU
  • KB 3118365 - SharePoint Server 2013 with Project Server October 2016 CU
  • KB 3118360 - Office Web Apps Server 2013 October 2016 CU - this is also a security fix!

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

  1. Wasea says:

    Hi,
    In the fixes page it say "Navigation settings to hide or unhide items don't work correctly." Just tested in a test environment where the September CU has been installed and seems that the Navigation Setting is not fixed yet. You still cannot select the "Show Pages"
    Regards,

    1. Hi Wasea,
      the fix is in October CU not September cu. Please test on a box where October CU has been installed.
      If the issue still occurs with October CU (after PSConfig has been executed) please open a support case to get your specific issue analyzed.
      Cheers,
      Stefan

      1. Wasea says:

        Hi Stefan,
        Actually I wanted to say that I tested the October CU in a test machine where it was installed the September CU. Actually on that test machine, I install every month the monthly CU's.
        PSconfig has run, as always, but that option is still unavailable.

        Regards,
        Vasile.

        1. Then please open a ticket with Microsoft to get this analyzed.
          Cheers,
          Stefan

          1. SPAdmin says:

            Installing Oct 2016 CU resolved the navigation issue for me. Maybe it is something else?

  2. Krzysztof says:

    Stefan is there a problem with this CU.?
    We can't download it from the site. It crash i middle of download or give an error when extracting the files after the download.
    Could you check this?

    1. Hi Krysztof,
      I just tested and it worked fine for me.
      Cheers,
      Stefan

  3. Gabriel says:

    Hi Stefan,

    Last month after installing Windows updates (no CU) the crawling on one of our farms is stuck and even if i forcefully stop it with powershell, it will simply get stuck again once started. The lastest CU installed is May CU.

    Does October updates fix such issue with search's crawl?

    Thanks!

    1. Hi Gabriel,
      I haven't heard about such an issue.
      Cheers,
      Stefan

  4. Tahir says:

    Hi Stefan,

    From where we can get the list known issues that we may get after installing October 2016 CU. we need to know it before applying on our farm.

    Regards
    TM

    1. Tahir says:

      particularly with SharePoint Server 2013 (Oct 2016 CU)

      Thanks in advance
      TM

    2. Hi Tahir,
      such a list is not available from Microsoft.
      The reason is simple: most known issues only affect a very, very small amount of customers as they occur only in specific scenario.
      In addition side effects for a CU are often reported by customers several months after the CU has been released. So such a list would not be guaranteed to be complete.
      For this reason it is important to test every single fix in a test environment which reflects the environment you are planning to use the fix in to verify if the fix causes any side effects here and open a support ticket if you identify any issues where you suspect that the issue was caused by a problem introduced through the specific fix.
      Cheers,
      Stefan

  5. AnisBO says:

    Hi Stefan,
    In our validation environment, after the installation of this CU, the issue about hiding items in Navigation settings is fixed.

    However, we have many errors with search’s crawl. The error occure with the same message :

    ExpressionBaseCompatibleRec: Attempt to assign value to field MicroBlogType caused exception Microsoft.Ceres.Evaluation.DataModel.Types.SchemaException: Invalid value for long field
    at Microsoft.Ceres.Evaluation.DataModel.BuiltInFields.PrimitiveInt64Field.set_Value(Object value)
    at Microsoft.Office.Server.Search.Query.Pipeline.Utilities.ExpressionBaseCompatibleRec`1.PopulateCompatibleRec(IRecord data)

    After installing this CU in another environment, this error is still there.

    1. Hi AnisBO,
      this sounds like a known issue if hybrid search is configured.
      A fix for this is currently planned for January 2017 CU.
      Cheers,
      Stefan

      1. BlueSky2010 says:

        Hi AnisBO, have you had a chance to try Jan 2017 CU to see if that fixes the Hybrid Search issue or not? Appreciate any feedback!

        1. Sobhash Prasad says:

          Hi AnisBO,

          Any update if this issue got resolved for you or you still have this issue. In JAN 2016 CU issue with Search within Task lists is not working was found by MS so now we are looking for your feedback as how you resolved your Hybrid search issue.

          Thanks for your help.

    2. Wes Niemi says:

      Hi Stefan,

      We are also getting the following error in our logs for SharePoint 2013 onprem: ExpressionBaseCompatibleRec: Attempt to assign value to field MicroBlogType caused exception Microsoft.Ceres.Evaluation.DataModel.Types.SchemaException: Invalid value for long field
      at Microsoft.Ceres.Evaluation.DataModel.BuiltInFields.PrimitiveInt64Field.set_Value(Object value)
      at Microsoft.Office.Server.Search.Query.Pipeline.Utilities.ExpressionBaseCompatibleRec`1.PopulateCompatibleRec(IRecord data)

      We did not configure the hybrid Search. We are currently on March 2017 CU (15.0.4911.1000).

      Any resolution for this in the works?

      Thanks,

      Wes.

      1. Hi Wes,
        this was in error we knew before January 2016 CU but only when using Hybrid Search.
        As you are on a newer CU: this has not been reported to us - so no fix for this in the works.
        Cheers,
        Stefan

  6. Mark Graff says:

    Our search was broken after this update. We tried recreating the crawl (which was running error-free) and indexes. Logs continued to show an error: "SqlError: 'Could not find stored procedure 'proc_MSS_GetUrlMapping'". This was resolved by running PSConfig.

    1. Hi Mark,
      you should always run PSConfig after installing a fix.
      This is the only way to e.g. apply fixed included in the CU for stored procedures into the database.
      Cheers,
      Stefan

  7. Uzma says:

    Hi there

    Have noted that in this KB https://support.microsoft.com/en-us/kb/3118371

    There is a change on the SQL side.

    I am planning to install the latest CU (Nov) so does this mean I MUST amend registry in view of the October CU?

    1. The registry changes should be optional.

  8. Oleksandr says:

    Hi Stefan,
    After the installation of this CU, managed metadata column button "Browse for valid choice" is now displayed on right top corner above the column, instead of it's default (in line) position.

    1. Oleksandr says:

      Hi Stefan,
      Kindly provide any information about this type of behavior.
      Time is of the essence.
      Thank you in advance, your help will be highly appreciated.

      1. Hi Oleksandr,
        I'm not familiar with such a change. If that is important for you, please open a support case with Microsoft.
        Cheers,
        Stefan

  9. Sobhash Prasad says:

    Hi Stefan,
    We already have hybrid search configured in SharePoint 2013 and has installed Feb 2016 CU and now we are planning to install December 2016 CU. In October 2016 CU hybrid search issue was found and a fix for this is currently planned for January 2017 CU.
    So can you please let me know if December 2016 CU will create issues with Hybrid search for our environment as CUs are cumulative update which include previous packages as well, should we go for it or is it resolved now or do you suggest any other CU.

    Thanks for your help as always.

    1. Hi Sobhash,
      each environment is different. For this reason we recommend to evaluate all hotfixes in a test environment before applying them on production.
      Cheers,
      Stefan

      1. Sobhash Prasad says:

        Hi Stefan,

        We have configured Hybrid search only in production environment so I wanted to check with you if we still have Hybrid search issue in December 2016 CU which was identified in Oct 2016 CU.

        Thanks for you prompt reply.

        1. Hi Sobhash,
          which specific hybrid search issue do you mean?
          Cheers,
          Stefan

  10. Sobhash Prasad says:

    Hi Stefan,
    In this blog it self you replied on November 16, 2016 at 2:44 pm. can you please see above.

    Hi AnisBO,
    this sounds like a known issue if hybrid search is configured.
    A fix for this is currently planned for January 2017 CU.
    Cheers,
    Stefan

    1. Hi Sobhash,
      ok thanks for the additional context - but sorry I don't have the info if and when it got fixed available right now.
      I would recommend to test it in your test environment yourself.
      Cheers,
      Stefan

      1. Sobhash Prasad says:

        Hi Stefan,

        Thanks for your help and support.

  11. Rkakkar says:

    Hello Stefan,

    Apologies if I am repeating the Same thing

    If Project Server CU is installed , It also contains CUs for SharePoint SErver & FOundation as well, Am I correct

Skip to main content