Description of the SharePoint Server 2013 hotfix package (Coreserver-x-none.msp): October 8, 2013

Issues that this hotfix package fixes

• When you are a search service administrator in a SharePoint Server 2013 farm, you cannot click Query Rules under the Queries and Results heading in the navigation pane to see query rules.
  

• When you follow a document on a SharePoint Server 2013 site that has alternate access mappings (AAM) enabled, the link to the document points to the default zone instead of to the AAM zone.
  

• When you use SharePoint Designer 2013 to add a Dataform web part to a SharePoint Server 2013 page and enable grouping on one or more fields, you cannot expand or collapse the group.
  

• When you trigger an automatic approval workflow on a SharePoint Server 2013 site from a nondefault zone, the approval email message includes a URL that uses the default zone.
  

• When you add a note board web part to a web part zone on a SharePoint Server 2013 site, web part zones on the right side of the page are unexpectedly moved down the page.
  

• When you post a link for a file that contains more than 16 Unicode Transformation Format (UTF) characters on the Newsfeed page, you receive the following error message:

  This couldn't be posted because we're having some issues at the moment.

• Assume that you add the Tag Cloud web part to a page on a SharePoint Server 2013 site that has the Save metadata on this list as social tags feature enabled. When you try to add a term in the Enterprise Keywords column for an item, the term is not added, and no tag is displayed on the Tag Cloud web part.
  

• Consider the following scenario:

  • You create a SharePoint Server 2013 document library that has the versioning and "required check out" features enabled.

  • You upload a document to the document library.

  • You check in the document and leave a version comment.

  • You open the version history of the document.

  In this situation, the version comment is blank.
  

• You cannot use the asset picker to add an image to a page on a Catalonian SharePoint Server 2013 site.
  

• Consider the following scenario:

  • You create a Team Site web application and a My Site web application that use different host names.

  • You follow up a post on a Team Site.

  • You click the link in the Added a follow up task to your task list dialog box to view your task.

  In this situation, you are not redirected to the My Site site.
  

• When you perform a crawl on a SharePoint Server 2013 site, and the site performs a redirect operation to a different page, you receive an error message that states that an object was not found.
  

• Assume that you enable the Company Entity Extraction or Custom Extraction feature on a SharePoint Server 2013 site. When you perform a crawl on a list that contains some attachments, the crawl freezes and then times out.
  

• When a site (site A) and your My Site site are hosted on different farms, you cannot follow people or content on the Newsfeed page on site A.
  

• Consider the following scenario:

  • You create a source label and a target variation label on a SharePoint Server 2013 site.

  • You run the Variations Create Hierarchies Job Definition job to enable hierarchies.

  • You create a list under a sub-site that is under the source variation.

  • You run the Variations Propagate Sites and Lists Timer job to enable propagation.

  • You click a hyperlink in the status column on the variation settings page for the list.

  In this situation, you receive an error message that states the list does not exist.
  

• When you search some words by using the Enterprise Search Center site on a SharePoint Server 2013 server on which a custom word breaker is installed, no words are highlighted.
  

• 2826001 "We’ve hit a snag" error message when a user clicks the Followed Sites or Followed Documents button in a consuming SharePoint Server 2013 farm

• When you change the search topology and remove the replicas on a SharePoint Server 2013 server, the disk is accumulated and is eventually filled up.
  

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:

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.