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

On This Page

Summary

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

INTRODUCTION

Issues that this hotfix package fixes

  • The data in a column is lost from a SharePoint list when you publish an InfoPath form to multiple form libraries and the form contains some new promoted fields. When you try to promote the data back to the list by using the Relink option on the document library, the data does not come back to the list.

    Note
    The Relink option will promote the data from the forms back to the SharePoint list in SharePoint 2010.
  • Assume that you create a document in a document library that contains a full-width space character (Double-Byte Character Set) in the file name. Additionally, assume that you create a list item that contains a link to the document. When you open the list item to click the link, the link cannot be accessed because the full-width space character in the link address is removed unexpectedly.
  • Assume that you create and save a survey list in a site collection inside a Web application, and that you save the site as a template. When you create a new site in the same site collection by using the custom template that is saved previously, the previous options of the survey list are not preserved. For example, the Show user names in survey results? and Respond to the survey options are not preserved.
  • Assume that you programmatically create a custom list that has a custom calendar view that specifies each title of its calendar columns during the activation of a custom feature. You create a List View Web Part in the home page of the current site that points to the custom list, and apply the custom calendar view to the List View Web Part by using the ListViewXml property. When you edit the current view of the List View Web Part in the site home page, the titles of the calendar columns are not retrieved.
  • This hotfix package adds the new SPDatabase.MultiSubnetFailover property. This property should be set to True in order to pass the MultiSubnetFailover=True parameter in the SQL connection string for databases that are part of Microsoft SQL Server 2012 AlwaysOn Availability Groups.
  • Assume that you create a Web application by using a custom site template and a list template together with the <ListTemplate /> element and BaseType=1 in the Onet.xml file in SharePoint 2010. When you try to create a document library by using the custom template, the custom document library template in the Silverlight window is not available.
  • Assume that you have the "Fabulous 40" templates installed on a Microsoft Office SharePoint Server 2007 farm. When you create a site by using different templates from the "Fabulous 40" after you upgrade SharePoint 2007 to Microsoft SharePoint Server 2010, the Web Part displays the following error message:
    Web Part Error: An error occurred while setting the value of this property: Microsoft.SharePoint.WebPartPages.DataFormWebPart:ListName - Exception has been thrown by the target of an invocation.
  • When you change the Sealed attribute to true for an Out of Box (OOB) Field, such as the "Title" field, you cannot change it back. The title field will be stored in the content database forever, and it will overwrite the behavior for every SharePoint list.

    Note
    Users should not be allowed to set the Sealed attribute.
  • Consider the following scenario:
    • You create a source site collection that contains more than one file that is greater than 10 megabytes (MB) in SharePoint Server 2010.
    • You create an empty destination site collection inside a Web application.
    • You enable incoming jobs and disable the requirement for Secure Sockets Layer (SSL) in the Central Administration site.
    • You create a new content deployment path and job in order to synchronize content between the source and destination farm.
    • You run the content deployment job.
    In this scenario, the content deployment job cannot delete all the .cab files from the TEMP location during the import phase.
  • When you upload an Office document that has a corrupted header to a document library that defines at least one Managed MetaDatacolumn in SharePoint Server 2010, the document is uploaded as a 0 kilobyte (KB) file in the database. Additionally, there is no error message to indicate that the file content is gone forever.
  • When you set a personal regional setting on a blog site by changing the user's time zone to a different value than the web time zone value in SharePoint 2010, the posts that are created and submitted from Microsoft Word show an incorrect publish time.
  • Assume that you create a site collection inside a Web application in SharePoint 2010. When you create a List View Web Part with grouping and aggregations (such as Totals) in the Agenda list in a new Basic Meeting Workspace, the view does not show the values for Totals. Additionally, an empty line appears where the aggregated value should be.
  • Assume that you create a list item in a list in the root page of the site collection inside a Web application. You add a list of files to the list item, and you leave the "Title" field blank. When you submit the form, the list of selected files for the attachment is cleared without notifying the user. Additionally, the form is refreshed together with the following validation error message:
    You must specify a value for this required field.

    Note
    Any files that were previously attached to the list item are not affected.
  • Considering the following scenario:
    • You develop an event receiver that implements a WorkflowCompleted event.
    • You deployed the event receiver to a site collection, and you associate the event receiver to a list.
    • You create a new content deployment path and job from this team site to a destination Web application.
    • You perform the content deployment through SharePoint 2010 Central Administration user interface.
    In this scenario, the content deployment job fails. Additionally, you receive the following error message:
    'System.Xml.Schema.XmlSchemaValidationException: The 'Type' attribute is invalid - The value 'WorkflowCompleted' is invalid according to its datatype 'urn:deployment-manifest-schema:SPEventReceiverType' - The Enumeration constraint failed. ---> System.Xml.Schema.XmlSchemaException: The Enumeration constraint failed.
  • Assume that you add some new documents as draft items in a document library in SharePoint 2010. You show the documents to people who have permissions to receive RSS feeds with links by clicking the Publish Major Version option. In this situation, only the approved items are sent in the RSS page to users. However, users can still browse to and view all the items in the list.

    Note
    This issue does not occur in SharePoint Server 2007.
  • Consider the following scenario:
    • You create a survey list in a subsite of a site collection in SharePoint Server 2010.
    • You change the Web Part view for the survey list in the home page of the subsite to the Graphical Summary view.
    • You save the subsite as a template that contains this content.
    • You create a new subsite on a site collection by using the template.
    In this scenario, the new subsite displays the questions and answers as text instead of as the Graphical Summary chart.
  • Considering the following scenario:
    • You deploy custom solutions to a SharePoint 2010 farm by using a .wsp file.
    • You create custom groups by activating the custom solutions.
    • You create a document library, and you upload a document to it.
    • You modify the document.
    In this scenario, the custom groups are not displayed.
  • Assume that you have a subsite whose name contains a space. You connect the subsite task list to Outlook from the task list ribbon by starting the OOB workflow. In this situation, Outlook cannot open the task list from the ribbon. Additionally, you receive the following error message:
    This task could not be updated at this time.
  • The Start and Due dates in the Gantt view are inaccurate by one day for sites that have a time zone west of Central Standard Time (UTC).

    Note
    This problem does not affect other Project Tasks list views.
  • The date picker of the Gannt view always edits the first List View Web Part’s cell if a Web Part page has two or more List View Web Parts in Gannt View.
  • Assume that you create a new User Profile Service Application (UPA), and you configure the synchronous database to use SQL authentication by setting up a SharePoint farm as an administrator. In this situation, the UPA creation is successful, but the UPA synchronization service cannot start.


    Note
    To resolve this issue, you must also apply the hotfix package in this article together with the following hotfix package:
    2687545 Description of the SharePoint Server 2010 hotfix package (Coreserver-x-none.msp): October 30, 2012
  • Assume that you create a document whose file name contains a full-width space character in a document library. You create a list item that contains a link to the document. When you open the item in order to click the link, the link is inaccessible because the full-width space character is removed from the link.


    Note
    To resolve this issue, you must also apply the hotfix package in this article together with the following hotfix packages:

    2687619 Description of the SharePoint Server 2010 hotfix package (Coreserver-x-none.msp, Wosrv-x-none.msp): October 30, 2012

    2687562 Description of the Office Online hotfix package (Wacwfe-x-none.msp, Xlwacwfe-x-none.msp): October 30, 2012

    2760391 Description of the SharePoint Server 2010 hotfix package (ems-x-none.msp, grs-x-none.msp, grs_hosted-x-none.msp): October 30, 2012
  • When you exclude a colon (:) from a lookup field of a list item in order to reference another item in a different list, you receive the following error message in a mobile list view:
    Index was outside the bounds of the array.
  • Assume that you have a running Out of Box (OOB) workflow task (for example, an "Approval – SharePoint 2010," "Collect Feedback – SharePoint 2010," or "Publishing Approval" task). When a task assignee edits the workflow task (for example, by approving or rejecting the trial), the task is locked and cannot be recovered.
    Note You must install this hotfix immediately after you install SharePoint Server 2010 Service Pack 1.


    Note
    To resolve this issue, you must also apply the hotfix package in this article together with the following hotfix package:
    2687614 Description of the SharePoint Server 2010 hotfix package (Coreservermui-xx-xx.msp): October 30, 2012
  • 2687599 Cannot change the SQL Server authentication password after you install a SharePoint Foundation 2010 farm
  • 2687601 High memory usage when you open a corrupted file on a SharePoint Server 2010 server

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 Service Pack 1 installed.

