July 2015 CU for SharePoint 2013 is available for download


The product group released the July 2015 Cumulative Update for the SharePoint 2013 product family.

For July 2015 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, July 2015 CU includes all fixes from July 2015 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 July CU are available at the following locations:

  • KB 3054931 – SharePoint Foundation 2013 July 2015 CU
  • KB 3054937 – SharePoint Server 2013 July 2015 CU
  • KB 3054933 – SharePoint Server 2013 with Project Server July 2015 CU
  • KB 3054930 – Office Web Apps Server 2013 July 2015 CU

The Full Server Packages for July 2015 CU are available through the following links:

After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.
Important: unlike other CUs: if you don't run PSCONFIG after installing the July 2015 CU fixes crawl might no longer work – so ensure to schedule a maintenance window when installing this CU which includes PSCONFIG runs.

See here for detail: http://blogs.technet.com/b/stefan_gossner/archive/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013.aspx

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 (31)

  1. Piotr Siódmak says:

    Hi Stefan,
    the article https://support.microsoft.com/en-us/kb/3054926 states that the Crawl will no longer work after installing the hotfix, untill you run psconfig. Doesn't that go against the premise that
    we can install updates and safely postpone psconfig for later?

  2. Hi Piotr,
    yes – you are right.
    Cheers,
    Stefan

  3. Anonymous says:

    Ya tenemos disponibles para descarga las actualizaciones acumuladas de julio de 2015 para SharePoint

  4. Philippe says:

    The link to KB3054937 is broken … This KB seems to be unavailable too (from Google or bing 😉

  5. Hi Philippe,
    just tested: works for me.
    Might be a replication problem. The KB servers are replicated to different locations on the planet and the one you are connecting to might not have received the update. Should be avail in a couple of hours.
    Cheers,
    Stefan

  6. Stefan says:

    Works only on english browser. Replace the Country code in the URL with en-us (f.e.
    https://support.microsoft.com/en-us/kb/3054931 and it workd)

  7. Anonymous says:

    I’m presenting a summarized "Build Numbers Cube Sheet" as I did so before, so please find

  8. Anonymous says:

    Hola, buenas, Ya podemos descargarnos la Actualización Pública para Project 2013 y Project Server 2013

  9. J Rohde says:

    Hi Stefan

    Does the SP Server 2013 CU also contain updates to language packs?

    Regards
    Jakob

  10. Hi Marcel,

    you can install the CU on multiple servers in parallel – but that means that your farm might be down while installing the CU.
    If you install it one-by-one on each server the other servers can still serve requests.

    With PSConfig you need to run PSConfig on just one server (the app server hosting the central admin is recommended) first to do the database schema upgrade.
    Afterwards you can run it in parallel on other servers.

    Again: that means your farm might be down while running PSConfig as the server where PSConfig is running will restart services.

    Cheers,
    Stefan

  11. Hi Stefan,

    I have a farm installed from the MSDN image with SP1. Can I apply this patch directly to the farm, or do I need to reinstall SP1 as a standalone service pack before proceeding? I recall an issue with using the official SP1 slipstream image a couple patches
    ago.

    Thanks!

  12. Hi Clayton,
    July CU should install fine on the SP1 slipstream install.
    No need to reinstall it.
    Cheers,
    Stefan

  13. Marina says:

    Hi Stefan,

    We have a farm installed from the MSDN image with SP1. After installing CU July 2015 we found that we couldn't execute search from the results page.

    Steps to reproduce:
    – search for a file on a home page.
    – When results are presented, retype your query. "Field or property TimeZoneID doesnt exist" error is shown.

    To fix the problem I executed the following in our Dev farm:
    1. SharePoint with integrated SP1 – 15.0.4569.1509 is installed
    2. Farm is created
    3. Tested Search – search is working as expected
    4. Installed CU July 2015
    5. Tested Search to confirm there is a problem – The search is broken when executed from the result page
    6. Installed re-released SP1 (15.0.4571.1502)
    7. Installed CU July 2015
    8. Tested Search – search is working as expected

    Wondering if anyone else had this problem.

    I am a bit nervious to apply the fix in prod to be honest but don't see any other way.

    Regards, Marina

  14. Hi Marina,
    did you run psconfig after installing the CU?
    Cheers,
    Stefan

  15. Marina says:

    Yes, I did. Crawl was working fine after the upgrade.

  16. Hi Marina,
    I haven’t heard about such an issue.
    If you need that issue investigated I would recommend to open a support case with Microsoft Support.
    Cheers,
    Stefan

  17. Frank says:

    Hi Marina,
    we had the same problem with the TimeZoneID property. The root cause was that the Microsoft.Office.Server.Search.ServerProxy.dll was not updated correctly. It has the wrong/old version after installing the CU.
    Regard, Frank

  18. Manjiri says:

    Hi Stephen,
    We too experienced exact same issue as Marina( 9Aug 2015) "Field or property "TimeZoneId" does not exist " on out test farm after applying July 2015 CU ,

    I was able to reproduce the same way
    Search for a file
    When results are presented , retype or change the query and this time you get an error "Field or property "TimeZoneId" does not exist "in sp2013 " in search center .

    I am nervous to apply this in Prod as well . Any update ?

  19. Marina says:

    Hi Frank,

    Thank you for the reply. How did you fix it? Would getting the correctl dll be enough? Or I need to go through the process of installing re-released SP1 and then applying CU July 2015? I am always nervious when I need to install "old" on "new".

    Cheers, Marina

  20. Manjiri says:

    Thanks Frank . I had exactly same issue as Marina . Is there any workaround ?

  21. Manjiri says:

    Thanks Frank . I had exactly same issue as Marina . Is there any workaround ?

  22. Marina says:

    We opened an incident report. Microsoft is investigating. They hinted that we may need to install re-released SP1 but haven't confirmed the recommendation in writing. I will post an update when I have a solution.

    Cheers

  23. Frank says:

    Hi,
    we just replaced the Microsoft.Office.Server.Search.ServerProxy.dll by the new one. We took the new file from a SharePoint where the error not occured after Installation of July CU. But it cannot be excluded, that there are more dll files affected which are
    not updated properly. Until now we found no other problems after the Installation of the CU. Found someone else a different approach to solve the problem?
    Cheers, Frank

  24. Hi Frank,

    Thank you for the solution you have provided, it helped me solve this issue. I noticed that the modified date on the web app file was much older than the one in the 15 hive, and 1kb smaller in size. Here's how I resolved:

    1. Renamed "Microsoft.Office.Server.Search.ServerProxy.dll" in /VirtualDirectories/xx/_app_bin/ with "_OLD" appended
    2. Copied "Microsoft.Office.Server.Search.ServerProxy.dll" from ~/15/CONFIG/BIN/
    3. Pasted in /VirtualDirectories/xx/_app_bin/ for each web application
    4. Rebooted WFE

    After this, search works as expected. As always, your mileage may vary but I hope this helps.

    Thanks!

  25. Marina says:

    Microsoft has confirmed that the problem we are having with the TimeZoneID property was indeed introduced by CU July 2015. As of today they haven't offered any solution. The ticket is still opened and their "back end team" is looking into the problem.
    I will post an update when/if there is a solution.

    Cheers,
    Marina

  26. Marina says:

    The solution to the TimeZoneID problem some of us are having is to run configuration wizard from UI, not form the command line. I just tested it and the farm and search look fine. Cheers

  27. Sushanta says:

    Thanks for this article.

    I'm having a doubt on the binaries. There are 3 bianries available to download:
    http://www.microsoft.com/en-us/download/details.aspx?id=48075
    ubersrvprj_1
    ubersrvprj_2
    ubersrvprj2013-kb3054933-fullfile-x64-glb

    So how we should install it.

  28. Hi Sushanta,
    it is explained in the article above:

    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.

    Cheers,
    Stefan

  29. Ben Stegink says:

    I’m experiencing the TimeZoneID error after installing June 2015 CU, debating trying to see if the July 2015 CU actually fixes it…anyone here have any thoughts/advice? Checked dates on Microsoft.Office.Server.Search.ServerProxy.dll and it’s 5/19/2015 which sounds consistent with the June 2015 CU. It’s also the same version of the file that’s in my config/bin folder in the 15 hive.

Skip to main content