Si vous êtes un client Small Business, découvrez des ressources de formation et de résolution de problèmes supplémentaires sur le site de Support pour Small Business.
This article describes the Microsoft SharePoint Foundation 2010 issues that are fixed in the SharePoint Foundation 2010 hotfix package that is dated October 25, 2011.
You create a List view that groups the results from a DateTime field in a SharePoint Foundation 2010 list.
You configure the number of groups that are displayed per page in the List view.
You specify a batch size limit for items that are displayed per page in the List view.
You use the new List view to view the items in the SharePoint Foundation 2010 list.
In this scenario, the settings for the number of groups and the batch size limit are not applied to the new List view.
Consider the following scenario:
You perform a content deployment from a source site collection to a destination site collection in SharePoint Foundation 2010.
You rename a webpage on the source site collection.
You use the name of the old webpage to create a new webpage.
You delete the renamed webpage.
You perform a content deployment from the source site collection to the destination site collection again.
In this scenario, an error occurs. Additionally, the webpage that you create in the source site collection disappears from the destination site collection.
Consider the following scenario:
You create a feature that can deploy a content type on a site collection in SharePoint Foundation 2010.
You deploy the feature on a SharePoint farm.
You create a site collection on the farm.
You enable the feature on the site collection.
In this scenario, an exception is logged in the Unified Logging Service (ULS) log.
When you click the Help icon to view the help content on a French version of a SharePoint Foundation 2010 site collection, you receive an error message.
Assume that there are two web parts on a SharePoint Foundation 2010 webpage. One web part has an invalid XSL template and the other one has a valid XSL template. In this situation, the web part that has the invalid XSL template uses the cached valid XSL template on the page.
Many proc_SecRefreshToken stored procedures are invoked to update the UserInfo table on an Internet-facing SharePoint Foundation 2010 site. However, most of the updates are not needed. In this situation, the SharePoint server experiences a decrease in performance.
Consider the following scenario:
You create an image library that has the Create major versions setting enabled in SharePoint Foundation 2010.
You enable the check-out feature for the image library.
You upload an image and then use the check-in feature to check the image into the image library.
Another user tries to view the image in the image library.
In this scenario, the thumbnail and the image preview are not displayed.
The incremental content deployment job fails when you delete a site collection that contains sub-sites in SharePoint Foundation 2010.
Consider the following scenario:
You install more than 28 language packs on a SharePoint Foundation 2010 server.
You create a custom list that contains multiple Managed Metadata columns.
You create a term set that contains some managed metadata terms for the Managed Metadata columns.
You view the custom list.
In this scenario, the managed metadata terms are not displayed correctly.
You cannot create a custom forms login page for SharePoint Foundation 2010.
Assume that you paste a bulleted list into a list column in SharePoint Foundation 2010. In this situation, the indentations between the bullets are lost.
Assume that you use custom code to call the Lists.GetList method in SharePoint Foundation 2010. In this situation, the last item modified attribute and the last item deleted attribute are formatted incorrectly in the XML file that the Lists.GetList method returns.
The Group By function in a view does not work in SharePoint Foundation 2010 after you apply the hotfix package that is described in Microsoft Knowledge Base (KB) article 2459108.
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.
Prerequisites
To install this hotfix, you must have Microsoft SharePoint Foundation 2010 or Microsoft 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.
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. Sts-x-none.msp information
