Summary

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

INTRODUCTION

Issues that this hotfix package fixes

  • Assume that you set a SharePoint alert for an item. Additionally, assume that you use the SPFolder.MoveTo method to move the item between document libraries. In this situation, you cannot delete the alert.

  • When you upload some file attachments to a list item on a SharePoint Server 2013 site, the attachments are listed randomly and not in alphabetical order as expected.

  • Assume that you copy a SharePoint Server 2013 site collection in a content database and make a copy of the site collection in the same content database. You delete a file from a document library of the site collection. In this situation, there are two identical deleted files in the recycle bin.

  • Assume that you upload an attachment to a discussion on a SharePoint Server 2010 site. You upgrade the site to a SharePoint Server 2013 site. In this situation, the attachment of the discussion is not displayed and cannot be downloaded.

  • You cannot upgrade an instance of SharePoint Foundation 2010 that has Remote BLOB Storage (RBS) to SharePoint Foundation 2013.

  • Assume that you set up a lookup column in a SharePoint Server 2013 document library. You click the link of a lookup item in the lookup column to retrieve information on the item. In this situation, you encounter an error.

  • When you install both Serbian (Latin) and Serbian (Cyrillic) language packs on the Office Server site, the Multilingual User Interface (MUI) does not display the correct language.

  • When you try to change the master page of a publishing site collection that does not have subpages in SharePoint 2010 compatibility mode in SharePoint Server 2013, you encounter an error.

  • Consider the following scenario:

    • You add a field in a calendar on a SharePoint Server 2013 site.

    • You create an event in the calendar list.

    • You change the added field in the calendar and add a new event in the calendar list.

    • You try to group the events on the field.

    In this scenario, the two events are displayed in different groups.

  • When you add some lookup fields to a SharePoint Server 2013 document library, you cannot use OneDrive for Business to synchronize the document library.

  • Assume that you create a SharePoint Server 2010 mode site collection in SharePoint Server 2013. Then, you set permissions of a document library to no longer inherit from a parent document library. When you open the permissions page of the site, you receive the following error message:

    Show me uniquely secured content

  • When you upload a virus-infected file to a SharePoint Server 2013 server by using drag-and-drop, you receive a generic error message.

    Note The expected action is that you receive an error message from a virus scanner.

  • When you try to create a meeting workspace in a calendar event item in a SharePoint Server 2010 mode site on a SharePoint Server 2013 server, you encounter an internal server error.

  • When you try to upgrade some site collections from SharePoint Server 2010 to SharePoint Server 2013, you encounter a save conflict error.

  • 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 Sakha and Dari as the alternative language on a SharePoint Server 2013 site. Additionally, assume that you add Sakha and Dari as the default language in Internet Explorer. In this situation, Sakha and Dari are still displayed incorrectly on the site.

  • Consider the following scenario:

    • You have more than one search service application (SSA) in a SharePoint Server 2013 site.

    • You try to perform an action in the site that creates a managed property in the SSA that is associated with the site on the next search crawl.

    In this scenario, the managed property is always created in the first SSA.
    Note The expected action is that the managed property is created in the SSA that is associated with the site.

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:

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!

×