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 28,
2008.
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.
958008
(http://support.microsoft.com/kb/958008/
)
Security trimming is not honored when more than one List View Web Part is displayed on the same page in a Windows SharePoint Services 3.0 site
958577
(http://support.microsoft.com/kb/958577/
)
Error message when you visit a sub-folder under a Windows SharePoint Services 3.0 list that contains more than 2,000 list items that have non-inheriting permissions: "#RENDER FAILED"
958578
(http://support.microsoft.com/kb/958578/
)
The "Check Names" button does not work as expected after you set a "Peoplepicker-searchadcustomfilter" LDAP filter in a Windows SharePoint Services 3.0 site
958579
(http://support.microsoft.com/kb/958579/
)
Error message when you perform a content deployment of a Windows SharePoint Services 3.0 site collection that has a custom site template: "Cannot import site"
958615
(http://support.microsoft.com/kb/958615/
)
The index is corrupted when the SharePoint Server 2007 index server experiences power failure or restarts unexpectedly
This hotfix fixes the
following issues that are not previously documented in a Microsoft Knowledge
Base article:
In a WSS 3.0 document library, you cannot use the filter
for columns after you set unique permissions on over 1,000 items.
You install the update that is described in the following
Microsoft Knowledge Base article:
937203
(http://support.microsoft.com/kb/937203/
)
Description of the Windows SharePoint Services 3.0 hotfix package: May 15, 2007
You create a blog site, and then you create a post
in the site. When you click Comments, you find that there is
no control that you can use to edit the comment.
In Windows SharePoint Services (WSS) 3.0, you send e-mail
messages that have attachments (especially Microsoft Office Word documents)
from Macintosh clients to a mail-enabled discussion board. When you do this,
attachments that have the multipart/appledouble MIME type are discarded. The resulting message in the discussion
board has no attachment.
When an e-mail message is sent to a WSS 3.0 document
library from certain applications, the file name extension of the e-mail file
is unavailable.
After you install the infrastructure update, you cannot use
the stsadm -o export/import command to transfer published sites to other site collections.
Microsoft Office SharePoint Server 2007 32-bit servers are
susceptible to application pool memory issues. When these issues occur, the
servers become unstable and inaccessible.
You migrate a Web application from SharePoint Portal Server
2003 to Microsoft Office SharePoint Server 2007. After the migration, you
cannot view or edit a list that includes a calendar item. This issue occurs
when the calendar item has lots of reoccurring tasks.
If you create a site from a saved template, you may be
unable to check in a document when the name of a required custom column
contains non-ASCII characters.
Generally, when a file is sent from one document library to
another, all the columns in the source document library will be copied to the
destination document library. However, a "Person or Group" column that has the
"Allow multiple selections" option will not be copied.
You create many columns for a list to use. This causes more
than one row ordinal to be generated. If one of the columns is a Multiple Value
Lookup (MVL) column, old values for MVL are duplicated in alert e-mail
messages.
The BreakRoleInheritance function takes over four seconds to execute in a large list that
contains more than 1 million top-level folders.
If folders in a document library have very similar names
that contain the same prefix, incorrect e-mail alerts can be sent to users who
have e-mail alert subscriptions. For example, the folder names may be
A Test Folder I and A Test Folder
II.
When the size of the EventCache table becomes very large,
SharePoint may stop responding. Therefore, you must have support methods to
clear the old entries in the EventCache table.
Consider the following scenario. There are more than 1,000
individual permission scopes in a list. A user has "Contributor" permissions to
a sub folder. However, the user has no permissions in the "List" level. When
the user opens the subfolder, the New menu and the
Upload menu will not be rendered. Therefore, the user cannot
create or upload files to the folder.
When you try to add a Domain Local Group to a Farm
Administration Group, you receive an error message that resembles the
following:
'DomainName\AccountName' is not a valid
account for the Farm Administrators Group. Accounts for the Farm Administrators
Group must be valid and cannot be a local machine group.
When you try to upload a document that already exists, and
you do not click to select the Add as a new version to existing
files option, you may receive an error message that resembles the
following:
A file with the name
<filename> already exists. It was last
modified by domain\user on
<DateTime>.
The issue is that you
may find the <DateTime> on the error page is
in Universal Time Coordinated (UTC), not in local time.
After you rename a folder in a document library, if you
expand the folder tree, the subfolders disappear from the tree view.
One user uploads a document and adds some comments. Then, a
second user clicks Edit Properties to add some text to the
title of the document. In this case, the document history shows the
modification and the versions correctly. However, the comments of the first
user were added to the second user's comments field.
After you install the following security update, the
"Welcome" e-mail messages contain an invalid hyperlink:
934525
(http://support.microsoft.com/kb/934525/
)
Description of the security update for Windows SharePoint Services 3.0: October 9, 2007
This hyperlink is to the relative URL of the home
page of the SharePoint site.
Consider the following scenario:
User 1 uploads a document.
User 2 updates the document by using Microsoft Office
Word.
User 3 opens the Document Properties
dialog box in WSS 3.0 and then changes the name of the document.
In this scenario, the version history shows that user 3
used Word to make the modification..
Consider the following scenario. You have a publishing site
that has multiple variation labels. The Web application is extended to a second
Web application in the Internet zone. Users in the different zones can create
content in the site.
If the site is now deployed to a different
server by using content deployment, all the pages that are created from the
Internet zone receive an incorrect page layout URL. This issue leads to
problems with copy operations on the target server and sometimes to "file not
found" errors when you browse the site.
If you use IAlertNotifyHandler to customize alerts, the SPAlertHandlerParams object contains incorrect data. For more information, visit
the following Microsoft Web site:
When one of the computers that are running SQL Server is
being referenced by using an alias, WSS writer reports the virtual name and not
the physical name.
SharePoint workflow notification e-mail messages do not use
locale date and time formats.
If you visit a SharePoint site by using a URL that has an
invalid character during an application pool recycle or during startup, the
safe mode may not be initialized correctly in the application pool state for
WSS. The SharePoint site cannot be browsed until the next application pool
recycle or Internet Information Services is reset. The event viewer shows the
following error message:
Event Type: Error
Event Source: Windows SharePoint Services 3 Event Category: (1734) Event ID:
6614 Date: 4/15/2008 Time: 5:14:38 PM User: N/A Computer: SERVERNAME
Description: Safe mode did not start successfully. Illegal characters in path.
Even when Information Rights Management (IRM) is enabled on
a document library, old versions of documents are not protected.
When you browse the Site Collection Administrators page,
you may receive the following error message if the port for the Web application
is 99:
User Cannot be found.
You customize a SharePoint Web part page that has the <CustomAction> element. When you edit the page in SharePoint Designer, you may
receive the following error message:
Operation is not
valid due to the current state of the object.
When you use the stsadm -o updatefarmcredentials -userlogin DomainName\UserName -password NewPassword command to update Microsoft Office SharePoint Server farm
credentials, you may receive the following error message:
There was an error encrypting or decrypting
credentials.
When you break the item level permissions on more than
1,000 list items, the content query Web part on root Web application displays
no items.
When a query is initiated from the Search.asmx SharePoint
2007 Web service, no results are returned if the site uses forms-based
authentication (FBA).
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
There are no prerequisites for
installing this hotfix.
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.
32-bit hotfix package
Download information
Collapse this tableExpand this table
File name
File version
File
size
Date
Time
Platform
Wss-kb957691-fullfile-x86-glb.exe
12.0.6331.5000
23,516,808
19-Oct-2008
00:20
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,742,976
18-Oct-2008
12:22
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
