Description of the SharePoint Server 2010 hotfix package (sts-x-none.msp): April 26, 2011

Applies to: SharePoint Server 2010


This article describes the Microsoft SharePoint Server 2010 issues that are fixed in the SharePoint Server 2010 hotfix package that is dated April 26, 2011.


Issues that this hotfix package fixes

  • Consider the following scenario. You export a document library that has versioning enabled in Microsoft SharePoint Server 2010. During the export process, an import process initiates. Specifically, another user updates the file and creates a new version of the file. In this scenario, the import process fails. Additionally, you receive the following error message:

    FatalError: Member 'Versions' was not found.

  • The desktop page is displayed unexpectedly when you try to use Windows Phone 7 to open a document in a SharePoint Server 2010 site.
  • The creation process of an Excel Services Application  may stop responding during the content deployment process in SharePoint Server 2010.
  • Assume that you do not have access permissions to certain content databases in a SharePoint Server 2010 farm. When you perform a migration job that is based on all the content databases, the migration can complete. However, after the migration is complete, you are prompted that the migration fails.

    Note The fix for this issue will not be included in SharePoint Server 2010 Service Pack 1.
  • Consider the following scenario:
    • You set a notification alert for a list in SharePoint Server 2010.
    • The list contains a column that allows multiple values and managed metadata items.
    • You add more than one managed metadata item to the column in the list.

    In this scenario, the notification email message is not sent as expected.
  • Assume that a Forms Based Authentication (FBA) user’s security token expires in a SharePoint Foundation 2010 hosted environment. You try to authenticate the user by using the security token service. In this situation, an error page displays when the user tries to access a SharePoint Foundation 2010 page.
  • The Site Data web service returns incorrect .xml files in SharePoint Foundation 2010 when the internal name of a field in a list contains invalid XML characters.
  • Assume that you perform a content deployment job from a source site collection to a destination site collection in SharePoint Server 2010. The source site collection contains more than 100 groups. In this situation, the pager control does not display on the groups.aspx page of the destination site collection.
  • You try to use a People Picker that is configured to return only users in SharePoint Server 2010. However, the People Picker shows both users and groups.
  • Assume that you are a FBA user in SharePoint Server 2010. When your security token is refreshed in SharePoint Server 2010, the authentication cookie that is saved in your browser is not refreshed. In this situation, you have to relog on to the site that you are working on.

    Note The fix for this issue will not be included in SharePoint Server 2010 Service Pack 1.
  • Assume that a page’s URL switches from a HTTPS URL to a HTTP URL in SharePoint Server 2010. In this situation, you cannot use Office InfoPath 2007 to customize a list on the Form Settings page after.
  • The W3wp.exe crashes when you try to use a FBA user account to log on to a SharePoint Server 2010 site. Additionally, you receive the following error message:

    SPSecurityTokenService.Issue() failed: System.Runtime.InteropServices.COMException (0x80049217): The data to pack/unpack is not valid RPS data.   Internal error: Failed to call spDataCrypt->UnpackData. Data is too short..   

    at Microsoft.Passport.RPS.Native.IRPSTicket.ProcessToken(String siteName, String ticketToken)   

    at Microsoft.Passport.RPS.RPSTicket.ProcessToken(String siteName, String ticketToken)   

    at Microsoft.Online.SharePoint.IdentityModel.RpsMembershipProvider.ValidateUser(String username, String password)   

    at Microsoft.SharePoint.IdentityModel.SPFormsUserNameSecurityTokenHandler.ValidateToken(SecurityToken token)   

    at Microsoft.IdentityModel.Tokens.SecurityTokenElement.GetSubject()   

    at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.SPRequestInfo..ctor(IClaimsIdentity identity, RequestSecurityToken request, Boolean initializeForActor)   

    at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.SPRequestInfo..ctor(IClaimsPrincipal principal, RequestSecurityToken request)   

    at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.GetTokenLifetime(Lifetime requestLifetime)   

    at Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.Issue(IClaimsPrincipal principal, RequestSecurityToken request)   

    at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.Issue(IClaimsPrincipal principal, RequestSecurityToken request)

  • This hotfix adds the ConvertListTitleToEntitySetName method to convert SharePoint list names into corresponding entity set names in the listdata.svc data service in SharePoint Server 2010.


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: 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 Server 2010 installed.

Restart requirement

You do 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

Microsoft Windows Installer .msp file information

File nameFile versionFile sizeDateTime
Sts-x-none.mspNot Applicable29,222,40024-Mar-119:00

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:

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