An important fix for SharePoint Foundation 2013 SP1 has just been released

When looking in the last couple of days at the KB article for SP1 for SharePoint Foundation 2013 you might have seen the following comment:

A known issue in SharePoint Foundation 2013 SP1 can affect the functionality of the Search WebPart. We encourage you to limit production installations of SharePoint Foundation 2013 SP1 until a fix is available. SharePoint Server 2013 is not affected by this issue.

Today we have released March 2014 Public Update (PU) for SharePoint Foundation 2013 which fixes this problem.

Be aware that this fix is only necessary for SharePoint Foundation 2013 installations. SharePoint Server 2013 is not affected by the problem.

The KB articles for March 2014 PU for SharePoint Foundation 2013 is available at the following location:

  • KB 2760625 - March 2014 PU for SharePoint Foundation 2013

The installer package for March 2014 PU for SharePoint Foundation 2013 is available through the following links:

KB article 2817439 for SharePoint Foundation 2013 SP1 will be updated shortly to include this information.

Steps to install SharePoint Foundation 2013 SP1 and this fix:

You can install this fix either before or after installing SP1. No specific sequence required.
PSConfig only has to be run once at the very end after after installing the fixes and SP1.


Related Info:


Comments (20)

  1. Anonymous says:

    When looking in the last couple of days at the KB article for SP1 for SharePoint Foundation 2013 you

  2. Stephen White says:

    When I go to download it, it says quite clearly that the update is for "Microsoft SharePoint Enterprise Server 2013", not Foundation….

  3. Michael Buckingham says:

    Thanks. Any known regressions for SharePoint Server 2013 SP1 or Office Web Apps SP1?

  4. Hi Stephen, please check the KB.
    It’s a Foundation fix.

    Hi Michael, I’m not aware of any till now.

  5. Anonymous says:

    SP1 is now available for SharePoint Server 2013, Project Server 2013, Project 2013, and SharePoint Designer

  6. Anonymous says:

    Following my tradition in presenting a summarized "Build Numbers Cube Sheet" as I did so before

  7. Simon says:


    I'm somewhat with Stephen on this one. The KB title reads: "Description of the SharePoint Foundation 2013 update 2760625: March 20, 2014". The download link on that pages leads to "Update for Microsoft SharePoint Enterprise Server 2013 (KB2760625)". Whilst the download package itself is "coreserver2013-kb2760625-fullfile-x64-glb.exe".

    Whilst I'm sure this is indeed an update that applies to Foundation, the title on the resulting download page is misleading at best.

  8. Hi Simon,

    I reported this problem and the text will be changed in the next couple of days to reflect SharePoint Foundation rather than SharePoint Enterprise Server.

    coreserver is part of SharePoint Foundation as well. It contains the search components.


  9. Mike Walsh says:

    Is there actually a SharePoint **Enterprise** Server ?

    Since when? (i.e. whatever happened to SharePoint Portal Server 2013)

  10. Hi Mike,

    there is a Standard and an Enterprise Edition:


  11. Anonymous says:

    With the KB article 2817439 you may saw an important notice regarding the search webpart. Now we have

  12. Anonymous says:

    Desde hace unos días está disponible el hotfix que soluciona los problemas y errores que el Service Pack

  13. Anonymous says:

    Como el primero de cada mes, aquí os dejo un nuevo recopilatorio de enlaces interesantes en torno a SharePoint

  14. Hi Stefan,

    In my enviroment we had extended http defalt site on https (SSL configured) internet site, with no server mapping.
    -Search works as expected on http site but default sharepoint search fail on https sites
    – search work as expected with global search on Search center site

    Search fail on default _layouts/15/OSSSearchResults.aspx

    Note: we have used SiteMinder as trust identity provider in https site

    Object reference not set to an instance of an object. at Microsoft.Office.Server.Search.Administration.UrlMapper.ExtractMapping(Pair`2 properties, SPSite site, IDictionary`2 urlMapping, IDictionary`2 reverseUrlMapping) at Microsoft.Office.Server.Search.Administration.UrlMapper.GetNewCacheEntry(Pair`2

    Server topology:
    2 Index server (Application server)
    2 Query server (Query Server)
    2 WFE

  15. Just like to isolate this issue i have found resolution :

    we have troubleshooted the issue and found orphan site collection which was causing Null reference error;

    Article :

  16. Anonymous says:

    Finalmente siamo tornati online e lo facciamo pubblicando la tabella degli aggiornamenti di SharePoint

  17. Glenn Duzy says:

    Thank you for this. It solved my problem!

  18. Eduardo Cedillo says:

    Very helpful thanks a lot for the Blog

  19. Anonymous says:

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

  20. Anonymous says:

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

Skip to main content