Summary
This article describes the Microsoft SharePoint Foundation 2010 issues that are fixed in the SharePoint Foundation 2010 that is dated August 31, 2010.
INTRODUCTION
Issues that this hotfix package fixes
-
When you click Sign In as Different User to sign in by using new user credentials, you cannot access the expected resource.
-
You cannot create a recurring calendar entry on a site that is created from a custom template.
-
This fix adds a new health rule. This rule can inform an administrator whether the Business Connectivity Service (BCS) connectors are enabled or disabled in Microsoft SharePoint 2010. Therefore, the administrator can monitor the status of the BCS connectors.
-
You add a large amount of content to a client notebook on a Microsoft SharePoint Foundation 2010 server that is under heavy load. After some time, the notebook is no longer synchronous with the server and you cannot save changes to the server. Additionally, you may receive the following error message:
Unable to save
-
Anonymous users cannot use Language Integrated Query (LINQ) to query data in Microsoft SharePoint Foundation 2010. Additionally, the anonymous users are prompted for user credentials when they use LINQ to query data.
-
Consider the following scenario. You change the site level permission on a Microsoft SharePoint Foundation 2010 site. Then, you change some property of the site. In this scenario, the sitedata.asmx.GetChanges() web service method does not report the security change.
-
The external content type name appears in the external list edit form if the optional field value is not present. Therefore, you cannot save the external list item successfully.
-
The CopyIntoItems method in the Copy.asmx web servicedoes not assign the custom content type when you upload a file from the file system. Instead, it always assigns the default content type.
-
When you click the Open this Task button in Microsoft Outlook, you cannot open the workflow task form from the notification email in Microsoft Outlook.
-
Consider the following scenario. In Microsoft SharePoint Designer, you apply Extensible Stylesheet Language (XSL) to a view that contains a link field. Then, you add a Universal Name Convention (UNC) link that contains non-ASCII characters to the field. In this scenario, the link is broken when you open it.
-
In the Turkish version of Microsoft SharePoint Server 2010, you click the Help icon and you try to use the search function. However, the search function does not work.
-
When you delete old versions of documents that contain web parts, spaces for the old versions in Microsoft SQL Server are not reclaimed.
-
When you upload a picture in the CMYK pixel format to an asset library, the upload is completed successfully and you see a thumbnail in the asset library. However, when you hover the mouse pointer over the thumbnail, the preview window does not show the picture in Windows Internet Explorer.
-
In sandbox solutions, Partially Trusted Code (PTC) usage decreases when the number of max processes per application server increases.
-
When you save a team site as a template, the web part that is used in the original site does not carry the correct view to the newly created site.
-
This fix adds support for both HTTP-based host-named site collections and HTTPS-based host-named site collections to coexist in the same web application. By default this support is disabled. To enable this support, set the
Microsoft.SharePoint.Administration.SPWebService.ContentService.EnableHostHeaderSiteBasedSchemeSelection property to true. As soon as it is enabled, SharePoint will no longer use the web application's default zone public URL protocol scheme for all host-named site collections in that web application. Instead, SharePoint will use the protocol scheme provided during host-named site collection creation, restoration, or rename. Host-named site collections that are created before this update is installed will default to use the HTTP protocol scheme if this property is set to true. These site collections can be switched to use the HTTPS protocol scheme by renaming the host-named site collection and providing an HTTPS-based URL as the new site collection URL. -
Consider the following scenario. You delete a picture library item. Then, you restore the item from the Recycle Bin and then delete the item again. In this scenario, you receive the following error message:
Violation of PRIMARY KEY constraint '<KeyName>'. Cannot insert duplicate key in object '<ObjectName>'. The statement has been terminated.
-
This fix improves the performance of migration time for users across all sites.
More Information
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:http://support.microsoft.com/contactus/?ws=supportNote 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 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 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 correct 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 name |
File version |
File size |
Date |
Time |
Platform |
Spf-kb2266423-fullfile-x64-glb.exe |
14.0.5123.5000 |
20,285,536 |
13-Aug-2010 |
11:00 |
x86 |
Microsoft Windows Installer .msp file information
File name |
File version |
File size |
Date |
Time |
Platform |
Sts-x-none.msp |
Not Applicable |
20,525,056 |
12-Aug-2010 |
22:40 |
Not Applicable |
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 name |
File version |
File size |
Date |
Time |
Platform |
Microsoft.sharepoint.administrationoperation.dll |
14.0.5123.5000 |
829,352 |
10-Aug-2010 |
4:16 |
Not Applicable |
Microsoft.sharepoint.dll |
14.0.5123.5000 |
16,557,912 |
10-Aug-2010 |
4:16 |
Not Applicable |
Microsoft.sharepoint.dll |
14.0.5123.5000 |
16,557,912 |
10-Aug-2010 |
4:16 |
x86 |
Microsoft.sharepoint.dll |
14.900.5123.5000 |
1,791,856 |
10-Aug-2010 |
4:16 |
Not Applicable |
Microsoft.sharepoint.health.dll |
14.0.5120.5000 |
96,176 |
20-Jul-2010 |
9:59 |
x86 |
Microsoft.sharepoint.identitymodel.dll |
14.0.5123.5000 |
96,112 |
10-Aug-2010 |
4:16 |
x86 |
Microsoft.sharepoint.intl.dll |
14.0.5123.5000 |
1,009,520 |
10-Aug-2010 |
4:16 |
x86 |
Microsoft.sharepoint.library.dll |
14.0.5120.5000 |
165,760 |
20-Jul-2010 |
9:59 |
Not Applicable |
Microsoft.sharepoint.linq.dll |
14.0.5123.5000 |
374,624 |
10-Aug-2010 |
4:16 |
x86 |
Microsoft.sharepoint.search.dll |
14.0.5123.5000 |
4,793,728 |
10-Aug-2010 |
4:44 |
Not Applicable |
Microsoft.sharepoint.usercode.dll |
14.0.5123.5000 |
34,672 |
10-Aug-2010 |
4:16 |
Not Applicable |
Mssdmn.exe |
14.0.5120.5000 |
780,168 |
20-Jul-2010 |
10:24 |
Not Applicable |
Mssph.dll |
14.0.5123.5000 |
1,675,136 |
10-Aug-2010 |
4:36 |
Not Applicable |
Mssrch.dll |
14.0.5120.5000 |
4,988,808 |
20-Jul-2010 |
10:24 |
Not Applicable |
Oisimg.dll |
14.0.5123.5000 |
194,928 |
10-Aug-2010 |
4:15 |
x64 |
Oleparser.dll |
14.0.5123.5000 |
32,664 |
10-Aug-2010 |
4:15 |
x64 |
Onetutil.dll |
14.0.5123.5000 |
2,980,216 |
12-Aug-2010 |
13:45 |
x64 |
Owssvr.dll |
14.0.5123.5000 |
6,553,456 |
10-Aug-2010 |
4:15 |
Not Applicable |
Owstimer.exe |
14.0.5123.5000 |
74,080 |
10-Aug-2010 |
4:15 |
Not Applicable |
Spuchostservice.exe |
14.0.5123.5000 |
100,288 |
10-Aug-2010 |
4:16 |
x86 |
Spucworkerprocess.exe |
14.0.5123.5000 |
47,048 |
10-Aug-2010 |
4:16 |
x86 |
Spucworkerprocessproxy.exe |
14.0.5123.5000 |
124,880 |
10-Aug-2010 |
4:16 |
x86 |
Spwriter.exe |
14.0.5123.5000 |
41,840 |
10-Aug-2010 |
4:15 |
Not Applicable |
Stssoap.dll |
14.0.5123.5000 |
468,848 |
10-Aug-2010 |
4:16 |
x86 |
Stswel.dll |
14.0.5123.5000 |
3,238,256 |
10-Aug-2010 |
4:15 |
x64 |
Wssadmin.exe |
14.0.5123.5000 |
15,776 |
10-Aug-2010 |
4:16 |
Not Applicable |
References
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