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


Issues that this hotfix package fixes

  • Assume that you open an Office document from a SharePoint library. Then you edit it, and leave it unattended. After several minutes, you access the same document without opening it in Office applications (for example, you click the document in a mapped network drive that is mapped to the SharePoint library), and then you try to save the opened document. In this situation, the save operation fails. Additionally, you receive the following error message:

    Unable to save the document.

  • Assume that your Preferred Name contains a comma (,) and you create or edit an item on a SharePoint site. When the SharePoint site retrieves the value from the Preferred Name field, an additional comma appears next to the original one.

  • Assume that you apply a multiple values filter to a SharePoint list that contains a calculated column. The filter result may be incorrect.

  • Assume that you configure a SharePoint group that enables requests to join/leave this group. When a user tries to join the group, the operation fails. Additionally, the user receives an error message that resembles the following:

    Multiple contents applied to PlaceHolderPageTitleInTitleArea.

  • Assume that you browse to a SharePoint site by using Internet Explorer 8, and you edit a SharePoint list item that contains an image. When you select the image and then rest the mouse pointer on the ribbon, you may receive a JavaScript error. Additionally, you may be unable to save the list item.

  • You may receive an "The attempted operation is prohibited because it exceeds the list view threshold enforced by the administrator." error when you create a custom NewForm for a list by using SharePoint Designer and then try to add items by using the custom NewForm.

  • Assume that you create a SharePoint subsite where the name contains the text 'mobile'. You may experience many unexpected behavior when you try to browse to this subsite.

  • When you try to programmatically recover a file from an unattached content database, if the file in the database is dirty, you may receive a NullReferenceException.

  • Assume that you add a multiple lines of text column to a SharePoint list. You create a new list item and add a hyperlink to a URL by using a file:// protocol or a Universal Naming Convention (UNC) path. When you save the list item, the URL value is removed silently.

  • Assume that you create a SharePoint 2010 workflow to work with an external list by using SharePoint Designer 2013. The workflow cannot update the items on the external list.

  • Assume that you add a managed metadata column to a SharePoint document library. When you filter the library by the column header of the managed metadata field, the small icon that indicates the column is filtered disappears. Therefore, you cannot see which field is filtered, and you cannot clear the filter.

  • Consider the following scenario:

    • You set up an Office Web Apps Server.

    • You enable the site feature Open Documents in Client Application by Default.

    • You configure the settings of a SharePoint document library to Open in the client application in Advanced Settings.

    • You browse to the document library, select a PDF file, and then click View Properties in File tab (this browses to a page that displays the document properties for this PDF file).

    • You try to open the PDF file by clicking the file name on the page.

    In this scenario, the PDF file opens in the browser.

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?

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!