Description of the SharePoint Foundation 2010 hotfix package (Wss-x-none.msp): April 24, 2012

Applies to: Microsoft SharePoint Foundation 2010


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

A recent, isolated issue was discovered in the SharePoint 2010 Products April 2012 Cumulative Update that could result in an HTTP 500 error when users delete objects to include documents, lists, and Webs and a new object is created using the same path where the original object remains in the Recycle Bin. The following packages were affected:

KB2598151 - SharePoint Server Package
KB2598152 - Project Server Package
KB2598321 - SharePoint Foundation Package
KB2598304 – Wss-x-none.msp

This issue has been resolved in the revised packages. The revised packages include support for resolving issues related to the originally published updates.

Products Affected
SharePoint Foundation 2010
SharePoint Server 2010


Issues that this hotfix package fixes

  • Consider the following scenario:
    • You configure the Incoming Email feature in SharePoint Foundation 2010.
    • You configure a web application to use Claims Based Authentication.
    • You create a site collection in the web application.
    • You create an email distribution group for an existing SharePoint group, and the distribution group is also created in Active Directory Users and Computers.
    • You add a user to the SharePoint group.
    • You view the distribution group in Active Directory Users and Computers.
    In this scenario, the user whom you just added is not displayed in the Active Directory Users and Computers distribution group.
  • You select the Enable Asynchronous Update check box and the Show Manual Refresh Button check box in the AJAX Options settings for a document library. Then, you edit the properties of a document in the document library, and you save the changes. In this situation, SharePoint Foundation 2010 prompts you to open the document.
  • You create a document library that contains a folder structure and some columns in a SharePoint site. Then, you save the site as a site template. In this situation, you cannot create a new site by using the site template.
  • Consider the following scenario:
    • You add a custom column to a document library in Microsoft Windows SharePoint Services 3.0.
    • You upgrade Windows SharePoint Services 3.0 to SharePoint Foundation 2010.
    • You edit the properties of a document in the document library.
    In this scenario, you cannot save the changes to the custom column field in the document property.
  • Workflows that are included in a list template are not attached to new lists that are created from the template after Internet Information Services (IIS) is restarted.
  • When you try to sync certain lists from a SharePoint Foundation 2010 site to Microsoft SharePoint Workspace 2010, the sync operation fails. Additionally, you receive the following error message:
    Unable to parse SOAP response. XML Error: 0x-1072896684 'Duplicate attribute’.
  • Consider the following scenario:
    • You create a Links list in a SharePoint site.
    • You add some link items to the Links list.
    • You enable the <Summary view> for the list.
    • You enable the Group By feature for a column in the list.
    In this scenario, the first link item is missing in each group of links.
  • Consider the following scenario:
    • You enable the Versioning feature for a SharePoint site.
    • You use Microsoft Word to check in a document as a minor version.

      Note The document was formerly published as a major version in the SharePoint site.
    • Another user tries to check out the minor version of the document.
    In this scenario, the user is prompted that the document is locked.
  • Assume that you set a value for the NoCrawl property of a site column through the .xml codein a SharePoint site. When you save the site as a site template, an error occurs.
  • You cannot remove an existing entry from the People Picker control or add a new user entry to the People Picker control in a SharePoint site.
  • You cannot republish a content type through a hub site in which the Hidden attribute is set to TRUE.
  • Consider the following scenario:
    • You move a file from one document library to another document library in a SharePoint Foundation 2010 site collection.
    • A link on a webpage references the file in the site collection.
    • You perform an incremental deployment from the site collection to another site collection.
    • You click the link on the webpage that references the file in the site collection.
    In this scenario, you receive the following error message:
    HTTP 404 - File not found
  • When you use the Managed Metadata columns together with document sets in SharePoint Foundation 2010, you cannot perform a content deployment successfully. Additionally, you receive the following error message:
    FatalError: Specified data type does not match the current data type of the property.

  • Client applications are not used to open a .pdf file from a document library.
  • Assume that you import a site collection to another site collection as a subsite. When you change a list permission in the subsite, you cannot visit the site collection. Additionally, you receive the following error message:
    500 Internal Server Error
  • When you deploy a site collection that has several subsites, variation labels, and folders in a page library, you receive the following error message during the content database import process:
    FatalError: Attempted to use an object that has ceased to exist. (Exception from HRESULT: 0x80030102 (STG_E_REVERTED))

    Debug: at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)

    at Microsoft.SharePoint.Library.SPRequest.GetRoleDefsDataAsSafeArray(String bstrUrl, UInt32 dwRolesScope, Guid& pguidScopeId, UInt32& pdwRowCount, Object& pvarDataSet)

    at Microsoft.SharePoint.SPRoleDefinitionCollection.Init()

    at Microsoft.SharePoint.SPRoleDefinitionCollection.get_WebId()

    at Microsoft.SharePoint.Deployment.RolesImport..ctor(ImportStreamingContext context, SPSite site, SPWeb web, XmlReader xr, Int32 iBatchSize)

    at Microsoft.SharePoint.Deployment.SecurityObjectSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)

    at Microsoft.SharePoint.Deployment.XmlFormatter.CallSetObjectData(Object obj, SerializationInfo objectData, ISerializationSurrogate surrogate, ISurrogateSelector selector)

    at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObjectDirect(Object objParent, Type objectType)

    at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope)

    at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)

    at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)

    at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()

    at Microsoft.SharePoint.Deployment.SPImport.Run()
  • Assume that you deploy a custom workflow that contains an UpdateAllTasks activity to a SharePoint site. In this situation, the workflow is canceled, and you receive the following error message:
    An error has occurred.

    This occurs because of a save conflict if a user edits a task at the same time that the workflow executes the UpdateAllTasks activity.
  • A list that has the Incoming Email feature enabled does not create a list item for an incoming email message. This issue occurs when the site collection that contains the list reaches the site quota limitation.
  • Consider the following scenario:
    • You create an external content type in SharePoint Foundation 2010.
    • You upload a document that is not an Office document to a document library.
    • You associate the document with the external content type.
    • You move the document to another document library.
    In this scenario, the document’s external content type data is not copied to the other document library.
  • Assume that you have the Full Control permission on a folder in a document library. When you check in multiple documents in the document library, you receive the following error message:
    Access Denied
  • Consider the following scenario:
    • You create a category whose name contains Japanese characters in a SharePoint blog website.
    • You create some posts within the category that you created.
    • You click the category name to view the posts.
    In this scenario, the category name appears as a question mark (?) character.
  • Assume that the external data source is updated in an external database. When you use the refresh button to update a customer list that contains an external content type column, external data in list items that are stored in folders is not updated.
  • Consider the following scenario:
    • You create a root site, and then save the root site as a template in SharePoint Foundation 2010.
    • You use the template to create a subsite, and you enable the following settings on the "Set up Groups for this Site" page:
      • Visitors to this Site: Create a new group
      • Members of this Site: Create a new group
      • Owners of this Site: Create a new group
    • You use the template to create a subsite under the subsite, and you set the sub-subsite to inherit permissions from the subsite.
    In this scenario, the associated groups for the sub-subsite are created incorrectly.
  • After you delete a website, or you delete a list, or a folder from the Recycle Bin in SharePoint Foundation 2010, the content database size is not reduced as much as expected. Additionally, list item views do not return results as quickly as expected.
  • Consider the following scenario:
    • You paste HTML markup into the comments field of a publishing page in a SharePoint site.
    • You change the page order by using the Site Navigation Settings page in the SharePoint site.
    • You perform a content deployment from this site to another site.
    In this scenario, the content deployment fails, and you receive the following error message:
    Cannot complete this action.

  • A lookup field that allows for multiple values does not have a horizontal scrollbar, and long text is truncated.
  • The External Content Type Picker cannot recognize a content type name if the content type name shares common character strings with another content type name.
  • Assume that you enable the output caching feature on a SharePoint Foundation 2010 site. After you apply the hotfix package that is described in Knowledge Base (KB) article 2656351, the site is no longer output cached when an authenticated user visits the site.

    Note For more information about the hotfix package in KB article 2656351, click the following KB number:
    2656351 MS11-100: Description of the security update for the .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2: December 29, 2011
  • When an anonymous user visits a SharePoint site through an alternative access mapping URL, the user cannot receive search results from the site.
  • When you try to edit a Microsoft Word document in a SharePoint site through a web browser, you receive the following error message:
    Document cannot be opened for editing.

    Note This issue specifically occurs when multiple web applications are running in the same application pool.
  • You create a Gantt view for a custom list on a SharePoint site. Then, you run a workflow which is designed by using Microsoft SharePoint Designer on the list. When you open the Gantt view, an error occurs.
  • Changes on the Home.aspx page are not crawled through an incremental crawl in SharePoint Foundation 2010.
  • Assume that you have a list that contains more than 8 status options in the status lookup column. When you create a workflow association on the list, the workflow association cannot be changed.
  • Hyperlinks on a Web Part page are broken after you import the page to another SharePoint site.
  • Assume that you create a user account that has permissions to view items in a document library. You change user account name, and then you perform a search for items in the document library by using the user account. In this situation, no items are returned.
  • 2598293 No search results are returned when you perform a search after you change the name of the current user account in SharePoint Foundation 2010


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, visit the following Microsoft website: 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.


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

File nameFile versionFile sizeDateTime

Microsoft Windows Installer .msp file information

File nameFile versionFile sizeDateTime
Wss-x-none.mspNot Applicable36,145,1526-Jun-120:57

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.

Wss-x-none.msp information
File nameFile versionFile sizeDateTime


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