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.
Description of the SharePoint Server 2010 hotfix package (wosrv-x-none.msp, pplwfe-x-none.msp, osrv-x-none.msp): July 21, 2010
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 Web site:
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
not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released
To use one of the hotfixes in
this package, you do not have to make any changes to the
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 correct
the issues that are listed in this article.
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.
Collapse this tableExpand this table
Microsoft Windows Installer .msp file information
Collapse this tableExpand this table
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: Osrchwfe-x-none.msp