Summary

This article describes the issues that are fixed in the Microsoft SharePoint Server 2013 hotfix package that is dated April 26, 2013.

INTRODUCTION

Issues that this hotfix package fixes

  • Consider the following scenario:

    • You create a multiple value lookup column for a document set in SharePoint Server 2013.

    • You create another document set that shares the same multiple value lookup column.

    • You upload a document to the second document set.

    In this scenario, the column only displays one value of the document.

  • Assume that you attach a file to a discussion in a discussion list on a SharePoint Server 2010 site. After you upgrade the SharePoint Server 2010 site to a SharePoint Server 2013 site, the attachment disappears from the discussion.

  • In the Korean version of the SharePoint site, when you search documents that contain a compound noun, some results are missing.

  • Assume that you create a site collection in SharePoint 2010 mode in SharePoint Server 2013. When you try to change the master page of the site collection, you receive an error message.

  • Assume that multiple users update a navigation node on a site that has many navigation nodes. When you try to view the site, the site cannot be displayed.

  • Assume that you use Microsoft Internet Explorer 8 to open a newsfeed post on a SharePoint site. You notice a typing lag when you type more than two lines of characters in the newsfeed post.

  • Audit reports generate an invalid .xlsx file on a SharePoint 2010 mode site in SharePoint Server 2013.

  • This update enables the differentiation of query specific segmentation for custom word breakers.

  • The eDiscovery feature does not display crawl error messages when the eDiscovery feature fails to crawl content in a SharePoint Server 2013 farm.

  • Consider the following scenario:

    • You use Internet Explorer 8 to view a newsfeed post on a SharePoint webpage.

    • You input a several lines of text in the textbox of the newsfeed post.

    • You select all the content on the webpage.

    In this scenario, some hidden characters on the webpage unexpectedly appear.

  • Assume that you create a SharePoint Server 2010 mode site collection on a SharePoint Server 2013 server. Additionally, assume that the site collection is not considered as part of the local intranet zone in Internet Explorer. When you use the people picker control on the site, you encounter an error.

  • Assume that you add a tag to a document on a SharePoint 2010 mode site. When you view the tag profile, the GUID tag name appears instead of the friendly name of the tag.

  • Assume that you install multiple Search Service Applications (SSA) in SharePoint Server 2013. When you use an SSA to crawl a site, the managed properties are not shown in the SSA that you used to crawl the site with. Instead, the managed properties are shown in another SSA incorrectly.

  • You cannot use the Term Store Management tool to move a term on a site in SharePoint 2010 mode.

  • Consider the following scenario:

    • You create a SharePoint environment that is compatible with multiple languages.

    • You select a different display language to the language that the term store uses on a site.

    • You try to add a term to a taxonomy field.

    In this scenario, the synonyms for the term are not available.

Resolution

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.

Prerequisites

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

You do not have to make any changes to the registry after you install this hotfix.

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!

×