Stefan Goßner

Senior Escalation Engineer for SharePoint Products and Technologies

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

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

  • Comments 16
  • Likes

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:


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

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

  • Hi Stephen, please check the KB.
    It's a Foundation fix.

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

  • Hi,

    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.

  • 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.


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

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

  • Hi Mike,

    there is a Standard and an Enterprise Edition:


  • 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 properties)

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

  • 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 :

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Raw Html Fix