Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Description of the SharePoint Foundation 2010 hotfix package (sts-x-none.msp): June 30, 2011

Description of the SharePoint Foundation 2010 hotfix package (sts-x-none.msp): June 30, 2011

View products that this article applies to.

Summary

This article describes the Microsoft SharePoint Foundation 2010 issues that are fixed in the SharePoint Foundation 2010 hotfix package that is dated June 30, 2011.

Known issue 1

After you install an earlier build of this hotfix, the following services may fail at either runtime or the provision process if you run these services by using a user account other than the farm administrator account:

  • Session State Service
  • Secure Store Service
  • Business Data Connectivity (BDC) Service

Note This issue is fixed in this hotfix package.


Known issue 2

After you install this hotfix, you must restart the User Profile Synchronization Service for profile synchronization to work correctly.

Workaround

To work around this issue, follow these steps:

  1. Visit Central Administration.
  2. Click Mange Services on the System Settings section.
  3. Find User Profile Synchronization Service in the list of services and then click Stop if its status is Started. Click Start and provide the credentials to start the User Profile Synchronization Service as soon as its status is Stopped.

↑ Back to the top

INTRODUCTION

Issues that this hotfix package fixes

  • When a list has multiple views in Microsoft SharePoint Foundation 2010, the views in the Current View drop-down box are not displayed in alphabetical order.
  • Information Rights Management (IRM) is not functioning when a Security Assertion Markup Language (SAML) token is used in a SharePoint Foundation 2010 web application.
  • The method of the DspSts web service, and the input parameters or output parameters of the DspSts web service are marked as obsolete in SharePoint Foundation 2010. Therefore, when you use the DspSts web service, it does not return expected results.
  • Consider the following scenario:
    • You create a SharePoint Foundation web application. The application pool identity of this web application is running under the farm administrator credentials.
    • You log on to the web application by using a Claims authentication account.
    • You perform a task that requires farm administrator permissions. For example, you try to create a site collection.

    In this scenario, you receive the following error message:

    Access Denied
  • Consider the following scenario:
    • You configure a SharePoint Foundation 2010 site to use authentication from an identity provider.
    • You use a Security Assertion Markup Language (SAML) token to log on to the identity provider.
    • You press the back button in your web browser after you are redirect to a SharePoint page.

    In this scenario, an infinite loop occurs between the identity provider page and the SharePoint page.
  • Consider the following scenario:
    • You can configure a SQL Server Reporting Services to work with SharePoint Foundation 2010.
    • You have a SharePoint list that breaks the permission inheritance.
    • You use the Reporting Services to generate reports from the SharePoint list data source.

    In this scenario, you may receive the following error message:

    An error has occurred during report processing. (rsProcessingAborted)
    Cannot read the next data row for the dataset DataSet1. (rsErrorReadingNextDataRow)
    For more information about this error navigate to the report server on the local server machine, or enable remote errors.
  • Consider the following scenario:
    • You have a My Site page in a site collection that uses the Active Directory Federation Services (ADFS) authentication in SharePoint Server 2010.
    • You use anonymous access permissions to access the My Site Page.
    • You try to view the My Site page that uses the ReturnUrl query string parameter in the URL.

    In this scenario, a credential dialog box pops up instead of an ADFS authentication page. If you click Cancel in the credential dialog box, you receive the following error message:

    The request failed with HTTP status 401: Unauthorized.
  • Assume that trusted claims authentication is enabled in SharePoint Foundation 2010. Then, you try to visit a SharePoint site that has a space character in its URL. In this situation, you receive the following error message:

    Http Error 400 Bad Request
  • Consider the following scenario:
    • You create a calendar list in SharePoint Foundation 2010.
    • You configure a customized content type in the calendar list.
    • You save this calendar list as a template.
    • You use the template to create a new calendar list.

    In this scenario, the content type settings of the new calendar list are unexpectedly changed.
  • Consider the following scenario:
    • You use a blank site template to create a subsite under a SharePoint Foundation 2010 site collection.
    • You enable the wiki page home page feature for this new subsite. Now, a new link is created in the Quick Launch menu.
    • You click the link.

    In this scenario, you are directed to an incorrect page.
  • Consider the following scenario:
    • You enable the document sets feature in SharePoint Foundation 2010.
    • You create a document library, and then add a document set content type to the document library.
    • You save the document library as a template.
    • You use this template to create a new document library.
    • You open the document library.

    In this scenario, the existing document set display as a folder instead of the document set.
  • A user creates several personal views in a SharePoint Foundation site. When the user switches between these personal views, the view name is not updated to the currently displayed view.
  • Consider the following scenario:
    • You customize the value of the AlternateHeader property or the SiteLogoUrl property in a SharePoint Foundation 2010 site.
    • You save this site as a template.
    • You use this template to create a new site.

    In this scenario, the values of the AlternateHeader property or the SiteLogo property in the new site are incorrect.
  • Consider the following scenario. You have a list name that begins with a number in SharePoint Foundation 2010. You try to create a service reference to the Listdata.svc data service in Visual Studio. In this scenario, you receive the following error message:

    Error 7001: Schema specified is not valid.
  • An error occurs when you pass the Editor attribute to the GetVersionCollection method of the Lists.asmx Web service in SharePoint Foundation.
  • Consider the following scenario. You export a site collection that contains a list in SharePoint Foundation 2010. Then, you import the site collection. In this scenario, the LastItemModifiedDate property on the list is not retained. Instead, the LastItemModifiedDate property is set to the import time.
  • Consider the following scenario:
    • You add a security group to an existing SharePoint Foundation 2010 site. The security group is created in Active Directory Domain Services (AD DS).
    • You export the SharePoint site.
    • You change the name of the security group in AD DS.
    • You import the SharePoint site to a new SharePoint site.

    In this scenario, the imported security group is changed to a user. Additionally, the stsadm –o migrategroup command does not work.
  • Consider the following scenario:
    • You click the Variation link to configure the variation setting in a Windows SharePoint Services 3.0 publishing site.
    • You click the Variation Labels link to create two variation labels.
    • You click the Create Hierarchies link to create hierarchies.
    • You create a new publishing page in the source variation site.
    • You publish the new publishing page, and then you wait until the page propagation ends.
    • You edit the page in the destination variation site, and then you try to save it.

    In this scenario, you receive the following error message:

    The settings for this list have been changed. Refresh your browser before editing this list.
  • Consider the following scenario. You create a discussion board lists in SharePoint Foundation 2010. Then, you create several pages through replies on the Flat view or the Threaded view. In this scenario, the pagination control displays incorrect item ranges. Additionally, when you use the pagination control to page backward through the replies, the pagination control is into a bad state.
  • Certain Unicode characters are not handled correctly when you use the SPWebApplication.MigrateUsers method to perform a user migration to claims authentication in SharePoint Foundation 2010. Therefore, this behavior results in bad user account entries.
  • Consider the following scenario:
    • You create a new site in an existing web application in SharePoint Server 2010.
    • You enable the SharePoint Server Publishing Infrastructure feature.
    • You configure a project page’s content type to associate with certain workflows, such as Approval workflow, Collect Feedback workflow and Collect Signatures workflow.
    • You try to create a new enterprise wiki subsite.

    In this scenario, you receive the following error message:

    Save Conflict.
    Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes.
    Troubleshoot issues with Microsoft SharePoint Foundation.
    Correlation ID: {GUID}
    Date and Time: {MM/DD/YYYY HH:MM:SS A/PM}
  • When you try to click the title of a list item in the workflow status page in SharePoint Foundation 2010, the link of the list item is broken.
  • Consider the following scenario. You clear the Enable Asynchronous Load check box in the XSLTListView Web Part properties pane in SharePoint Foundation 2010. Then, you verify this check box again in the XSLTListView Web Part properties pane. In this scenario, the check box is still selected.
  • Consider the following scenario. More than 200 subsites and lists are created by using SharePoint object model. The BreakRoleInheritance method is called during those subsites and lists creation process. In this scenario, a SQL deadlock occurs in SharePoint Foundation 2010.
  • SharePoint Foundation 2010 solution packages that use the binding redirect assembly attribute do not work for certain PublicKeyTokens.
  • This hotfix introduces a new ForceDeleteSite method to the SPContentDatabase Class. This method is functionally equal to the existing stsadm –o deletesite –force command.
  • Consider the following scenario:
    • You perform a content deployment from a source web application to a destination web application in SharePoint Foundation 2010.
    • You select languages under the Alternate language section in the source web application.
    • You perform an incremental content deployment.

    In this scenario, the alternative language setting is not changed in the destination web application.
  • Content databases cannot be upgraded when the databases contain certain Web Parts that are present or absent in SharePoint Server 2010.
  • Consider the following scenario:
    • You create a wiki page library in SharePoint Foundation 2010.
    • You add this wiki page library as a Web Part into a page within the library itself.
    • You save this SharePoint site that includes all the contents as a template.
    • You use this template to create a new SharePoint site.
    • You try to access the page that contains the wiki page library Web Part in the new SharePoint site.

    In this scenario, you receive the following error message:

    An Unexpected error has occurred.
  • Assume that you create a discussion list in a SharePoint Foundation 2010 site. After you apply the hotfix package that is described in Microsoft Knowledge Base (KB) article 2479788, you cannot access this discussion list.
  • After you apply the hotfix package that is described in KB article 2516472, the Trusted Identity claim provider does not appear when you open SharePoint People Picker in SharePoint Foundation 2010.
  • Consider the following scenario:
    • You create a new list view that groups the results in descending order in a SharePoint Foundation 2010 list.
    • You configure the number of groups that are displayed per page in the list view.
    • You add enough list items that exceed the number of groups configured per page in the list view.
    • You use the new list view to view the items in the SharePoint list.

    In this scenario, not all the groups and items that should be in the list view are displayed.
  • Consider the following scenario:
    • You deploy content from a source site to a destination site in SharePoint Foundation 2010.
    • You access a document library without making any changes in the destination site.
    • You click View all site content in the destination site.

    In this scenario, the value in the Last Modified column in the All Site Content page is changed to the current date, or to the current time.
  • Assume that you perform an incremental content deployment on a destination SharePoint Server 2010 farm. In this situation, the changes for the alternative language settings on the source farm are not reflected on the destination farm.
  • 2553060 The RSS feeds do not display the query results from the Search Core Results Web Part in SharePoint Server 2010
  • 2553059 Search Paging Web Part generates a broken webpage when you perform a search in SharePoint Server 2010
  • 2553058 SharePoint Server 2010 takes longer than expected to return search results from a content index that has multiple ACLs applied
  • 2553057 Search function returns incorrect results when you search by author name in SharePoint Server 2010
  • 2553056 The SearchServiceApplication.Pause() command does not return search results if a SharePoint query server is shut down in a SharePoint Server 2010 farm which has more than one SharePoint query servers
  • 2552995 You are forced to select a content type for a file when you save the file to a document library in SharePoint Server 2010
  • 2552142 Search returns incomplete results after you install Office Online in SharePoint Server 2010
  • 2551695 You are not returned to the Search Results page after you create an alert warning in an extranet environment in SharePoint Server 2010
  • 2537540 SharePoint Health Analyzer rules do not automatically defragment the property store in SharePoint Server 2010
  • 2537539 A query times out if it takes more than 10 seconds to return the search results in SharePoint Server 2010, Search Server 2010, or in SharePoint Foundation 2010
  • 2532279 You cannot create another content type that is based on a base content type in SharePoint Foundation 2010

