Description of the SharePoint Server 2007 post-2007 Microsoft Office servers Service Pack 1 hotfix package: May 29, 2008

Article ID: 953137 - View products that this article applies to.

This article has been archived. It is offered "as is" and will no longer be updated.

SUMMARY

This article describes the Microsoft Office SharePoint Server 2007 issues that are fixed in the SharePoint Server 2007 post-2007 Microsoft Office servers Service Pack 1 hotfix package that is dated May 29, 2008.

Back to the top | Give Feedback

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 install 2007 Microsoft Office servers Service Pack 1 (SP1) on a computer that is running the release version of Microsoft Office SharePoint Server 2007. However, all DCOM permissions for the WSS_ADMIN_WPG security group and for the WSS_WPG security group are removed from the OSearch DCOM application. Additionally, if the Office SharePoint Server service is running under an account that is not in the Administrators group, the search function will not work.

Note To work around this issue, manually add DCOM permissions for the WSS_ADMIN_WPG security group and for the WSS_WPG security group. To do this, follow these steps:
1. Click Start, click Run, type dcomcnfg, and then press ENTER.
2. Expand Component Services, expand Computers, expand My Computer, and then click DCOM Config.
3. In the details pane, right-click OSearch, and then click Properties.
4. Click the Security tab.
5. Under Launch and Activation Permissions, click Customize, and then click Edit.
6. Click Add to add the local WSS_ADMIN_WPG security group and the local WSS_WPG security group, grant them Local Launch and Local Activation permissions, and then click OK.
7. Under Access Permissions, click Customize, and then click Edit.
8. Click Add to add the local WSS_ADMIN_WPG security group and the local WSS_WPG security group, grant them Local Access Activation permission, and then click OK two times.
9. Restart the computer.
After you perform a crawl on a computer that is running Microsoft Office SharePoint Server 2007, you may receive an error message that resembles the following in the crawl log:
Filtering of this file ended because the file reached the maximum filter output limit. Check that the filter does not generate a large amount of data relative to the size of the document.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756
(http://support.microsoft.com/kb/322756/ )
How to back up and restore the registry in Windows
Note To work around this issue, follow these steps:
1. Click Start, click Run, type regedit, and then press ENTER.
2. Locate the following registry subkey:
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Global\Gathering Manager\MaxGrowFactor
3. Double-click MaxGrowFactor, type 4096, click to select Decimal, and then click OK.
4. Exit Registry Editor.
You perform an incremental crawl on a computer that is running Microsoft Office SharePoint Server 2007. However, any documents in a meeting workplace template document library are not crawled.

Note To work around this issue, perform a full crawl.
Consider the following scenario:
- You create a Calendar list on a computer that is running Microsoft Office SharePoint Server 2007.
- You use Microsoft Office SharePoint Designer 2007 to use a Display item form to display items in the Calendar list in a custom .aspx page.
- You create a series of repeating calendar items.
When you try to edit one of the repeating calendar items on the custom .aspx page, the first calendar item in the series opens instead of the calendar item that you selected.

Note To work around this issue, edit the calendar item in the All Events view of the Calendar list.

Known issue of the hotfix package

Symptoms

Consider the following scenario. You add a custom list as a Web Part on the home page of a SharePoint 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, you expect the Edit View page for this custom list to open.

Workaround

To work around this issue, edit the list view before you add the custom list as 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, 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 as a Web Part on the home page.

Back to the top | Give Feedback

MORE INFORMATION

Hotfix information

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