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

Article translations Article translations
Article ID: 2553031
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 October 13, 2011.

INTRODUCTION

Issues that this hotfix package fixes

  • Consider the following scenario. You add a Delay activity to a workflow. Then, you set the duration for the Delay activity. You deploy the workflow in SharePoint Foundation 2010. In this scenario, the workflow is not resumed after the duration of the Delay activity.
  • Consider the following scenario:
    • You add a custom list to an out-of-box meeting workspace site.
    • You set Change items into series items to Yes in the custom list.
    • You add an out-of-box workflow to the custom list, and then add a list item to the custom list.
    • You start the workflow on the list item.

    In this scenario, the workflow does not run and you receive the following error message:

    Error Occurred
  • Assume that a Web Part uses an AJAX control in SharePoint Foundation 2010. When an AJAX request occurs, SharePoint Foundation 2010 does not load client-side component scripts for the AJAX control. Additionally, the following exception occurs in the Sys$_ScriptLoader$_loadScriptsInternal recursive function:

    Object expected.
  • An incorrect code is generated for a Boolean field in SharePoint Foundation 2010 when you use the SPMetal tool to generate Visual Basic .NET classes.
  • When a user account name contains an apostrophe in a SharePoint Foundation 2010 web application, you cannot migrate the user account from a Windows authentication account to a claims-based authentication account.
  • The content type updates for all the sub sites time out. This occurs when you try to add a lookup column to a site content type in a SharePoint Foundation 2010 site collection.
  • Assume that you apply CSS styles that are referenced from an external CSS file to a SharePoint Foundation 2010 site. When you try to edit a webpage on the site, you receive an "Access denied" error message. Additionally, you receive the following warning message:

    This page is accessing information that is not under its control. This poses a security risk. Do you want to continue?
  • Consider the following scenario:
    • You use Microsoft Office Online to open a Word document that has a Chinese file name in a SharePoint Foundation 2010 site.
    • You copy the URL of the Word document.
    • You paste the URL as a navigation link on the Quick Launch bar.
    • You click the newly added navigation link on the Home Page.

    In this scenario, you receive the following error message:

    File not found.
  • Consider the following scenario:
    • You create a publishing site collection in SharePoint Foundation 2010.
    • You use an out-of-box article page layout to create a content page on the site.
    • You set the time zone and the site collection time zone between UTC-01:00 and UTC-12:00 on the SharePoint Foundation 2010 server.
    • You provide a date time value for the article start date on the content page.
    • You save the content page.
    • You publish the content page.

    In this scenario, the article start date is one day earlier than the date time value that you set.
  • Consider the following scenario:
    • You configure Alternate Access Mappings (AAM) for a SharePoint Foundation 2010 site collection.
    • You create an overlay to an existing calendar.
    • You try to access the calendar in the site collection.

    In this scenario, you cannot access the calendar.
  • Consider the following scenario:
    • You use the team site template to create a site collection in the German version of SharePoint Foundation 2010.
    • You add a document library that contains several custom columns to the site collection.
    • You save the site collection as a template.
    • You import and deploy the template to another site collection through Microsoft Visual Studio 2010.
    • You view the site collection that uses the template.

    In this scenario, certain custom column names contain incorrect German characters.
  • Assume that the tree view is enabled on a SharePoint Foundation 2010 site. When an SPList object name contains several characters followed by "_file" or "_files", the SPList object cannot be displayed on the SharePoint site.
  • Consider the following scenario:
    • You set the Locale to any location other than English (United States) on a SharePoint Foundation 2010 site.
    • You create a Date and Time lookup column that connects to a calendar in a document library.
    • You upload several files to the document library.
    • You group by the lookup column in the document library view.

    In this scenario, the date and time in the grouped view header uses United States formatting conventions.
  • Consider the following scenario:
    • You create a column in a custom list in a SharePoint Foundation 2010 document library.
    • You configure the column validation feature.
    • You add a list item that violates the restrictions in the column validation feature.

    In this scenario, you do not receive a notification message. Instead, you receive the following error message:

    List data validation failed.
  • Consider the following scenario:
    • You configure an alert for a list in SharePoint Foundation 2010.
    • You select a user from the Display alerts for list and delete the alert for the user on the Manage User Alerts page.

    In this scenario, the user who you deleted is still displayed in the Display alerts for list.
  • Consider the following scenario:
    • You add a metadata column to a library in SharePoint Foundation 2010.
    • You create a term set for the column.
    • You apply an Include descendants filter to the metadata column.

    In this scenario, you receive the following error message:

    <!--#RENDER FAILED -->
  • Assume that you create a Web Part that references data from another SharePoint site and has custom content types enabled. When you try to add the Web Part to a new Web Part page, the following exception occurs:

    ArgumentException: Value does not fall within the expected range.
  • Consider the following scenario:
    • You use a name that contains a question mark (?) to create a site column on a SharePoint Foundation 2010 site.
    • You create a site content type, and then add the site column to the site content type.
    • You add the site content type to a document library on a SharePoint site.
    • You upload a document to the document library.
    • You make changes to the site content type on the EditForm.aspx page that contains the site column.

    In this scenario, you lose the data that you previously changed in the site content type.
  • Assume that you have a Home Page that contains a Content Editor Web Part and some custom HTML code on a Microsoft Office SharePoint Server 2007 server. After you upgrade the SharePoint Server 2007 server to SharePoint Foundation 2010, the Content Editor Web Part cannot be displayed.
  • Consider the following scenario:
    • You create a new Pages library on a SharePoint Foundation 2010 site collection.
    • You create a column for the Pages library and set the column as required.
    • You create a new page.

    In this scenario, you receive the following error message:

    Updates are currently disallowed on GET requests. To allow updates on a GET, set the 'AllowUnsafeUpdates' property on SPWeb.
  • Consider the following scenario:
    • You create a web application in SharePoint Server 2010.
    • You create an explicit inclusion managed path in the web application.
    • You create several site collections on the managed path.
    • You detach a content database that contains the web application.
    • You reattach the content database.

    In this scenario, some site collections are not restored in the web application.
  • Assume that you view a discussion item on a SharePoint Server 2010 site. If the discussion item contains a user profile picture, the aspect ratio of the picture is not retained. Therefore, the picture appears distorted.
  • Consider the following scenario:
    • You create an all-day event calendar item in SharePoint Foundation 2010.
    • You save the calendar item and export it as an iCalendar (.ics) file.
    • You import the .ics file into an Outlook client.

    In this scenario, the date of the all-day event in the Outlook client is one day earlier than the date that you set in SharePoint Foundation 2010.
  • Consider the following scenario:
    • You add a custom ItemUpdating event receiver to a Pages library on a SharePoint Server 2010 publishing site.
    • You update a page in the Page library.
    • The event receiver cancels the update operation.
    • You try to save the page.

    In this scenario, you receive a save conflict message instead of an event receiver error message.
  • W3wp.exe consumes excessive CPU resources when you use nonstandard ASP.NET codes. This occurs when you create a new page on a SharePoint Foundation 2010 site. Therefore, other users cannot access the SharePoint site.
  • You have rows in the feature table that reference nonexistent rows in the solutions table on a SharePoint Foundation 2010 site collection. Therefore, the whole site collection breaks.
  • Consider the following scenario:
    • You create a new content type in a content type publishing hub on SharePoint Foundation 2010.
    • You publish the content type to subscribing sites.
    • You change the column order in the content type publishing hub.
    • You republish the content type to the subscribing sites.

    In this scenario, the column order is not updated on the subscribing sites.
  • Assume that a calendar contains a calculated column on a SharePoint Foundation 2010 site. An error occurs when you try to create a Gantt view for the calendar.
  • Consider the following scenario:
    • You install the June, 2011 cumulative update from Microsoft Knowledge Base article 2536599 on a Microsoft SharePoint Server 2010 server.
    • You add a Summary Link Web Part to a site collection.
    • You add a link to the Web Part, and then try you to save the Web Part.
    In this scenario, you receive the following error message:

    The security validation for this page is invalid.

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 Microsoft SharePoint Foundation 2010 or Microsoft 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-kb2553031-fullfile-x64-glb.exe14.0.6109.500534,410,7766-Oct-113:11

