This article describes the issues that are fixed in the Microsoft SharePoint Server 2013 hotfix package that is dated June 10, 2014.
Issues that this hotfix package fixes
When you search a PDF file in a SharePoint 2013 site, the title of the PDF file may contain garbage characters when the PDF file is displayed in the search result.
Local custom properties for the term or termset may be lost when you make changes in the other tabs on the Term Store Management Tool page.
Assume that you enable the Allow multiple values option for the keywords managed property on a SharePoint 2013 site. Documents that have more than one crawled property mapped to keywords in this configuration cause a failure in the crawler flow, and are indexed incorrectly.
You cannot find the security groups that use a double-byte character set (DBCS) name in the audience picker.
You can select the “SpTermsIdx” full-text index when you create a new managed property. As a result, when you crawl the site, the indexer may fail and display an error message.
When the metadata service application uses the Windows Communication Foundation (WCF) web service in a SharePoint Server 2013 farm, the following event is logged in the Application log:
Newsfeed repopulation fails when a user's latest post is a ColleagueFollowing post. Therefore, no posts appear on the Newsfeed page even after you click "Show More Posts".
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
You must install the following public update before you apply this hotfix package:
2767999 Description of the SharePoint Server 2013 update: March 12, 2013
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to resolve the issues that are listed in this article.
The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.