Assume that you create a Windows SharePoint Services 3.0 site collection and a subsite under the root site. An exception occurs when you view the Site Navigation Settings page of the root site or the subsite.
Consider the following scenario:
You enable the incoming email feature for a document library in Windows SharePoint Services 3.0.
You remove Manage Permissions in the "User Permissions for Web Applications" window.
You send an email message that contains an attachment to the document library.
In this scenario, the attachment is not added to the document library, and an error message is logged in the Unified Logging Service (ULS) log.
When you create a document library on a team site by using a template that contains an invalid field, you cannot delete the invalid field from the document. This issue specifically occurs when the team site’s URL contains a space.
You cannot add authenticated users to a SharePoint group by using the Add all authenticated users link in Windows SharePoint Services 3.0.
After you upgrade Windows SharePoint Services 3.0 to Windows SharePoint Services 3.0 Service Pack 3, performance issues occur.
Assume that you have a Windows SharePoint Services 3.0 site that contains a list, and you assign the Collect Feedback workflow to the list. When the workflow is canceled, a deadlock occurs on a SQL server that stores Windows SharePoint Services 3.0 content databases.
Consider the following scenario:
You create a content source in a search service application.
You configure the crawl setting and select the Only crawl the Site Collection of each start address option.
You remove a user from a SharePoint security group.
You perform an incremental crawl.
In this scenario, the search crawler does not receive user removal information.
Assume that you delete the Content Type column in a document library in Datasheet view, and then you try to upload some documents to the document library. In this situation, you cannot upload the documents to the library, and an exception occurs.
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 website:
How to obtain the latest service pack for the 2007 Office server products
You may not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
To use the hotfix in this package, you do not have to make any changes to the registry.
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 resolve the issue that is 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
tab in the Date and Time item in Control Panel.