This article describes the issues that are fixed in the SharePoint Foundation 2010 hotfix package that is dated November 11, 2014. Click the "Hotfix Download Available" button to get the hotfix. This hotfix has a prerequisite.
Issues that this hotfix package fixes
-
Assume that you upload or download files from a SharePoint Server 2010 folder. If the path of the folder exceeds the supported length, the PathTooLongException error message is displayed in the Unified Logging Service (ULS) log.
-
Assume that you create a managed metadata column in a SharePoint 2010 document library, and that the name of the column contains a space. When you copy a document from the document library to another library that has the same column defined, the value of the column is empty.
-
Assume that you browse to a SharePoint Server 2010 site by using Google Chrome browser. You click Site Actions > Site Permissions > Grant Permissions, and then you click the Address Book icon. In the Select People and Groups dialog box, you select a user and then click Add. In this situation, the user is added two times in the entity picker.
-
Assume that you enable tree view for a SharePoint Foundation 2010 site. When you browse to an Announcements list that contains no items, the Announcements list may not be opened, and an error page may be displayed.
-
After you install September 2014 cumulative update on a SharePoint Foundation 2010 server, you cannot add the server to a SharePoint Foundation 2010 farm by using the Psconfig command-line tool. Additionally, you receive the following error message:
The following is missing on <Computer Name>:
Hotfix for Microsoft SharePoint Server 2010 (KB2863913) 64-Bit Edition -
Assume that you enable the document version history feature for a SharePoint Foundation 2010 document library (to do this, select the check box of the Create major versions option in the Versioning Settings page, and then click OK). In this situation, when you upload a document to the document library and input lots of double-byte character set (DBCS) characters in the Version Comments field, you may receive the following error message even if the number of characters do not reach the maximum length allowed for the field:
You have exceeded the maximum length allowed (1023) for the Comments field. Reduce the amount of text included in the Comments field and try again.
-
Assume that you create a SharePoint 2010 document library that has a link fixup operation pending, and you delete a column that contains the original link from the library before the fixup. In this situation, when you browse to the library, an incorrect SQL command is run on SQL server. Additionally, an error message that resembles the following is logged in the ULS logs:
09/03/2014 15:39:41.56 w3wp.exe (0x0CB8) 0x0B68 SharePoint Foundation Database 5586 Critical Unknown SQL Exception 207 occurred. Additional error information from SQL Server is included below. Invalid column name '<Column Name>'. 97be9128-d6ca-483a-b59b-f44e960ac620
-
Consider the following scenario:
-
You create a SharePoint 2010 publishing site collection.
-
You create a new site in the site collection, and you select the Use unique permissions option when you create the site.
-
You migrate a user by using the MigrateUserAccount Windows PowerShell method.
-
You browse to the Manage Content and Structure page, and then you create a copy of the new site.
In this scenario, the user that you migrate is deleted from all group memberships unexpectedly.
-
-
Consider the following scenario:
-
You add a Data Form Web Part to a page of a SharePoint 2010 publishing site, and then you publish and approve the page.
-
You edit and make a change to the page, and then you save and check in the page.
In this scenario, when users who have different permission levels visit the page, they may experience performance issues.
-
-
Consider the following scenario:
-
You install and configure Remote BLOB Storage (RBS) for a Microsoft SQL Server 2008 R2 Express database server that supports a Microsoft SharePoint 2010 farm.
-
You enable RBS for a content database that contains a SharePoint site collection.
-
You publish a declarative workflow to a SharePoint library of the site collection.
-
You start the workflow, for example by uploading a document to the SharePoint library.
-
The volume that is used to store the remote blobs becomes inaccessible.
-
You recycle the application pool for the web application that holds the SharePoint site collection.
-
You browse to the Workflow Settings page of the SharePoint library.
In this scenario, the workflow is deleted. Additionally, the tasks associated with the workflow may also be deleted.
-
-
Consider the following scenario:
-
You grant the Full Control permission to a user to a SharePoint 2010 document library.
-
The document library does not inherit permissions from its parent.
-
You add a Person or Group column to the document library.
-
You create a public view for the document library, and you add a filter that hides some items from the list.
-
You add a column to the document library.
In this scenario, when the user refresh the public view, duplicate items might appear in the document library.
-
-
Consider the following scenario:
-
You configure a SharePoint 2010 sub site to stop inheriting permissions from its parent site.
-
You configure a SharePoint document library of the sub site to stop inheriting permissions from the sub site.
-
You configure a document in the document library to stop inheriting permissions from the document library.
-
You restore permissions inheritance for the sub site to inherit permissions from its parent site.
In this scenario, the yellow status bar displays the following information:
Some items of this list may have unique permissions which are not controlled from this page. Show me uniquely secured items of this list. This library has unique permissions.
Additionally, if you click Show me uniquely secured items of this list, the document library appears in the list, which is unexpected. And then, if you click view exceptions at the right side of the document library in the list, there is no items appear.
-
-
Consider the following scenario:
-
You add a new column to a SharePoint 2010 document library.
-
You add a validation formula for the new column.
-
You add a new document to the document library, and you fill in a valid value to the new column.
-
You change the validation formula for the new column so that the original formula does not work.
-
You edit the document property of the new document and you update the value of the new column so that it is valid for the new validation formula.
In this scenario, you cannot save the document property. Additionally, an error message that resembles the following is logged in the ULS logs:
09/19/2014 15:39:45.76 w3wp.exe (0x25F8) 0x1420 SharePoint Foundation General 8khx High The error "[Repro] - [Column Validation Failed.]" with hr:-2130208766 in the thread context is being replaced by error "The file Repro/Business Impact Statement.docx has been modified by <User Name> on 19 Sep 2014 12:58:18 -0500." with hr:-2130245375. The first error was not cleared before the second error replaced it. ccf42c63-036a-4ea7-986e-4723505ad128
-
How to get the hotfix
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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.
Hotfix information
Registry Information
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
Prerequisites
To install this hotfix, you must have SharePoint Foundation 2010 Service Pack 2 (SP2) installed.
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.
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.