Hotfix KB2910925 for SharePoint Server 2013 December 9, 2014 (Coreserver-x-none.msp; Coreservermui-<Language-Code>.msp)

• Consider the following scenario:
  • You set up a User Profile service application, a Search service application, and an App Management service application on a SharePoint 2013-based server.
  • You configure alternate access mappings and forms-based authentication for the server.
  • You browse to a SharePoint site that is hosted on the server, and then you search for a user.
  In this scenario, when you click the user name that appears in the search result, you may receive an error message.
  
• This hotfix improves crawl performance for SharePoint 2013 when deadlocks occur in the link databases.
  
• This hotfix improves the accuracy of the Most Popular Items report by counting the usage event statistics for all documents in a SharePoint 2013 library.
  
• This hotfix improves the @Mention feature on My Site pages by displaying the login when you move the pointer over a display name. This improvement helps you distinguish different users who share the same display name.
  
• Assume that you configure a SharePoint 2010 farm to consume a Search service application of a SharePoint 2013 farm. Then you configure alternate access mappings for the SharePoint 2010 farm. In this situation, when you search for content in the SharePoint 2010 search center, the URLs that appear in the search result are incorrect.
  
• Consider the following scenario:
  • You enable the ratings for a SharePoint 2013 list.
  • You add a user whose user name contains an apostrophe (') character.
  • The user browses to the list, and rates an item in the list.
  In this scenario, when the user updates the page, the rating disappears. Additionally, the user receive the following error message: 
  var ratedBy = '20;#<User Name>'
• In some cases the "Did you mean" spelling correction feature does not work on a multi-node SharePoint 2013 search farm.
  
• In multi-node SharePoint 2013 search farm setup, the restart of the primary indexer node (for example for maintenance or applying updates) may cause a restart of the secondary node which results in a query outage during the restart of the primary node. This fix makes sure that the restart of the primary node does not lead to a restart of the secondary node. Therefore, the search service will still be available.
  
• Assume that you sign in a SharePoint 2013 site by using Security Assertion Markup Language (SAML)-based claims authentication. When you search for content in the site, no result is returned.
  
• When you use enterprise search in a SharePoint 2013-based server, the Best Bets feature may not work.
  

Back to the top | Give Feedback

Registry Information

Prerequisites

Restart requirement

Hotfix replacement information

File information

Collapse this imageExpand this image