Assume that a content type is created and associated with many libraries. When you add or change a field in this content type, the incremental content deployment takes a very long time to process.
Consider the following scenario:
You create a folder in a Microsoft SharePoint document library and upload a document to it.
You rename the folder.
You move the document within the folder to another document library by using the Manage Content and Structure option.
In this scenario, the last-modified time of the document is changed to the time that the folder was moved.
An incremental content deployment fails when you add and then delete a user from the source site collection.
Assume that you create more columns in a SharePoint list than one SQL server database row supports. As a result, row-wrapping occurs, and one list item is stored in multiple database rows. When you set list items to inherit permissions from their parent list, attachments to the list items become inaccessible.
When you use a delay activity for a workflow, the workflow does not resume from the delay, or the workflow takes longer than expected to resume from the delay.
Assume that you set a user as a site collection administrator, and you do not assign any specific permission assignments at any scope. When you delete this user from the site collection, the site data does not report the site collection level security change.
Assume that you enable the output caching feature on a Windows SharePoint Services 3.0 site. After you apply the hotfix package that is described in Microsoft Knowledge Base (KB) article 2656351, the site is no longer output cached when an authenticated user visits the site.
The imaging web service requires more and more time to upload images.
When verbose logging is enabled, certain kinds of call stack information will generate an unhandled exception.
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 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.