You are running an add-in to SQL Server Reporting Services that creates SharePoint 2007 list items. However, when the list items are created the associated workflows are not started as expected. Additionally, you receive the following error message in the reporting services host Application log:
Event Type: Error
Event Source: Windows SharePoint Services 3 Event Category: General
Event ID: 6875
Time: 1:57:56 PM
Error loading and running event receiver Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver in Microsoft.SharePoint, Version=188.8.131.52, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Additional information is below.
: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
You configure a workflow to start automatically when a new item is added to a SharePoint Server 2007 document library. When you add several items to the document library, not all the workflow instances that correspond to the items are started automatically.
The variation system does not remove the web part from target sites when the last web part has been removed from the source page.
There is no API that can be used to access the Information Rights Management (IRM)-protected protected files in a not encrypted manner.
You synchronize a recurring event to a Windows SharePoint Services calendar by using Outlook. In this situation, successive modifications to one of the exceptions in the recurrence cannot be synchronized with the WSS calendar.
You are member of multiple SharePoint groups that were granted unique permissions on multiple list items in multiple lists. The lists are used as lookup columns in a Pages library. When you are added to an additional SharePoint group which will increase the total number of visible items with unique permission above 1000, the default view in Pages library will display the following error message:
<!- Render failed->
This problem occurs because of an incorrect SQL query.
Note If you are removed from the last SharePoint group, the items will be displayed correctly.
You change the view of the ListViewWebPart web part for a survey to <Summary view> in SharePoint Server 2007. In this situation, you receive the following error message:
An unexpected error has occurred
You change a column for a content that is used in the SharePoint Server 2007 document library from Required to Hidden. When you try to check in a document in the document library, you receive the following error message:
You must fill out all required properties before checking in this document.
An incremental content deployment of a package in SharePoint Server 2007 fails. This problem occurs when the following conditions are true:
The package contains a renamed site.
A sub site contains a link to the renamed site.
You create a survey that contains branching logic. Immediate alerts are not sent to subscribers when a new survey is filled-out.
You enter text in the Type a message to include with your request text box when you design an approval workflow in SharePoint Server 2007. When you run the workflow, the text is not displayed.
If a lookup column is added to a list and then the view is converted to an Extensible Style sheet Language Transformations (XSLT) data view, the URL to the DispForm.aspx page always points to the first row in the XML document that is returned for the data view.
You create a view that does not contain one of the following columns in a SharePoint Server 2007 website:
Type (icon linked to document)
Edit (link to edit item)
Title (linked to document with edit menu)
Title (linked to item)
If you group the view by a manually created date column, you receive the following error message:
<!-- #RENDER FAILED -->
After you delete an Office SharePoint site collection, the audit data for the site collection is not trimmed if you use the stsadm -o trimauditlog command. Additionally, see more information about the stsadm command
Alerts that are created by using a view that filters items by using the Created field or Modified field do not work.
If a SharePoint Server 2007 farm is running in ProviderUserKey mode, users cannot be imported.
A picture library item is deleted, restored from recycle bin and then deleted again. In this situation, a violation of primary key constraint error is generated during an incremental content deployment.
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.
You must have 2007 Microsoft Office Servers Service Pack 2 or 2007 Microsoft Office Servers Service Pack 1 installed to apply this hotfix package.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for the 2007 Office server products
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.
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 English 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.