Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


This article describes the issues that are fixed in the Microsoft SharePoint Server 2013 hotfix package that is dated September 9, 2014.


Issues that this hotfix package fixes

  • Assume that you have a SharePoint 2013 page that contains a multi-value lookup field that requires a value. You check out the page and edit it, and the lookup field contains a value. In this situation, you might be unable to check in the page without saving it first. Additionally, you might receive an error message that resembles the following:

    You must fill out required properties before completing this action.

  • The Search Service Application cannot detect the correct proxy setting so that the OpenSearch result source is not available when you search in a SharePoint 2013 site.

  • Assume that you author a page in a host-named site collection. You create a page and begin to create new target labels. In this situation, you might be unable to see the variations of the pages for the selected languages. Additionally, the SharePoint administrator might see an error message that resembles the following in the ULS logs:

    Variation Page Creation
    SharePoint failed to sync source page with one or more of its target page variations because the source page could not be found.

  • The title of the result page is incorrect when you search a term on a SharePoint search center site.

  • The search result summary might be lost when the search result contains paths that have long Japanese characters.

  • Assume that you create a new document on a SharePoint page on a SharePoint 2013 publishing site. You cannot view or edit the properties of the document without checking in the document. Additionally, when you click View Properties or Edit Properties, an error page might appear.

  • Assume that you have a SharePoint 2010 server farm that uses a Remote SharePoint Index on a SharePoint 2013 server farm. When you perform a search in a SharePoint Server 2013 search center, no result is returned.

  • Assume that you create a search scope that uses a content type on a SharePoint 2010 site, and the content type name contains a space. After you upgrade the site from SharePoint 2010 to SharePoint 2013, the search scope does not work.

  • Assume that you create a search scope that uses a managed property in a SharePoint 2010 site. After you upgrade the site from SharePoint 2010 to SharePoint 2013, the search scope does not work.

  • The query results are not cached on a SharePoint 2013 server.

  • When you start a three-state workflow from a retention policy action, the workflow may fail.

  • After you install the April 2014 cumulative update, when you search for a user in the Search Center, the hyperlinks in the search result does not work.

  • Assume that you browse to a SharePoint site from a computer that is running Chinese version of Windows 8 (or later versions of Windows), and then you perform a search. The search results may not be accurate because the query that is issued does not use correct culture information that should be Chinese.

  • Assume that you create a SharePoint enterprise search center site. Some options on the Search Settings page may not work.

  • Consider the following scenario:

    • You create a SharePoint document library on a SharePoint 2013 site.

    • You grant Contribute permission to a user to the document library.

    • The user does not have the permission to visit the SharePoint site.

    In this scenario, the user is able to follow the SharePoint site and receive the newsfeed of the site. This behavior is unexpected.

  • When you retrieve static images from a SharePoint 2013 site where the BLOB cache is enabled, the site may become unresponsive.

More Information

Hotfix information

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

Restart requirement

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.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

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.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!