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 February 24,
2009.
This article describes the following items about the hotfix package:
The issues that the hotfix package fixes.
The prerequisites for installing the hotfix
package.
Whether you must restart the computer after you install
the hotfix package.
Whether the hotfix package is replaced by any other
hotfix packages.
When you decline a recurring meeting request from the
meeting workspace, the e-mail message that is sent by the SharePoint server is
not recognized by Microsoft Office Outlook 2007 as a meeting declination.
Therefore, Outlook does not update the meeting attendee status to
"Declined."
You migrate discussion boards from Windows SharePoint
Services 2.0 to Windows SharePoint Services 3.0. Discussion boards work fine
after that. However, if you export and import a discussion board into another
Windows SharePoint Services 3.0 site, the thread relationship is broken, and
all entries appear in one list.
Content deployment target site permissions that are not
inherited can be removed.
The entries for e-mail-enabled lists are being deleted from
the EmailEnabledLists table in the configuration database. When this issue
occurs, incoming e-mail messages for these lists are not delivered. Therefore,
the e-mail messages are deleted, and errors are logged for "Unkown
alias."
If you have a list that has more than 500 unique scope IDs
and if the Content Approval option is enabled, duplicated items may appear in
the default view of this list.
In a Windows SharePoint Services 3.0 site, alerts for All
day Calendar events do not show the correct start and end time in alert e-mail
messages.
When you try to modify group membership of the built-in
groups of site collections, you may receive a
"System.UnauthorizedAccessException" exception. For example, this issue may
occur when you try to add a new user to a built-in group. Built-in groups
include visitors, owners, members, and so on.
If you use the SharePoint Content Migration API to export
large sites, the performance is poor.
You create a new page in the source variation by using a
customized page layout that has calculated columns. However, when you try to
allow the variation engine to propagate the new page to the other variation
label Web sites, it fails.
When you move through a specific blog category page, you
cannot move to the Next page of blog entries. By default, the
paging is set to 10 items per page. However, when you move to the next page in
a category, a "There are no posts in this category" message is displayed. This
message is incorrect. Paging in the All Posts area works as
expected.
Before an incremental content deployment, you activate and then deactivate
the feature that creates content types on both the source site and the
destination site. During the incremental deployment, the content type delete
operation fails, and the content deployment stops with an error message.
All meetings that you view under a meeting workspace
display folder numbers instead of document names.
You create a versioned page, and you create a major version
and a minor version. When you delete the versioned page and try to export the
document library, it fails.
If you have an orphan site collection, the XML produced by
the stsadm -o enumsites command is not well formed, as shown in the following example.
The last tag is missing an "s." It should be </Sites>. Also, the
<site Error …> tag is not correctly closed.
After you install update 957691, you cannot set a user type
column from the workflow when you create a new list item.
If you programmatically run the SPListItem.SystemUpdate(bool) method on a document library, the latest check-in comment will be
removed.
If you add a Site Columns choice type that has a slash (/)
in the column name to a document library, you cannot change the value of it on
a SharePoint site. However, you can change the value by opening the document in
Microsoft Word, editing the property, and saving it back to the document
library.
When you build an application to control a document
library, the SPFolder.CopyTo() method does not increase the List.ItemCount number, this will
cause inconsistency in the list.
The Microsoft PKM Search Filter Daemon (Mssdmn.exe) crashes
every 15 seconds when crawled using certificate authentication.
When you try to back up the Shared Search index, it always
fails, and you receive the following error message in the backup log:
[30/9/2008 2:11:46]: Verbose: Starting object: Shared
Search Index. [30/9/2008 3:12:17]: Error: Object Shared Search Index failed in
event OnBackupComplete. For more information, see the error log located in the
backup directory. WebException: The current operation timed-out after 3600
seconds [30/9/2008 3:12:17]: Debug: at
Microsoft.Office.Server.Search.Administration.CatalogPauseTimeout.WaitAndThrowIfTimeout()
at
Microsoft.Office.Server.Search.Administration.SearchApi.CatalogResumeCrawl(GathererPauseReason
reason) at
Microsoft.Office.Server.Search.Administration.SearchSharedApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnBackupComplete(Object
sender, SPBackupInformation args) [30/9/2008 3:12:17]: Verbose: Starting
object: SharedServices_Default_Search.
When you search on a SharePoint site, the performance may
sometimes be slow.
Search results are not security trimmed for anonymous users
who access the sites that have the lockdown feature activated.
After you set the Enable RSS Feeds option to No on the Web Application General Settings page in SharePoint Portal Server Central Administration, the search result pages still show the RSS icon
You cannot limit the People Picker on the site-collection level to find only users in a specific organization unit (OU) in a trusted domain in a SharePoint site
When you crawl file shares that are accessed through a domain-based Distributed File System (DFS) in SharePoint Server 2007, you experience poor performance
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 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-kb961750-fullfile-x86-glb.exe
12.0.6341.5000
23,425,496
17-Feb-2009
20:37
x86
Microsoft Windows Installer .msp file information
Collapse this tableExpand this table
File name
File version
File
size
Date
Time
Platform
Sts.msp
Not
Applicable
23,659,008
14-Feb-2009
22:12
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:
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:
Back to the top
