The product group released the June 2015 Cumulative Update for the SharePoint 2013 product family.
For June 2015 CU we have full server packages (also known as Uber packages). No other CU is required to fully patch SharePoint.
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 security fixes) released since SP1. The CU does not include SP1. You need to install SP1 before installing this CU.
The KB articles for June CU are available at the following locations:
- KB 3054864 – SharePoint Foundation 2013 June 2015 CU
- KB 3054866 – SharePoint Server 2013 June 2015 CU
- KB 3054865 – SharePoint Server 2013 with Project Server June 2015 CU
- KB 3054863 – Office Web Apps Server 2013 June 2015 CU
The Full Server Packages for June 2015 CU are available through the following links:
- Download SharePoint Foundation 2013 June 2015 CU
- Download SharePoint Server 2013 June 2015 CU
- Download Project Server 2013 June 2015 CU
- Download Office Web Apps Server 2013 June 2015 CU
After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.
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:
- Common Question: What is the difference between a PU, a CU and a COD?
- SharePoint Patching demystified
- Support for SharePoint 2013 RTM has ended
- SP1 for SharePoint 2013
- June 2015 Office Update Release
- CHANGE: SharePoint 2013 Rollup Update for the December 2013 Cumulative Update Packaging
- How to: install update packages on a SharePoint 2013 farm where search component and high availability search topologies are enabled
- Update Center for Microsoft Office, Office Servers, and Related Products
- SQL Server 2014 and SharePoint Server 2013
Permalink
Ya tenemos disponibles las actualizaciones acumuladas para SharePoint 2010 y SharePoint 2013 de junio
Permalink
Hello Stefan,
for the May Update a User discovered the following bug:
"After have I Installed the May 2015 CU for SharePoint 2013 I have found a bug inside the search refinements. which is based on the language setting for Germany.
The refinement uses the wrong delimiter (German) namely: "," instead of a "." makes a error inside the search:
Miete:range(decimal(150,00), decimal(00600,)) —> Microsoft.Ceres.InteractionEngine.Processing.BuiltIn.InvalidRefinementException: Unable to parse refinement for input: Miete:range(decimal(150,00), decimal(600,00)) —> Microsoft.Ceres.InteractionEngine.Processing.BuiltIn.Parsing.ParseException:
Query 'Miete:range(decimal(150,00), decimal(600,00))' failed: syntax error
at position 23, unexpected COMMA, expecting RPAR"
Do you know if this got resolved in this June Update? I hesitate to install May and/or June Update as Long as Search has such a Problem.
Permalink
Hi,
I have the same error for Poland language and I have may CU for Sharepoint 2013.
Permalink
Hi Krzysztof,
then please also run the script and provide the output.
Thanks,
Stefan
Permalink
Hi Andy,
I haven’t heard about such an issue and I’m not sure if this has even been reported to us by a customer.
Even if it would have been reported it is unlikely that a fix could be in June CU as it usually takes several months to fix and test a solution.
Ensure to open a support case with Microsoft as without a support case to report an issue no fixes will be created.
Cheers,
Stefan
Permalink
Hola, buenas, Después de que haya llegado el segundo martes del mes, ya podemos descargarnos la Actualización
Permalink
Hello Stefan,
I read through your article 'SharePoint patching demystified' . The uber package seems like the best approach. I have SharePoint 2013 ent with project server. Above in you June 2015 CU release for 2013 you have a link to '•KB 3054865 – SharePoint Server 2013
with Project Server June 2015 CU' and a link for 'Full server packages' . Which one is the uber? Is there an uber that contains foundation, server and project server? To confirm, do you need to install foundation separately if you install the server cu or
server with project server cu?
Thanks for your help
-Bob
Permalink
Hi Bob,
Uber package and full server packages are synonyms.
The project server package above includes SharePoint Foundation and SharePoint Server CU.
Cheers,
Stefan
Permalink
Hello Stephan,
I tried to install the CU but I have the message "he expected version of the product was not found on the system " even if I have MS Project 15.0.4569.1506 and SharePoint 2013 15.0.4569.1000 that indicate the SP 1 is install….
Do you have any Ideas ?
Thanks !
Daniel
Permalink
Hi Stefan,
same here, installed a fresh new SharePoint with March 2015 PU. When I wanted to install the June CU, I received the same Message as Daniel above:
"The expected version of the product was not found on the system"
Ist there something we can do? maybe install the May CU?
Gruss,
Robert
Permalink
Hi Robert, Hi Daniel,
please run this script and verify if there are any components below SP1 baseline:
http://blogs.technet.com/b/stefan_gossner/archive/2015/04/20/powershell-script-to-display-version-info-for-sharepoint-product-and-language-packs.aspx
Cheers,
Stefan
Permalink
Hi Stefan,
thaks for the Skript, indeed, the Build numbers are totaly mismatching and I beleve the LPs are below SP1:
DisplayName : Microsoft SharePoint Server 2013
DisplayVersion : 15.0.4569.1506
DisplayName : Language Pack for SharePoint and Project Server 2013 –
German/Deutsch
DisplayVersion : 15.0.4420.1017
DisplayName : Language Pack for SharePoint and Project Server 2013 –
French/Français
DisplayVersion : 15.0.4420.1017
It seems the Downloads were wrong. Im installing now the SP1 for LPs
Thanks,
Robert
Permalink
Hi Stefan,
The script told me that my Language Pack was not at SP1. So I installed the SP1 and run the script again to confirm that the version was now OK. But now, I have another error message : "The installation of this package failed"
Any other suggestions ?
Thanks,
Daniel
Permalink
Hi Daniel,
this is a very generic error. I would suggest to enable MSI logging – or to open a support case with Microsoft in case you need assistance to identify the root cause.
Cheers,
Stefan
Permalink
I am unable to install the June 2015 CU, as per your suggestion i have keep all the file in same folder, still I am getting the error as "Installation of package failed", Please suggest.
Permalink
Hi Ashish,
this is a generic error. I would recommend to enable MSI logging.
If you cannot resolve it yourself, I would suggest to open a support case with Microsoft.
Cheers,
Stefan
Permalink
Hello Stefan,
I have re-download the CU Binary and now i am able to install it.
Thanks for your response.
Permalink
Hello Stefan,
I am not able to find an answer from Microsoft if Workflow Manager is now supporting SQL Server 2014. Could you maybe get an answer from your collegues at Microsoft if Workflow Manager is supporting SQL Server 2014 with any Kind of CU for Workflow Manager?
I did find an answer that Workflow Manager now supports Windows Server 2012 R2, though. But nothing for SQL Server 2014.
Kind regards,
Andy
Permalink
I’m presenting a summarized "Build Numbers Cube Sheet" as I did so before, so please find
Permalink
@Andy,
I can confirm that Workflow Manager works with SQL 2014. I have done a couple of deployments with SQL 2014.
Permalink
I’m presenting a summarized "Build Numbers Cube Sheet" as I did so before, so please find
Permalink
Hi Stefan,
I'm facing an issue that seems quite unique in that I can't see anyone else complaining about in the forums. I think it is related to applying the June 2015 CU on a SP1 build. I have several custom search result sources that use 'QueryString' in the query text.
Using SP1, the Query Builder loads up fine with such construct, but after applying the June 2015 CU, the Query Builder loads with error "An unknown error occurred." and the ULS suggests that it has something to do with non existent query strings in the URL
that is used to load the QueryBuilder.aspx page.
Here's the corresponding ULS log entry:
==================================================================================
Stacktrace:
==================================================================================
Exception in Query Builder OnLoad: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SharePoint.Publishing.SearchTokenExpansion.GetQueryStringProperty(String[] matchSegments, String originalPath)
at Microsoft.SharePoint.Publishing.SearchTokenExpansion.GetTokenValue(String token, SearchTokenExpansionContext context)
at Microsoft.SharePoint.Publishing.SearchTokenExpansion.GetTokenValues(IEnumerable`1 tokens, SearchTokenExpansionContext context)
at Microsoft.Office.Server.Search.Internal.UI.QueryBuilder.PopulateSearchSourceDropDown()
at Microsoft.Office.Server.Search.Internal.UI.QueryBuilder.OnLoad(EventArgs e)
==================================================================================
When using a Content Search Web Part from within a custom page on another site collection, the Query Builder loads without errors. Now, I noticed that the URL passed to the QueryBuilder.aspx page is different when loaded from the Central Admin versus a normal
site collection & when I try to simulate loading the page like the central admin by appending the 'RawUrl' query string argument, the page does not throw the exception.
Here are the steps I followed as part of the upgrade to June 2015 CU:
* Installed June 2015 CU
* Ran Configuration Wizard from within Central Admin
* Executed "psconfig -cmd upgrade -inplace b2b -wait"
* Reset search index
Are you able to please highlight if I'm missing a step or doing something wrong? Any help is greatly appreciated.
Thanks,
Raj
Permalink
Hi Raj,
did you resolve the problem?
thanks
Permalink
Hi Raj,
as always if you run into a problem with a CU: please open a support case with Microsoft to get this analyzed.
Thanks,
Stefan
Permalink
Hello Stefan,
we had installed SharePoint SP1 from MSDN with the pre-released (problematic) SP1. Then we updated to SP1 rereleased and updated to CU September 2014 with no problems.
Now we tried installing CU May 2015 and we get the error message "The expected version of the product was not found on the system."
The SP1 Version is the KB2880552 and the current build version of the Farm is "15.0.4649.1000"
Any help is appreciated!
Permalink
Hi Ioannis,
15.0.4649.1000 is a patch level – not a patch baseline.
Please run the script on the page below and check if there are any components with a patch baseline below 15.0.4569.1506:
http://blogs.technet.com/b/stefan_gossner/archive/2015/04/20/powershell-script-to-display-version-info-for-sharepoint-product-and-language-packs.aspx
Cheers,
Stefan