This article describes the Windows SharePoint Services
3.0 issues that are fixed in the Windows SharePoint Services 3.0
hotfix package that is dated October 27, 2009.
You use a tool that calls the GetChanges() method in a loop in order to obtain a list of changes from a Windows SharePoint Services (WSS) 3.0 site. You notice that this tool takes a long time to obtain changes from the WSS 3.0 site.
You use the Check Names feature in Windows SharePoint Service (WSS) 3.0.The feature resolves names very slowly. This issue occurs when WSS 3.0 checks names from NT4.0 domains.
In a Discussion list, you delete a list item. The attachment that is related to the list item is not deleted in the back-end database.
When the Content Approval feature is enabled, only users who can approve items can receive alerts for minor version documents. After you apply this update, users who can also read items can receive alerts for minor version documents.
Note Draft Item Security determines whether users can read items or approve items.
You use the Content Deployment feature to transfer a site collection to another target. You cannot create new sites on the site collection after you transfer it. This issue occurs because the variation system does not propagate pages correctly. This issue also occurs because the wrong Content Types are used.
You perform the incremental deployment in the French version of Microsoft Office SharePoint Server 2007.When you perform the incremental deployment, the user information list has columns that are duplicated.
You propagate a Web page by using variation systems. The SPListItem.ForwardLinks property is not updated until the page is published in the target variation sites.
You have a sub-site that contains a lookup column that refers to a list in the root Web site. When you do an incremental content deployment, the deployment succeeds. However, you receive a warning message:
Unable to find a lookup list /sites/PublishingSite/RootDocLib. The list is not part of the exported package and does not exist in the destination site collection.
The lookup column is not deployed and the value for the column is not set. Additionally, the lookup value list is empty.
The SharePoint domain has a trust relationship with a remote domain. A user in the remote domain can access a Microsoft Office SharePoint Services (MOSS) site by using a domain local security group. A profile is created for the user at the site collection level. Then, the profile is stored in the UserInfo table that is in the content database. Information about user access is stored in the tp_ExternalToken column of the database table.
When the tp_ExternalToken column is updated by the timer job incorrectly, alerts are not sent. Additionally, the alerts would be security trimmed.
When you try to restore a site collection that contains content whose URL path length will be longer than 260 characters, the restoration fails. Additionally, you receive the following error message:
One or more files in the restored site collection will exceed the maximum supported path length. Please select a shorter destination site address and try again.
After you install this update, restoration will complete if your site URL path length is less than or equal to the original site URL path length. However, you will only be able to access content in the restored site that is within the maximum supported path length of 260 characters.
You use the –includeusersecurity option to import a site from a .cab file to a SharePoint site. Then, you see a list of deleted users when you click All People in the SharePoint site. However, you do not expect to see this list.
The following is a sample code that uses the –includeusersecurity option to import a site from a .cab file:
When you click X more items in a SharePoint calendar, the calendar view does not display all the items that it contains.
You create an ASPX page and then add a Dataformwebpart Web part in SharePoint Designer. When you try to delete the list items that have contributor rights in the Web part, you receive an "Access Denied" error. However, the list items are deleted.
When you upload oversized files to a Discussion Board, you receive the following error message:
One or more attachment file is over sized…
Additionally, five discussion topic items are duplicated.
You experience the performance regression that was detected in the 2009 August cumulative update (CU).
You open a UNC-based Web folder in an attachment folder of an Issue Tracking list item. When you drag a file attachment to the attachment folder, four duplicate comments are created for each item that is added.
You experience slow performance when you access a pages library that is deployed through the Content Deployment feature.
In a list, you have a folder that is based on a customer folder content type. The customer folder has a multiple value lookup column. When you rename the folder, the multiple value lookup values are lost.
You create a custom field that derives from the SPFieldLookup class. You add this field to a document library and then enable the field to have multiple values. After you add some values to the column, you run the Content Deployment feature. None of the values for the custom field is transferred successfully to the target farm.
When you run a SharePoint site in a .Net Framework 4.0 process, the site causes .Net Framework 4.0 assembly references to be written to the SharePoint configuration database. Then, you experience failures when you run the SharePoint site in the .Net Framework 2.0.This issue occurs because the .Net Framework 2.0 cannot resolve assembly references in the .Net Framework 4.0.
Note The .Net Framework 4.0 release is planned for March 2010.
You create a data view Web part that uses SQL databases as a data source. When you try to enable the filtering functionality and the sorting functionality, the Web part generates drop-down menus. However, the Web part does not filter or sort.
This issue does not occur when you use SharePoint Lists or SharePoint Library as data sources.
You upload files to a SharePoint site and mark them as "allow everyone to read." "Everyone" is defined as "all authenticated users."For multiple sites that share the same host, such as SharePoint Online, users from one site (Site A) are "authenticated users" on another site (Site B). Therefore, certain files from Site B are visible to users from Site A.
You input values in a page and then submit the page. When information for a mandatory field is missing, you receive the following validation error message:
You must specify a value for this required field.
Then, the lookup column does not keep the values that were changed during the editing process.
You have a multiple value lookup column. You also have a column that contains values that are calculated from another text column. If you use the multiple value lookup column and the calculated column together, you cannot open the Version History page. The Version History page fails, and you receive an unknown error.
Before you install a Microsoft Office SharePoint Server 2007 update, you detach the content databases and then install the 2009 August CU for the 2007 Microsoft Office system. When you try to reattach the databases, you receive the following error message:
Index was outside the bounds of the array
After you install this update, reporting rules for the pre-upgrade checker utility will be updated.
The Windows SharePoint Services Search service does not start when the fully qualified domain names of the server are used to configure a Windows SharePoint Services 3.0 single server installation
When you click "Search" without specifying search words in the Advanced Search page of a Windows SharePoint Services 3.0 site, you receive all the results from the index
When you use the GetListItems method of the Lists.asmx Web service to obtain all the occurrences of a recurring event in a Windows SharePoint Services 3.0 calendar list, only one item is returned
Users who have read permission do not receive alerts for drafts or for minor version documents when the Content Approval option is enabled in a Windows SharePoint Services 3.0 site
A supported hotfix is available from Microsoft. However, this hotfix is
intended to correct only the problems that are described in this article. Apply
this hotfix only to systems that are experiencing the problems 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.
Prerequisites
To install this hotfix, you must have Windows SharePoint Services
3.0 Service Pack 2 or Windows SharePoint Services
3.0 Service Pack 1 installed.
For more information,
click the following article number to view the article in the Microsoft
Knowledge Base:
How to obtain the latest service
pack for Windows SharePoint Services 3.0
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 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.
x86
Download information
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Wss-kb975002-fullfile-x86-glb.exe
12.0.6520.5000
19,040,232
17-Oct-2009
14:57
x86
Microsoft Windows Installer .msp file information
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Sts-x-none.msp
Not Applicable
19,162,624
16-Oct-2009
23:47
Not Applicable
After the hotfix is installed, the global version of
this hotfix will have the file attributes, or a later version of the file attributes,
that are listed in the following table:
After the hotfix is installed, the global version of
this hotfix will have the file attributes, or a later version of the file attributes,
that are listed in the following table:
Back to the top
