Description of the Windows SharePoint Services 3.0 hotfix package: June 5, 2008

Hotfix Download Available
View and request hotfix downloads

View products that this article applies to.

SUMMARY

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 June 5, 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 package.
Whether you must make any registry changes.
The files that the hotfix package contains.

Back to the top

INTRODUCTION

List of issues that this hotfix package fixes

This hotfix package fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

You have two forests that have one-way forest trusts. From one forest, you try to use Microsoft Office SharePoint Server 2007 to crawl a file share in the other forest. To do this, you use a Crawl rule to configure the foreign content access account. However, nothing in the file share is crawled.

Note To work around this issue, you can create a two-way forest trust between two forests and then use the default content access account.
When you search by Created dates or Modified dates in Windows SharePoint Services 3.0, you receive an error message resembles following:
No results matching your search were found.
You use more than one content type in a Windows SharePoint Services 3.0 list. You try to create a new document by using a content type other than the default content type. However, in Office client applications, you find that the content type metadata displays the required columns for the default content type instead of the required columns for the content type that you are using.

Note Office client applications include Microsoft Office Word, Microsoft Excel, and Microsoft PowerPoint.
When you try to delete a Windows SharePoint Services 3.0 site that has subsites, you receive an error message that resembles following:
Error deleting Web site "/S1". You can't delete a site that has subsites.
This error message is correct because you cannot delete a site that has subsites. However, after you receive the error message, the owners group and members group of the site are deleted.
When you use WebDAV commands to upload large files to a Windows SharePoint Services 3.0 site or download large files from a Windows SharePoint Services 3.0 site, the back-end SQL server is under heavy load.

This issue occurs because the WebDAV GET command does not chunk large files.
In a Windows SharePoint Services 3.0 site, the Calendar view from a custom list that has Start date and End date fields is not displayed correctly. This problem occurs when the date period for a new entry overlaps an existing entry.
The migrateuser command does not work when the user has different access control lists (ACLs) set. For example, the user may have both Passport Unique Identifiers (PUIDs) and e-mail ACLs.

Note The migrateuser command can be used in the following syntax:
stsadm -o migrateuser -oldlogin DOMAIN \ user -newlogin DOMAIN \ user [-ignoresidhistory]
On a Windows SharePoint Services 3.0 site, you add a lookup column to the People and Groups list. If you try to add a new user to the list, you receive an error message that resembles following:
Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION))

Back to the top

Known issues

Consider the following scenario. You add a custom list as a Web part on the home page of a Windows SharePoint Services 3.0 site. When you try to edit the current view of the custom list by clicking Edit the current view, the Create View page opens. However, the Edit View page for this custom list should be opened.

Note To work around this issue, edit the list view before you add the custom list to a Web part on the home page of the SharePoint site. To do this, follow these steps:
1. Remove the Web part that contains the custom list from the home page.
2. Open the custom list, and then click Modify this View.
3. On the Edit View page, make any changes that you want, and then click OK.
4. Add the custom list back to a Web part on the home page.
953399 (http://support.microsoft.com/kb/953399/ ) The thesaurus feature does not function when the "Enable Search Term Stemming" option is enabled on a SharePoint site

Back to the top

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 this specific problem. 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:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

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 package.

Restart information

You do not have to restart the computer after you apply this hotfix package.

Hotfix replacement information

This hotfix package is not replaced by any later hotfix package.

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 package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to correct the issues that are listed in this article.

32-bit hotfix package

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