Microsoft Windows Installer .msp file information

Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Sts-x-none.mspNot Applicable34,499,0725-Oct-1116:37

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

Collapse this tableExpand this table
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.6108.5000124,80021-Jul-1113:11
Microsoft.sharepoint.administrationoperation.dll14.0.6108.5000833,45621-Jul-1113:11
Microsoft.sharepoint.applicationpages.administration.dll14.0.6108.5000608,12821-Jul-1113:11
Microsoft.sharepoint.applicationpages.dll14.0.6108.50001,058,72021-Jul-1113:11
Microsoft.sharepoint.client.dll14.0.6108.5000288,62421-Jul-1113:11
Microsoft.sharepoint.client.dll14.0.6108.5000288,62421-Jul-1113:11
Microsoft.sharepoint.client.serverruntime.dll14.0.6108.5000186,27221-Jul-1113:11
Microsoft.sharepoint.client.silverlight.dll14.0.6108.5000272,26421-Jul-1113:11
Microsoft.sharepoint.client.silverlight.runtime.dll14.0.6009.1000145,30420-Oct-106:07
Microsoft.sharepoint.dll14.0.6109.500216,783,20824-Aug-1119:03
Microsoft.sharepoint.dll14.0.6109.500216,783,20824-Aug-1119:03
Microsoft.sharepoint.dll14.900.6108.50001,795,96821-Jul-1113:11
Microsoft.sharepoint.dsp.dll14.0.6105.500059,26421-May-1118:37
Microsoft.sharepoint.dsp.oledb.dll14.0.6108.5000124,80021-Jul-1113:11
Microsoft.sharepoint.dsp.soappt.dll14.0.6108.500087,93621-Jul-1113:11
Microsoft.sharepoint.dsp.sts.dll14.0.6108.5000104,32021-Jul-1113:11
Microsoft.sharepoint.dsp.xmlurl.dll14.0.6108.500087,93621-Jul-1113:11
Microsoft.sharepoint.health.dll14.0.6017.100096,17619-Jan-114:40
Microsoft.sharepoint.identitymodel.dll14.0.6107.5000104,3201-Jul-1116:46
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.6108.5000649,08821-Jul-1113:11
Microsoft.sharepoint.powershell.intl.dll14.0.6108.500067,45621-Jul-1113:11
Microsoft.sharepoint.sandbox.dll14.0.6009.1000122,24820-Oct-104:31
Microsoft.sharepoint.search.dll14.0.6108.50004,850,05620-Jul-1113:40
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.6108.5000317,31221-Jul-1113:11
Microsoft.sharepoint.workflows.dll14.0.6108.500071,55221-Jul-1113:11
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.6108.5000382,86421-Jul-1114:01
Mssdmn.exe14.0.6108.5000790,40820-Jul-1113:40
Mssearch.exe14.0.6108.5000523,65620-Jul-1113:40
Mssph.dll14.0.6108.50001,672,07220-Jul-1113:40
Mssrch.dll14.0.6109.50004,987,7849-Aug-1112:10
Offparser.dll14.0.6106.50002,915,23212-Jun-110:38
Oisimg.dll14.0.6108.5000194,94421-Jul-1113:11
Oleparser.dll14.0.6108.500032,68021-Jul-1113:11
Onetnative.dll14.0.6106.5000584,07212-Jun-111:24
Onetutil.dll14.0.6109.50022,986,36024-Aug-1119:08
Onfda.dll14.0.6106.50002,782,60012-Jun-112:21
Owssvr.dll14.0.6109.50026,590,84824-Aug-1119:01
Owstimer.exe14.0.6108.500074,09621-Jul-1113:11
Policy.12.0.microsoft.sharepoint.search.dll14.0.6107.500011,1681-Jul-1117:26
Psconfig.exe14.0.6009.1000567,19220-Oct-106:07
Psconfigui.exe14.0.6009.1000825,24020-Oct-106:07
Query.dll14.0.6108.5000371,05620-Jul-1113:40
Setup.exe14.0.6010.10001,377,14428-Oct-107:54
Spmetal.exe14.0.6107.5000149,4321-Jul-1116:46
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.6108.500041,85621-Jul-1113:11
Stsadm.exe14.0.6108.5000346,02421-Jul-1113:11
Stssoap.dll14.0.6108.5000472,96021-Jul-1113:11
Stswel.dll14.0.6109.50023,254,65624-Aug-1119:01
Tquery.dll14.0.6109.50005,646,2169-Aug-1112:10
Wssadmin.exe14.0.6108.500015,79221-Jul-1113:11
Wsssetup.dll14.0.6015.10007,588,20020-Dec-1020:24
Wsstracing.exe14.0.6106.5000107,90412-Jun-110:38

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
<ArticleBemisContent xmlns="http://www.microsoft.com/office/sustainedengineering/kbcontent" Version="15.0.5001.1000" Revision="0" IRISArticleID="63" ContentID="2553031"> <Summary /> <RelatedBugs /> <FileList /> <ReplacementInformation /> <Prerequisities /> <RestartInformation> <Info SourceName="RestartCheck"> <Data>No</Data> </Info> </RestartInformation> <UninstallInformation /> <TargetedApplications /> <RegistryChanges /> <ObtainUpdate /> <UpdateNotes /> <Keywords /> <SecurityBulletin /> <SecurityUpdateSupport /> </ArticleBemisContent>

Properties

Article ID: 2553031 - Last Review: April 17, 2014 - Revision: 5.1
Keywords: 
kbqfe kbsurveynew kbexpertiseinter kbhotfixserver kbhotfixrollup kbautohotfix kbhotfixallversions KB2553031

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