The product group released the April 2016 Cumulative Update for the SharePoint 2013 product family.
For April 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, April 2016 CU includes all fixes from April 2016 PU.
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 April 2016 CU should be available at the following locations in a couple of hours:
- KB 3114935 – SharePoint Foundation 2013 April 2016 CU
- KB 3114938 – SharePoint Server 2013 April 2016 CU
- KB 3114936 – SharePoint Server 2013 with Project Server April 2016 CU
- KB 3114934 – Office Web Apps Server 2013 April 2016 CU – This is also a security fix!
The Full Server Packages for April 2016 CU are available through the following links:
- Download SharePoint Foundation 2013 April 2016 CU
- Download SharePoint Server 2013 April 2016 CU
- Download Project Server 2013 April 2016 CU
- Download Office Web Apps Server 2013 April 2016 CU
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 April 2016 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.
- 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
- Blog: April 2016 Office Update Release
- 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
I noticed there was a fix in there for “When you try to create a SharePoint group that has a specially formatted name, the IIS worker process may restart.” Is there any posts out there or documentation regarding this bug? It would be nice to know how to not trigger this problem until we are able to test/apply the CU.
This can (e.g.) happen if you are trying to add a site group named “abc?%” (the last two characters are important).
I posted this in yammer and Dean Gross told me to ask you 😉
I want to try a new approach i found below a blog post.
I already tried it out in a VM Sandbox (and it worked) but i’m not sure if this is supported by Microsoft.
I install the patch with the powershell script provided by here:
But then i do not execute the Configuration Wizard. First i upgrade my content database by executing this powershell line:
“Get-SPContentDatabase | Upgrade-SPContentDatabase -UseSnapshot -Confirm:$false”
(I read somewhere that this only works with SQL Enterprise Server)
Big advantage here is. The sql server performes a snapshot for the database and if someone tries to access a site that is in a content db upgraded right now he/she will see this information (see picture)
After upgrading this content db the user can proceed working.
After this powershell command is finished i execute the wizard and it upgrades the remaining DBs. As i did not find another blog post about this great feature i’m wondering what’s wrong with that 🙂
Is there something?
this approach is perfectly fine – there is nothing wrong with it. It’s used by various different IT departments to reduce the downtime caused by SharePoint patching. You can also run multiple Powershell sessions to upgrade several content databases in parallel if you like.
And you are right: you need SQL enterprise editon to make use of the snapshot functionality.
Does it include the fix for the Follow functionality to work in a multi farm environment ?
Yes it includes this fix.
Attempting to patch SharePoint 2013/Project Server 2013 DEV 2 server farm to April 2016 CU
1 server installs successfully with no issues
1 server generates error “An error occurred while running detection”
Attempted to bypass check using packagename PACKAGE.BYPASS.DETECTION.CHECK=1
On unsuccessful server received error “The installation of this package failed”
Also attempted to stop search service using powershell script but package still fails
Both servers Windows 2008 R2
Currently @ SharePoint 15.0.4571.1502 & SP 1
Project Server 15.04649.1001
never(!) use PACKAGE.BYPASS.DETECTION.CHECK=1 without being guided by Microsoft Support.
If you manage to force a patch on a system where the fix misses prerequisites using this option you would need to reinstall the box afterwards.
The symptoms are not sufficient to diagnose the problem.
If you need assistance with with the installation of a CU you should open a support ticket with Microsoft.
After upgrading to April 2016 CU Open with Explorer is not working , We are having problem in opening from this location in explorer & Add this site to trusted sites, This is already there in trusted site list but still not working, Any idea?
Is anyone else having issues disabling alerts after installing the April 16 CU? I can no longer disable alerts at the web app level via the Central Admin, stsadm or powershell. The settings update fine when I check, but list alerts continue to trigger. thanks.
Do you know if SQL Server 2014 SP1 CU 7 is supported with this April 2016 CU for SharePoint 2013 ?
Thanks in advance
After installing the April, 2016 CU, receive the following error message on all newsfeed web parts: “SharePoint site feed web part failed to render “Wiki content” column because of an error in the “Multiple lines of text” field type control. Object reference not set to an instance of an object. Web part causes page not to open. Any thoughts on a repair?
I just double checked and this is not a known issue.
I would recommend to open a support ticket with Microsoft to get this analyzed.
Did you solve it ?
In one of our SharePoint server 2013 farm we have installed this update however post installing the same, we can’t fetch any usage report or search report.
We have already checked and confirmed everything is configured properly with respect to analytic.
We have even confirmed that enable receiver value is true and receiver has required value.
What should we do? Please suggest.
please verify if the issue still occurs with the latest CU (currently August 2016 CU) to ensure that this is not an issue which has already been addressed. If the issue still occurs with the latest CU I would recommend to open a support ticket with Microsoft to get this analyzed.