July 2015 CU for SharePoint 2013 is available for download

37 Comments

1. 

   Piotr Siódmak
   On 15. July 2015 Permalink

   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?

   Reply
2. 

   Stefan Goßner
   On 15. July 2015 Permalink

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

   Reply
3. 

   Anonymous
   On 15. July 2015 Permalink

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

   Reply
4. 

   Philippe
   On 15. July 2015 Permalink

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

   Reply
5. 

   Stefan Goßner
   On 15. July 2015 Permalink

   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

   Reply
6. 

   Stefan
   On 15. July 2015 Permalink

   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)

   Reply
7. 

   Anonymous
   On 15. July 2015 Permalink

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

   Reply
8. 

   Anonymous
   On 16. July 2015 Permalink

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

   Reply
9. 

   J Rohde
   On 29. July 2015 Permalink

   Hi Stefan

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

   Regards
   Jakob

   Reply
10. 

    Stefan Goßner
    On 29. July 2015 Permalink

    Hi Jakob,
    yes it does.
    See here for details:
    http://blogs.technet.com/b/stefan_gossner/archive/2013/03/21/common-question-what-is-the-difference-between-a-pu-a-cu-and-a-cod.aspx
    Cheers,
    Stefan

    Reply
11. 

    Stefan Goßner
    On 7. August 2015 Permalink

    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

    Reply
12. 

    Clayton
    On 7. August 2015 Permalink

    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!

    Reply
13. 

    Stefan Goßner
    On 7. August 2015 Permalink

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

    Reply
14. 

    Marina
    On 9. August 2015 Permalink

    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

    Reply
15. 

    Stefan Goßner
    On 9. August 2015 Permalink

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

    Reply
16. 

    Marina
    On 9. August 2015 Permalink

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

    Reply
17. 

    Stefan Goßner
    On 10. August 2015 Permalink

    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

    Reply
18. 

    Frank
    On 10. August 2015 Permalink

    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

    Reply
19. 

    Manjiri
    On 10. August 2015 Permalink

    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 ?

    Reply
20. 

    Marina
    On 11. August 2015 Permalink

    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

    Reply
21. 

    Manjiri
    On 11. August 2015 Permalink

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

    Reply
22. 

    Manjiri
    On 11. August 2015 Permalink

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

    Reply
23. 

    Manjiri
    On 11. August 2015 Permalink

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

    Reply
24. 

    Manjiri
    On 11. August 2015 Permalink

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

    Reply
25. 

    Manjiri
    On 11. August 2015 Permalink

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

    Reply
26. 

    Manjiri
    On 11. August 2015 Permalink

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

    Reply
27. 

    Marina
    On 12. August 2015 Permalink

    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

    Reply
28. 

    Frank
    On 12. August 2015 Permalink

    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

    Reply
29. 

    Clayton
    On 13. August 2015 Permalink

    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!

    Reply
30. 

    Marina
    On 18. August 2015 Permalink

    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

    Reply
31. 

    Marina
    On 24. August 2015 Permalink

    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

    Reply
32. 

    Stefan Goßner
    On 24. August 2015 Permalink

    Hi Marina,
    thats what I mentioned here:
    http://blogs.technet.com/b/stefan_gossner/archive/2015/08/20/why-i-prefer-psconfigui-exe-over-psconfig-exe.aspx
    Cheers,
    Stefan

    Reply
33. 

    Sushanta
    On 20. September 2015 Permalink

    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.

    Reply
34. 

    Stefan Goßner
    On 20. September 2015 Permalink

    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

    Reply
35. 

    Ben Stegink
    On 10. November 2015 Permalink

    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.

    Reply
36. 

    Sondre
    On 4. February 2021 Permalink

    The download link for this CU is no longer working. I am trying to update a farm to newest cus, but if fails. During some research i found that “All updates after July 2015 CU REQUIRE the July 2015 CU to be installed first”. Is it possible to get this CU from somewhere else..?

    Reply
    1. 

       Stefan Goßner
       On 4. February 2021 Permalink

       Hi Sondre,
       not sure where you got this but thats not true.
       You can install the current CU on SP1.
       Cheers,
       Stefan

       Reply