August 11, 2015, update for SharePoint Server 2013 (KB3055002)

• This update adds the hybrid crawl feature. For more information, see Cloud hybrid search capability in SharePoint Server 2013 .
  
• Improves the error message that occurs when you try to create a declare record from a document set.
  
• Adds hybrid followed sites feature to SharePoint Server 2013.
  
• Fixes the following issues:
  
  
  • After you enable company extraction on the body managed property, results that are not companies are displayed in the refiner panel of the search results page.
    
  • When you search items from a Microsoft SharePoint Server 2010 farm that consumes search results from a SharePoint Server 2013 search service application, you may receive an unhandled exception if there is an item whose title contains more than 50 characters and an ampersand "&."
    
  • When you use Chinese taxonomy refiners to search items on a SharePoint Server 2013 site, the search appears broken.
    
  • When you set the PreserveID attribute to True for some SharePoint Server 2013 items, duplicate document IDs may be generated. In this case, when you try to open an item, you may be redirected to a search page that contains multiple items instead of browsing to the item directly, or you see an incorrect document opened.
    
  • When you try to use in-place search to search items in a list that contains multiple pages, the search can find items on the current page, but cannot find items on a different page.
    
  • When you use the Other Value text box to filter refiners for a search result, the count is displayed as zero. This issue occurs if you enable the results counter on the File Type refiner that is a multiple value refiner.
    
  • When you check a page that has a web part with a TODAY token in a query, you may see the search contents of the previous day.
    
  • After you add a file without an extension to a document set, shared properties are not inherited from the document set.
    
  • When you click the Go to search results link in a search alert email message for a localized search center, you receive the following error message:
    Page not found.
  • When you parse a Word document, high CPU utilization occurs on the noderunner.exe process.
    

Restart information

Prerequisite