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 December 10, 2013. Additionally, this hotfix introduces new searchPowerShell cmdlets to manipulate (Create, Read, Update and Delete) SharePoint Search Result Source.


Issues that this hotfix package fixes

  • When you edit a post on a discussion board on a SharePoint Server 2013 site that is created by an anonymous user, the page is not displayed, and a script error occurs.

  • When more than one front-end server is set up to process incoming email messages on a SharePoint Server 2013 server farm, only one of the servers can process email messages, and cannot fail over to any other server.

  • When you try to add a Web Part to a SharePoint Server 2013 community portal site, the Web Part picker is not displayed.

  • When you create a list workflow in which the platform type is "SharePoint 2013 workflow" in SharePoint Designer 2013, the workflow may set an incorrect user name in some list item fields.

  • Consider the following scenario:

    • You publish a content type from the content type hub.

    • You move some fields to change their order on a list that uses the content type. The fields are used in the published content type.

    • You republish the content type from the hub.

    In this situation, the customized column order for the list is reverted.

  • When you create an alert for a post on a discussion board on a SharePoint Server 2013 site, you receive the following server error message:

    ArgumentException: Value does not fall within the expected range.

  • The presence icon appears incorrectly in the Contact Details Web Part on a SharePoint Server 2013 site.

  • When you execute a query that contains FAST Query Language (FQL) language, you cannot highlight the result.

  • When you add more than one Content Query Web Part to a wiki page on a SharePoint Server 2013 site, the added Content Query Web Part is not displayed on the wiki page.

  • On SharePoint Server 2013, when a survey page is in edit mode, the ribbon does not display.

  • Rating fields such as Likes and Star Ratings are not available for list items that contain the Video content type in an Asset Library.

  • When you perform a crawl on a site in which the URL contains encoded Hebrew characters, percent signs, or encoded question marks, the crawl fails.

  • When you perform an advanced search that contains a quotation mark on a SharePoint Server 2013 site, you receive an error message that states the query contains only one quotation mark.

  • If a SharePoint central administration site is configured to use SSL, a User Profile Synchronization that uses Active Directory Import fails.

  • Consider the following scenario:

    • You set up a SharePoint Server 2013 server farm with Managed Metadata Service.

    • You change the sorting for a term or termset.

    • You change the custom or local custom properties for the term or termset.

    In this situation, the sorting is reverted to the default.

  • When you add a Summary Link Web Part to a page in the source variation site and the change is propagated to a target variation site, the Web Part properties cannot be changed and exported from the target site.

  • After you perform a search on a SharePoint Server 2013 site, the search results are loaded as invalid links. Additionally, when you click the result, you are moved to the home page of the site collection instead of to the actual URL.

  • After you upgrade a server to SharePoint Server 2013, the Table of Contents Web Part that has the Show content from starting option is selected.

  • When you make a topology change in a Search Service Application (SSA) that contains lots of items, topology activation fails even if the index schema compression is enabled.

  • The performance of a Fast Search server for SharePoint 2013 is suboptimal during usual operations, and the memory usage is larger than necessary.

  • When you activate a topology that contains more than 20 index components, a time-out issue occurs.

  • When you use a Noteboard Web Part to post a note that contains line feeds or special characters such as angle brackets (<, >) or quotation marks ("), the note is displayed as encoded HTML in the Newsfeed on a MySite.

  • When you add a tag for a document in a Korean version of a SharePoint Server 2013 document library, the tagged document information is not displayed in tagprofile.aspx.

More Information

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem 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 install 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 package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to resolve the issue that 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?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!