Article ID: 2598348 - View products that this article applies to.
Expand all | Collapse all

On This Page

SUMMARY

This article describes the Microsoft SharePoint Foundation 2010 issues that are fixed in the SharePoint Foundation 2010 hotfix package that is dated July 2, 2012.

INTRODUCTION

Issues that this hotfix package fixes

  • An update enables the MigrateUser method to accept content database names as parameters so that you can perform migrations on the specified list of database. Additionally,this update enables you performthe migrationin parallelif you have a large volume of data that contains millions of users.
  • Assume that a SharePoint Designer workflow sends an email message that has more than 2,000 characters in the email message body. In this case, a character at the beginning of a line is missing in the email message body.
  • The navigation link for a document library on a subsite with unique permissions disappears intermittently.
  • An update provides APIs or cmdlets to make sure that the same claim type uses the same encoding character on multiple SharePoint farms.
  • When you try to export translations for a site in SharePoint Foundation 2010, you receive the following error message:
    Server Error in '/' Application
  • Assume that you use the metadata navigation and filter feature to filter a view of a document library. When you check in or check out a document through the menu on the ribbon, you receive the following error exception:
    System.ArgumentException: Value does not fall within the expected range. at Microsoft.SharePoint.SPWeb.GetFile(String strUrl) at Microsoft.SharePoint.ApplicationPages.Checkin.get_File() at Microsoft.SharePoint.ApplicationPages.Checkin.OnPreInit(EventArgs e) at System.Web.UI.Page.PerformPreInit() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
  • Consider the following scenario:
    • You create a site collection by using the Publishing Portal template.
    • You create a site lookup column that fetches information from a custom list.
    • You add a new site content type to the page library settings.
    • You create a new page by using the site content type and then select a value for the lookup column.
    • You save the new page.
    • You edit the page and then check it in.
    In this scenario, the value that you selected for the lookup column is missing.
  • Assume that you use Microsoft SharePoint Designer 2010 to change a column width on the AllItems.aspx page. When you try to check out a document from the AllItems.aspx page on a site collection, the dialog box that prompts you to select a draft folder displays two times. Additionally, you receive the following error message after the dialog box pops out for the second time:
    This document could not be check out. You may not have permission to check out the document or it is already checked out or locked for editing by another user.
  • After you add the <FieldRef/> element to a content type schema, a field is not added to the existing list that uses the content type.
  • Consider the following scenario:
    • You create an approval workflow that contains a Type a message to include your request field on the approval page in Microsoft Office SharePoint Server 2007.
    • You migrate the workflow from SharePoint Server 2007 to SharePoint Foundation 2010.
    • You run an instance of the workflow in SharePoint Foundation 2010.
    In this scenario, the Type a message to include your request field does not display on the approval page.
  • Assume that you add some reusable content items to a reusable content list on a SharePoint page. When you edit and then save the page, certain reusable content items do not display. Additionally, some space lines are added to the page.
  • Assume that you set a user as a site collection administrator and do not assign other additional permissions to them. When you delete the user from the site collection, the Site Data web service does not emit the site collection level security update.
  • Assume that you disable the Recycle Bin in a site collection. After you run a workflow that deletes a list item, the list item is not deleted. Additionally, you receive the following error message:
    The Workflow could not delete the list item. Make sure the list exists and the user has permissions to delete items in the list. Unknown Error
  • You create a custom list in a site that inherits permissions from the site collection. Then, you add a list item to the custom list and break the permissions inheritance. In this situation, it takes a long time for you to grant a user permissions to the list item.
  • Assume that you create a sandboxed solution that enumerates a collection of SharePoint objects. When the enumerator throws an exception, a SecurityException exception is thrown.
  • After you install a content type that inherits from a custom content type, the out-of-box content types disappear in SharePoint Foundation 2010.
  • When you open a document on a search result by clicking View in Browser, the document is opened in an Office client instead of in Office Web App.
  • Assume that you set the regional settings for a site to a language other than English. When you try to filter a view on the site by clicking Show Filter Choices, you receive the following error message:
    <!-- #RENDER FAILED -->
  • Redirect pages do not work after you perform a content deployment to a public site collection.
  • Assume that you configure a list view web part to display list items by using the datasheet view on a SharePoint site. You save the site as a template, and then you create a new site by using the template. In this situation, the datasheet view setting on the list view web part is lost on the new site.
  • Assume that you create a team site on a web application that is configured to use claim-based authentication. When a three-state workflow is triggered on the team site, the Assign To property is empty in the workflow.
  • When you drag web parts from a web part adder tool part to a meeting workspace page, a JavaScript error occurs.
  • Assume that you enable the external BLOB storage in SharePoint Foundation 2010. After you move a document from a document library to a second document library, you cannot download the document from the second document library. Additionally, you receive the following error message:
    An unexpected error has occurred.
  • Assume that you configure a document library to require check-out for files. When you run a process that uploads and checks in files automatically to the document library, two files may be saved with the same name in the document library.
  • You lose permissions to new list items when you apply the SharePoint Foundation cumulative update that is described in Knowledge Base (KB) article 2598321. Additionally, you receive an HTTP 500 error message when you try to access the affected list items.
  • You cannot save a site as a site template after the solution gallery includes a solution that does not have a solution ID.
  • Assume that you send an email message that contains a document attachment to an email-enabled document library. The email message contains more than 255 characters in the email header. After you edit the document in an Office client, you cannot save the document to the document library.
  • Assume that you move documents from a document library to another document library through the Site Content and Structure page, and the destination library has managed metadata columns. When you edit the property of a document, columns that appear with "_0" are displayed unexpectedly.
  • After you change the calculated column name and the formula in the calculated column, publishing for the content type does not work correctly. This issue occurs when the content type subscriber timer job is running.
  • The XSLT List View web part unexpectedly compiles .xsl files every time that network load balancing sends an HTTP request to different SharePoint Front End (WFE) servers. This issue occurs when a solution is not deployed at the same time on the different WFE servers.
  • Assume that you use Internet Explorer 8 or Internet Explorer 9 to go to a SharePoint site and that you set the user interface language to a language other than the default language. When you go to the subsite of the SharePoint site, the subsite is displayed in the default language incorrectly.
  • Assume that two document libraries contain a same site column in different SharePoint sites. When you change the column value of the first site, the site column value in the document library of the second site is also changed, even though the second site is not a subsite of the first site.
  • Consider the following scenario:
    • You create a custom team subsite that has a content query web part on the home page.
    • You save the team subsite as site template.
    • You use the site template to create a subsite.
    • You use the content deployment feature to deploy the subsite to the other SharePoint farm.
    • You go to the subsite on the destination farm.
    In this scenario, you receive the following error message:
    A Web Part with this ID has already been added to this page.
  • A decrease in performance occurs when you perform a migration for many site collections. This issue occurs because the SPWebApplication.MigrateUser method does not cache certain data entries.
  • If a site is deleted by a dead site delete timer job, the site is deleted permanently. Instead, the site should be sent to the Site Collection Recycle Bin.
  • When you browse the home page as an anonymous user on a SharePoint site that has the anonymous access enabled, the following error message is logged in the Unified Logging Service (ULS) log:
    The EXECUTE permission was denied on the object 'proc_SecGetUserAccountDirectoryPath'
  • When you reclick a tree node of a custom Claims Provider through the Select People and Groups dialog box in the People Picker control, a user entry that belongs to the child node of the current tree node is displayed unexpectedly in addition to the user entry under the current tree node.
  • A document library cannot receive incoming email messages when the site collection in which the document library exists is not configured by using the site collection quotas feature.
  • Assume that you add a custom web part to a web part page. When you change the name of the custom web part assembly, the web part page does not display the web part, and an error occurs.

