Consider the following scenario. You create a folder in a SharePoint document library that contains documents and subfolders. Then, you change the name of the folder one or more times. In this scenario, the modified time feature values for all the documents and subfolders that are located in the renamed folder are changed unexpectedly.
Consider the following scenario:
You create a workflow and configure it to start automatically when a list item is created in a list in Windows SharePoint Services 3.0. Additionally, you configure the workflow to update the list item that triggers the workflow.
You create a second workflow and configure it to start automatically when a list item is changed in the list.
You create a third workflow and configure it to create a list item in the list and start manually.
You create a list item.
The first two workflows start automatically.
You start the third workflow manually in the list.
In this scenario, the first two workflows are not triggered on the new list item that is created by the third workflow.
Consider the following scenario:
You have Full Control permissions on a subsite and Read-only permissions on the subsite’s root site.
You add a webpage to the subsite.
You schedule an end date for the webpage, at which time the webpage will be unpublished.
You update the end date to Never on the Page Settings page.
In this scenario, the webpage is unpublished at the end date that you scheduled.
When you try to customize the top link bar or the Quick Launch area in Windows SharePoint Services 3.0, an error occurs.
Consider the following scenario. You configure document libraries to receive email messages in Windows SharePoint Services 3.0. Then, you send an email message to multiple document libraries. In this situation, an incoming email timer job deletes the email message even if the email message was not successfully delivered to all the document libraries.
Note This issue specifically occurs when the document libraries are in different content databases.
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 the problem 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.