This article describes the issues that are fixed in the Microsoft SharePoint Server 2013 hotfix package that is dated July 8, 2014.
Issues that this hotfix package fixes
When you use a custom search refiner based on file size, you may receive an error message that resembles the following:
Property doesn't exist or is used in a manner inconsistent with schema settings.
You cannot use a third-party filter-based format handler (iFilter interface) to replace the built-in format handler.
Assume that you add a Document Set as a Content Type to a SharePoint library, and you add a column validation to a column in the library. When you add a new Document Set to the library, if the column validation fails, you may be redirected to another error page.
You can save a SharePoint page in which the Publishing HTML field is empty, even if this field is required.
Assume that you create the index components by using the –RootDirectory option. When you try to restore a backup, the operation may fail. Additionally, data loss may occur.
Assume that you modify a setting in the NAVIGATION tab when you configure the term stores in the Term Store Management Tools page. You cannot save the changes in the other tab. Additionally, you receive an error message that resembles the following:
Term store may be unavailable.
Assume that you set up two or more SharePoint sites, and you perform a full crawl on site A. You apply the Deny All policy to a user for site A, and then you perform a full crawl on site A again. Then, the user logs on to another site, and then searches for content that belongs to site A. In this situation, the search results may contain site A content.
When you try to create a search query by using the Query Builder feature, the option to trim duplicates is not available.
When you switch the Taxonomy Term Store language and then you modify the default label value, the Custom Sort of terms may revert to the default.
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.