Restart requirement

You may 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-kb2687557-fullfile-x64-glb.exe14.0.6129.500032,890,08822-Oct-1220:23

Microsoft Windows Installer .msp file information

Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Wss-x-none.mspNot applicable32,787,45620-Oct-1221:55

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 file information

Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Csisrv.dll14.0.6129.50003,371,66420-Oct-1212:52
Dwdcw20.dll14.0.6116.5000637,72817-Jan-1219:47
Microsoft.sharepoint.addgallery.server.dll14.0.6128.5000125,57620-Sep-1210:33
Microsoft.sharepoint.administrationoperation.dll14.0.6126.5000834,22428-Aug-1218:28
Microsoft.sharepoint.applicationpages.administration.dll14.0.6108.5000608,12829-Aug-1113:52
Microsoft.sharepoint.applicationpages.dll14.0.6128.50001,063,60020-Sep-1210:33
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.dll14.0.6129.500016,845,40018-Oct-1223:31
Microsoft.sharepoint.dll14.0.6129.500016,845,40018-Oct-1223:31
Microsoft.sharepoint.dll14.900.6127.50001,796,74429-Aug-1215: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.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.dll14.0.6101.5000374,64029-Aug-1113:53
Microsoft.sharepoint.powershell.dll14.0.6124.5000649,84828-Aug-1218:28
Microsoft.sharepoint.powershell.intl.dll14.0.6108.500067,45629-Aug-1113:53
Microsoft.sharepoint.search.dll14.0.6126.50004,854,40828-Aug-1218:15
Microsoft.sharepoint.workflowactions.dll14.0.6124.5000318,08028-Aug-1218:29
Microsoft.sharepoint.workflows.dll14.0.6108.500071,55229-Aug-1113:55
Microsoft.web.commandui.dll14.0.6128.5000137,84820-Sep-128:40
Microsoft.web.commandui.dll14.0.6128.5000137,84820-Sep-128:40
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.6129.50002,923,66418-Oct-1223:29
Oisimg.dll14.0.6126.5000195,70428-Aug-1218:28
Oleparser.dll14.0.6126.500033,44028-Aug-1218:28
Onetnative.dll14.0.6123.5000584,8328-Jun-1212:17
Onetutil.dll14.0.6129.50002,987,10420-Oct-1212:51
Onfda.dll14.0.6129.50002,785,38419-Oct-121:02
Owssvr.dll14.0.6129.50006,629,48818-Oct-1223:29
Owstimer.exe14.0.6129.500074,84818-Oct-1223:29
Policy.12.0.microsoft.sharepoint.search.dll14.0.6107.500011,16829-Aug-1113:39
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
Spwriter.exe14.0.6126.500042,61628-Aug-1218:29
Stsadm.exe14.0.6128.5000355,00020-Sep-1210:33
Stssoap.dll14.0.6127.5000473,73629-Aug-1215:08
Stswel.dll14.0.6129.50003,260,01618-Oct-1223:29
Tquery.dll14.0.6126.50005,646,47228-Aug-1218:15
Wssadmin.exe14.0.6126.500016,55228-Aug-1218:28
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: 2687557 - Last Review: April 17, 2014 - Revision: 3.1
Applies to
  • Microsoft SharePoint Foundation 2010
Keywords: 
kbqfe kbsurveynew kbexpertiseinter kbhotfixserver kbhotfixrollup kbautohotfix KB2687557

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