jeudi 2 septembre 2010

The first cumulative update for SPF2010 and SharePoint 2010


Microsoft SharePoint Foundation 2010:

Issues that this hotfix package fixes
  • Consider the following scenario:
    • You define a big sandboxed solution that contains some list templates.
    • You define a web template that uses the list templates.
    • You enable this sandboxed solution and create a webpage by using the web template.
    In this scenario, memory of the size of the sandboxed solution is leaked for each list that is created. Therefore, the W3wp.exe process very quickly stops responding.
  • On a computer that has in Microsoft SharePoint Designer 2010 installed, the memory usage increases together with the caching of certain objects linearly.
  • After you upgrade a content database, the search engine crawls everything in that web application again.
  • When you click Check Permissions for a security group, you receive the following error message if the Claims authentication is configured:

    System.InvalidOperationException: Operation is not valid due to the current state of the object. at Microsoft.SharePoint.SPUserToken.GetClaimsUserLoginName()

  • Consider the following scenario:
    • You set SPField to Hidden at the content type level.
    • You move an item between folders in the same list. This item is associated with a content type.
    In this scenario, the associated SPField properties are imported at the list level instead of the content type level during the Content Migration API (also known as PRIME) import phase.
  • The variation system does not remove the web part from target sites when the last web part is removed from the source page.
  • An incremental content deployment fails if websites are moved to a new location and if the earlier parent site is deleted.
  • An incorrect order of the data in the proc_DeplGetListItemVersionsFields stored procedure causes data loss for versions such as list item versions during export, import, or content deployment.
  • The Microsoft Office SharePoint Server administrators notice that the worker processes fail after a user performs an authoring operation. Additionally, the in-process requests are lost, and the integrity of the worker processes is potentially compromised for all the users of that web application.
  • You cannot connect to a site through the Outlook Social Connector or another Windows-based client if the website uses the Windows-based Claims authentication.
  • The user name that is visible and the internal unique identifier do not match if you use a SharePoint Foundation 2010-based Claims authentication. For example, LiveID deployments must use a user principal name (UPN) for the logon name and use a Unique ID (PUID) as the unique identifier for some Personally Identifiable Information (PII) reasons.
  • A folder content type loses a column in a website that is created from a customized website template.
  • If a list item or a document library item has both approved and draft versions, the search crawl query cannot find the item. Therefore, the query builder cannot return the item. For example, a document has an approved checked-in version. However, the document cannot be searched if the document is checked out or if the document is pending approval.

Description of the SharePoint Server 2010 hotfix package (Osrchwfe-x-none.msp;Pplwfe-x-none.msp;Spswfe-x-none.msp): June 29, 2010

Microsoft SharePoint Server 2010:;EN-US;983497
Issues that this hotfix package fixes
  • After you move a site to a new content database, the Microsoft SharePoint Foundation 2010 sync does not work on that site.
  • If you change your information, a Microsoft SharePoint Server 2010 site still displays your old information after you log on to that site.
  • The Welcome Name field is not synced with a user profile as expected if the user obtains access to a site through an Active Directory group. This issue occurs even if the administrator uses the synchronization job to sync profile details for inactive site users.
  • If a user profile synchronization service uses a named SQL instance, the service no longer starts after you provision the service. For example, this issue ocurrs when you stop the service.
  • You cannot obtain most activity properties from the ActivityManager object without obtaining the LinkList property first.
  • When you add a Windows user to SharePoint Server 2010, the user's properties are not populated from Active Directory. Additionally, the user name is the logon name.
  • When a SharePoint Server 2010 farm administrator runs the User Profile Change Cleanup job, the performance of the SQL server that hosts the profile database is poor.
  • Profile import is slow when a group is deleted. Additionally, the deletion can take hours in some cases. If the group deletion is completed in a transaction, many other database requests are also blocked.
  • If all members are removed from a group but the group itself is not deleted, the memberships are not removed.
  • When you create a Business Data Catalog (BDC) sync connection, you receive the following error message:

    An error has occurred while accessing the SQL Server database or the SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.

  • When you run a BDC import, the import data file is created by running queries on the SharePoint Server 2010 profile store and the BDC back-end store. If an error or exception occurs, all the data is lost.
  • If a customer's Lightweight Directory Access Protocol (LDAP) server does not respond within 30 seconds, there is no way for the administrator to create a profile import connection.
  • If there are more than 1,000 tag events or rating events during a gatherer run, only the first 1,000 events are processed.
  • You clear an activity that you follow in your edit profile screen. However, this action cannot be undone.
  • The "people search" result relevance is poor for organization type queries.
  • If there are more than 1,000 events during a gatherer run and these events do not fall under certain criteria, only the first 1,000 events are processed correctly. Duplicate events may be generated for the rest of the events.
  • When a taxonomy service has a large change log, an offline term store that has never been online cannot recover itself online.
  • 2201116 ( ) A deadlock occurs in SQL Server when you import many users and groups in Office SharePoint Server 2010

After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.

Aucun commentaire: