This
article describes the Microsoft Windows SharePoint Services 3.0 issues that are
fixed in the Windows SharePoint Services 3.0 hotfix package that is dated
February 23, 2010.
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.
You upload a .dwt file to a document library. When you try
to open this file, you receive the following error message:
HTTP Error 403 – Forbidden
The Calendar Web part does not display events when you
visit the following month. This issue occurs when variations are used on
non-source labels.
You perform a prime export of a pending fold in a document
library that is approval enabled. In this case, you receive the following error
message:
Violation of PRIMARY KEY constraint
'PK__#ExportO__<Number>'. Cannot insert duplicate key in object
'dbo.#ExportObjects'.
When you delete a discussion item, you receive the
following error message:
Error Cannot complete this
action. Please try again.
For certain incoming e-mail messages, the Owstimer.exe
process increases CPU usage to 100%. Additionally, a very long time is required
to process these e-mail messages.
You use a discussion list in a List view Web part. Then,
you add the Reply field and you include an apostrophe in the subject line. In this
case, you cannot reply to threads.
Office SharePoint Designer e-mail actions do not specify
the name of the originating Web site as the display name for the sender of an
e-mail message.
You are no longer notified when a task is assigned to you.
This issue occurs when you set Read access to Only
their own.
Consider the following scenario. You create a feature that
includes a custom document-library-list template. Next, you use that feature in
a meeting workspace and you save the new document library as a template file
(.stp). Then, you try to re-create a new document library that is based on that
.stp file. In this scenario, the new document library is created. However,
there is no New Folder option. Therefore, you cannot create
folders in that document library.
You have Contribute permission for a sub folder. When you
click Actions for that subfolder, you are presented with the
View in Datasheet option. However, you expect to be presented
with the Edit in Datasheet option.
You add a new item to a list. When your display name
contains a semicolon (;), the warning e-mail message for the new item is not
sent.
Consider the following scenario. You have a custom site
template to which a custom feature is associated. Next, you create a site by
using this custom site template. The feature is enabled and performs a task.
Then, you use the stsadm -o createweb or the stsadm -o createsite command to create a site. In this scenario, the site is created
and that feature is enabled. However, the feature does not perform the
task.
Consider the following scenario. You use the rich text
editor feature in a Content Editor Web part to enter text into a Web part page.
This page contains a Contact field that uses the people picker
control. Then, you click OK to close the rich text Editor. In
this scenario, the Content Editor Web Part contains the text that you typed in
the rich text editor. However, you receive the following error message in the
Contact field:
You are only allowed to
enter one item.
After you export and import a site, not all Office
SharePoint groups are present in the imported site. Additionally, permissions
for the missing groups are also lost in the imported site.
Microsoft SQL Server generates bad query plans for the
proc_DirtyDependents stored procedure.
A .xls file contains double-byte character set (DBCS)
characters in the header or in the footer. In this case, the header strings,
footer strings, and certain numeric values are not indexed.
When all authenticated users are given access to a site
collection, all tenants in the data center can access this site
collection.
Cross-page connections between two Web Parts do not
redirect a page as expected after you apply Office SharePoint Server 2007
SP2.
When you remove and then re-add a content type to a list,
the content deployment fails. Additionally, you receive the following error
message:
A duplicate name "<Name>" was
found.
Consider the following scenario. You add a custom field to
a document library and then you set a custom field value for a document in that
library. Then, you click Send To to copy that document from
this document library to another document library that has the same custom
field and the same column name as the source library. In this scenario, the
values in the custom fields are not copied.
You use a custom alert handler. When many alerts are used,
a memory leak occurs in Owstimer.exe .
When a draft version (0.x) of a page is crawled in Office SharePoint Server 2007, subsequent incremental crawls ignore that page when it is published to a major version (1.x)
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-kb978389-fullfile-x86-glb.exe
12.0.6529.5000
19,130,424
06-Feb-2010
08:11
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,263,488
04-Feb-2010
20: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