↑ Back to the top

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=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 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 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.


Download information

File nameFile versionFile sizeDateTime
Sharepointfoundation2010-kb2536591-fullfile-x64-glb.exe14.0.6106.500234,329,12030-Jun-1114:23

Microsoft Windows Installer .msp file information

File nameFile versionFile sizeDateTime
Sts-x-none.mspNot Applicable34,426,88030-Jun-113:20

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 following table.

Sts-x-none.msp information

File nameFile versionFile sizeDateTime
Addgallery.officeonlineprovider.dll14.0.6015.100055,16820-Dec-1012:03
Csisrv.dll14.0.6106.50003,368,88012-Jun-112:24
Dwdcw20.dll14.0.6015.1000636,76820-Dec-1019:41
Microsoft.businessdata.dll14.0.6009.1000116,63220-Oct-105:14
Microsoft.sharepoint.addgallery.server.dll14.0.6015.1000124,80020-Dec-1012:03
Microsoft.sharepoint.administrationoperation.dll14.0.6010.1000829,36028-Oct-106:51
Microsoft.sharepoint.applicationpages.administration.dll14.0.6106.5001608,12819-Jun-1111:08
Microsoft.sharepoint.applicationpages.dll14.0.6106.50011,058,72019-Jun-1111:08
Microsoft.sharepoint.client.dll14.0.6106.5001288,62419-Jun-1111:08
Microsoft.sharepoint.client.dll14.0.6106.5001288,62419-Jun-1111:08
Microsoft.sharepoint.client.serverruntime.dll14.0.6106.5001186,27219-Jun-1111:08
Microsoft.sharepoint.client.silverlight.dll14.0.6106.5001272,26419-Jun-1111:08
Microsoft.sharepoint.client.silverlight.runtime.dll14.0.6009.1000145,30420-Oct-106:07
Microsoft.sharepoint.dll14.0.6106.500216,770,92029-Jun-111:03
Microsoft.sharepoint.dll14.0.6106.500216,770,92029-Jun-111:03
Microsoft.sharepoint.dll14.900.6106.50011,795,96819-Jun-1111:08
Microsoft.sharepoint.dsp.dll14.0.6105.500059,26421-May-1118:37
Microsoft.sharepoint.dsp.oledb.dll14.0.6106.5001124,80019-Jun-1111:08
Microsoft.sharepoint.dsp.soappt.dll14.0.6106.500187,93619-Jun-1111:08
Microsoft.sharepoint.dsp.sts.dll14.0.6106.5001104,32019-Jun-1111:08
Microsoft.sharepoint.dsp.xmlurl.dll14.0.6106.500187,93619-Jun-1111:08
Microsoft.sharepoint.health.dll14.0.6017.100096,17619-Jan-114:40
Microsoft.sharepoint.identitymodel.dll14.0.6106.5002104,32029-Jun-111:03
Microsoft.sharepoint.intl.dll14.0.6010.10001,009,53628-Oct-106:51
Microsoft.sharepoint.library.dll14.0.6022.1000165,7602-Mar-1112:01
Microsoft.sharepoint.linq.dataservice.dll14.0.6023.100051,10411-Mar-118:24
Microsoft.sharepoint.linq.dll14.0.6101.5000374,64013-Apr-1119:19
Microsoft.sharepoint.powershell.dll14.0.6105.5000644,99221-May-1118:37
Microsoft.sharepoint.powershell.intl.dll14.0.6009.100067,45620-Oct-106:07
Microsoft.sharepoint.sandbox.dll14.0.6009.1000122,24820-Oct-104:31
Microsoft.sharepoint.search.dll14.0.6105.50004,849,03218-May-1116:38
Microsoft.sharepoint.search.intl.dll14.0.6009.1000378,78420-Oct-104:31
Microsoft.sharepoint.usercode.dll14.0.6009.100034,68820-Oct-106:07
Microsoft.sharepoint.workflowactions.dll14.0.6106.5001317,31219-Jun-1111:08
Microsoft.sharepoint.workflows.dll14.0.6106.500171,55219-Jun-1111:08
Microsoft.web.commandui.dll14.0.6016.1000137,0647-Jan-112:38
Microsoft.web.commandui.dll14.0.6016.1000137,0647-Jan-112:38
Microsoft.web.design.server.dll14.0.6106.5001382,86419-Jun-1120:47
Mssdmn.exe14.0.6105.5000790,40818-May-1116:30
Mssearch.exe14.0.6105.5000523,65618-May-1116:30
Mssph.dll14.0.6105.50001,672,07218-May-1116:30
Mssrch.dll14.0.6105.50004,986,76018-May-1116:30
Offparser.dll14.0.6106.50002,915,23212-Jun-110:38
Oisimg.dll14.0.6106.5001194,94419-Jun-1111:08
Oleparser.dll14.0.6106.500132,68019-Jun-1111:08
Onetnative.dll14.0.6106.5000584,07212-Jun-111:24
Onetutil.dll14.0.6106.50022,982,26429-Jun-1117:14
Onfda.dll14.0.6106.50002,782,60012-Jun-112:21
Owssvr.dll14.0.6106.50026,588,80029-Jun-111:03
Owstimer.exe14.0.6106.500174,09619-Jun-1111:08
Policy.12.0.microsoft.sharepoint.search.dll14.0.6013.100011,16819-Nov-108:01
Psconfig.exe14.0.6009.1000567,19220-Oct-106:07
Psconfigui.exe14.0.6009.1000825,24020-Oct-106:07
Query.dll14.0.6015.1000371,05620-Dec-1012:30
Setup.exe14.0.6010.10001,377,14428-Oct-107:54
Spuchostservice.exe14.0.6105.5000108,49621-May-1118:37
Spucworkerprocess.exe14.0.6015.100047,05620-Dec-1012:03
Spucworkerprocessproxy.exe14.0.6009.1000124,89620-Oct-106:07
Spwriter.exe14.0.6106.500141,85619-Jun-1111:08
Stsadm.exe14.0.6106.5001346,02419-Jun-1111:08
Stssoap.dll14.0.6106.5001472,96019-Jun-1111:08
Stswel.dll14.0.6106.50023,253,12029-Jun-111:03
Tquery.dll14.0.6106.50005,646,2168-Jun-114:33
Wssadmin.exe14.0.6010.100015,79228-Oct-106:51
Wsssetup.dll14.0.6015.10007,588,20020-Dec-1020:24
Wsstracing.exe14.0.6106.5000107,90412-Jun-110:38

↑ Back to the top

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

↑ Back to the top

Keywords: kbcu, kbsurveynew, kbqfe, kbhotfixserver, kbhotfixrollup, kbexpertiseinter, kbautohotfix, kbhotfixallversions, kb

↑ Back to the top

Article Info
Article ID : 2536591
Revision : 3
Created on : 3/30/2017
Published on : 3/30/2017
Exists online : False
Views : 364