The product group released the October 2019 Cumulative Update for the SharePoint 2013 product family.
For October 2019 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 2019 CU includes all fixes from October 2019 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 2019 CU should be available at the following locations in a couple of hours:
- KB 4484118 – SharePoint Foundation 2013 October 2019 CU
- KB 4484121 – SharePoint Server 2013 October 2019 CU
- KB 4484120 – Project Server 2013 October 2019 CU
- There was no fix released for Office Web Apps Server 2013 this month
The Full Server Packages for October 2019 CU are available through the following links:
- Download SharePoint Foundation 2013 October 2019 CU
- Download SharePoint Server 2013 October 2019 CU
- Download Project Server 2013 October 2019 CU
- There was no fix released for Office Web Apps Server 2013 this month
After installing the fixes you need to run the SharePoint 2013 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.
Be aware that the SharePoint Server 2013 CU contains the SharePoint Foundation 2013 CU. And the Project Server 2013 CU also contains the SharePoint Server 2013 CU and SharePoint Foundation 2013 CU.
Related Info:
- Technet: Updated Product Servicing Policy for SharePoint 2013
- Blog: Common Question: What is the difference between a PU, a CU and a COD?
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Blog: Support for SharePoint 2013 RTM has ended
- Blog: SP1 for SharePoint 2013
- Technet: CHANGE: SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging
- Technet: Install a software update for SharePoint 2013
- Blog: How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SQL Server 2014 and SharePoint Server 2013
Permalink
Hi Stefan , After installing CU of September 2019 , PowerShell app is crashing .
I am uploading the masterpage to all site collection and it updating for few sitecollection and then powershell.exe getting crashed . No error in the script or logs .
Permalink
Hi Rahul,
please open a ticket with Microsoft support to get this analyzed.
Cheers,
Stefan
Permalink
Hi Stefan, after instaling CU of October 2019, in the calendar group view not function left hiperlink to individually caledars 🙁
Permalink
Hi Vit,
if you need assistance here you should open a support case with Microsoft.
Cheers,
Stefan
Permalink
Hi Stefan,
SharePoint October 2019 CU installed successfully in SharePoint 2013 servers, but when I try to run PS Config command, we are getting error “failed to upgrade at Microsoft.SharePoint.Upgrade.SPDatabaseSequence.Upgrade().”
As per the ULS logs,
Issue is related with Search service application database upgrade.
“Upgrade [SearchAdminDatabase Name=Search_Service_Application_DB_481323e51…] failed.”
Please let us know if you have any feedback.
Thank you,
Hemant
Permalink
Exception information from ULS
Upgrade [SearchAdminDatabase Name=Search_Service_Application_DB_481323e51…] failed.
Exception: Target string size is too small to represent the XML instance
Permalink
Hi Hemant,
if you need assistance here I would suggest to open a ticket with Microsoft Support.
Cheers,
Stefan