RESOLUTION

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, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note 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

To install this hotfix, you must have SharePoint Foundation 2010 or SharePoint Foundation 2010 Service Pack 1 installed.

Restart requirement

You may 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 the hotfix 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.


Download information

Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Sharepointfoundation2010-kb2598348-fullfile-x64-glb.exe14.0.6123.500235,262,90426-Jun-128:22

Microsoft Windows Installer .msp file information

Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Wss-x-none.mspNot Applicable36,203,00826-Jun-1212:17

After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the table.

Wss-x-none.msp information

Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Addgallery.officeonlineprovider.dll14.0.6015.100055,16829-Aug-1113:53
Csisrv.dll14.0.6123.50003,370,1528-Jun-1212:59
Dwdcw20.dll14.0.6116.5000637,72817-Jan-1219:47
Microsoft.businessdata.dll14.0.6009.1000116,6321-Sep-1117:17
Microsoft.sharepoint.addgallery.server.dll14.0.6108.5000124,80029-Aug-1113:53
Microsoft.sharepoint.administrationoperation.dll14.0.6122.5000834,22416-May-1219:37
Microsoft.sharepoint.applicationpages.administration.dll14.0.6108.5000608,12829-Aug-1113:52
Microsoft.sharepoint.applicationpages.dll14.0.6122.50001,063,58416-May-1219:37
Microsoft.sharepoint.client.dll14.0.6108.5000288,62429-Aug-1113:53
Microsoft.sharepoint.client.dll14.0.6108.5000288,62429-Aug-1113:53
Microsoft.sharepoint.client.serverruntime.dll14.0.6108.5000186,27229-Aug-1113:53
Microsoft.sharepoint.client.silverlight.dll14.0.6108.5000272,26429-Aug-1113:53
Microsoft.sharepoint.client.silverlight.runtime.dll14.0.6009.1000145,30429-Aug-1113:53
Microsoft.sharepoint.dll14.0.6123.500016,833,1208-Jun-1211:08
Microsoft.sharepoint.dll14.0.6123.500016,833,1208-Jun-1211:08
Microsoft.sharepoint.dll14.900.6123.50001,796,7288-Jun-1211:08
Microsoft.sharepoint.dsp.dll14.0.6105.500059,26429-Aug-1113:53
Microsoft.sharepoint.dsp.oledb.dll14.0.6108.5000124,80029-Aug-1113:53
Microsoft.sharepoint.dsp.soappt.dll14.0.6108.500087,93629-Aug-1113:53
Microsoft.sharepoint.dsp.sts.dll14.0.6108.5000104,32029-Aug-1113:53
Microsoft.sharepoint.dsp.xmlurl.dll14.0.6108.500087,93629-Aug-1113:53
Microsoft.sharepoint.health.dll14.0.6017.100096,17629-Aug-1113:53
Microsoft.sharepoint.identitymodel.dll14.0.6120.5000109,17625-Apr-121:48
Microsoft.sharepoint.intl.dll14.0.6114.50001,010,48828-Nov-118:33
Microsoft.sharepoint.library.dll14.0.6114.5000166,71228-Nov-118:33
Microsoft.sharepoint.linq.dataservice.dll14.0.6023.100051,10429-Aug-1113:53
Microsoft.sharepoint.linq.dll14.0.6101.5000374,64029-Aug-1113:53
Microsoft.sharepoint.powershell.dll14.0.6123.5002649,84825-Jun-1218:36
Microsoft.sharepoint.powershell.intl.dll14.0.6108.500067,45629-Aug-1113:53
Microsoft.sharepoint.sandbox.dll14.0.6009.1000122,24829-Aug-1113:54
Microsoft.sharepoint.search.dll14.0.6123.50004,854,4086-Jun-125:05
Microsoft.sharepoint.search.intl.dll14.0.6009.1000378,78429-Aug-1113:40
Microsoft.sharepoint.usercode.dll14.0.6009.100034,68829-Aug-1113:53
Microsoft.sharepoint.workflowactions.dll14.0.6122.5000318,08016-May-1219:37
Microsoft.sharepoint.workflows.dll14.0.6108.500071,55229-Aug-1113:55
Microsoft.web.commandui.dll14.0.6016.1000137,06429-Aug-1114:05
Microsoft.web.commandui.dll14.0.6016.1000137,06429-Aug-1114:05
Microsoft.web.design.server.dll14.0.6108.5000382,8641-Sep-1117:17
Mssdmn.exe14.0.6119.5000790,85625-Apr-121:45
Mssearch.exe14.0.6116.5000524,61617-Jan-1219:26
Mssph.dll14.0.6116.50001,674,05617-Jan-1219:26
Mssrch.dll14.0.6122.50004,988,04015-May-1214:25
Offparser.dll14.0.6123.50002,923,6728-Jun-1211:07
Oisimg.dll14.0.6123.5000195,7048-Jun-1211:07
Oleparser.dll14.0.6123.500033,4408-Jun-1211:07
Onetnative.dll14.0.6123.5000584,8328-Jun-1212:17
Onetutil.dll14.0.6123.50002,987,1288-Jun-1212:17
Onfda.dll14.0.6123.50002,785,4088-Jun-1212:58
Owssvr.dll14.0.6123.50006,627,4488-Jun-1211:07
Owstimer.exe14.0.6123.500074,8568-Jun-1211:07
Policy.12.0.microsoft.sharepoint.search.dll14.0.6107.500011,16829-Aug-1113:39
Psconfig.exe14.0.6009.1000567,19229-Aug-1113:53
Psconfigui.exe14.0.6009.1000825,24029-Aug-1113:53
Query.dll14.0.6108.5000371,05629-Aug-1113:42
Setup.exe14.0.6118.50001,378,10425-Apr-121:56
Spmetal.exe14.0.6107.5000149,43229-Aug-1113:53
Spuchostservice.exe14.0.6105.5000108,49629-Aug-1113:53
Spucworkerprocess.exe14.0.6015.100047,05629-Aug-1113:53
Spucworkerprocessproxy.exe14.0.6009.1000124,89629-Aug-1113:53
Spwriter.exe14.0.6123.500042,6168-Jun-1211:07
Stsadm.exe14.0.6119.5000346,98425-Apr-121:49
Stssoap.dll14.0.6122.5000473,72016-May-1219:37
Stswel.dll14.0.6123.50003,260,0248-Jun-1211:07
Tquery.dll14.0.6123.50005,646,9846-Jun-124:51
Wssadmin.exe14.0.6122.500016,55216-May-1219:37
Wsssetup.dll14.0.6120.50007,595,61625-Apr-121:56
Wsstracing.exe14.0.6123.5000108,6648-Jun-1211:07

REFERENCES

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 2598348 - Last Review: July 3, 2012 - Revision: 1.0
APPLIES TO
  • Microsoft SharePoint Foundation 2010
Keywords: 
kbqfe kbsurveynew kbexpertiseinter kbhotfixserver kbhotfixrollup kbautohotfix KB2598348

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com