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 use the Publishing Portal template to create a Microsoft Office SharePoint Server 2007 site collection. You add an Active Directory group to the Approver group of the Parallel Approval workflow in the site collection. However, when you log on as a user in the Active Directory group and browse the "Waiting for Approval" page, you see that the Accept/Reject button is disabled on the Workflow menu.
  
  Note To work around this issue, you can individually add the users in the Active Directory group to the Approver group.
  
• You use the Collaboration Portal template to create a Microsoft Office SharePoint Server 2007 site collection. You add a new folder under the Links list in the site collection, and you name the new folder "Forms." If you try to rename the newly created folder, you receive an error message resembles following:
  Exception from HRESULT: 0x8107096B
  Additionally, if you click Manage Content and Structure on the Site Actions menu, you find that the name of the newly created folder is blank.
  
• You have two forests that have one-way forest trusts. From one forest, you try to use Microsoft Office SharePoint Server 2007 to crawl a file share in the other forest. To do this, you use a Crawl rule to configure the foreign content access account. However, nothing in the file share is crawled.
  
  Note To work around this issue, you can create a two-way forest trust between two forests and use the default content access account.
  
• When you search by Created dates or by Modified dates in Microsoft Office SharePoint Server 2007, you receive an error message resembles following:
  No results matching your search were found.
• You try to add more than one security group as an audience to the Top Navigation bar of a Microsoft Office SharePoint Server 2007 site. However, only the last security group is resolved and added to the top navigation bar. The other security groups are not resolved.
  
  Note To work around this issue, add all security groups into one master security group. Then, add the master security group as audience to the top navigation bar.

This hotfix package fixes the following issue:

• 953145  (http://kbalertz.com/Feedback.aspx?kbNumber=953145/ ) Error message when you try to create a Shared Services Provider (SSP) in Office SharePoint Server 2007: "An error occurred while translating user name "Domain@Name\User1" to a Windows account name - (DS_NAME_ERROR_NOT_FOUND)"
• 953399  (http://kbalertz.com/Feedback.aspx?kbNumber=953399/ ) The thesaurus feature does not function when the "Enable Search Term Stemming" option is enabled on a SharePoint site

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: 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 informationMicrosoft Windows Installer .msp file informationAfter the hotfix package is installed, the global version of this hotfix package has the file attributes, or a later version of the file attributes, that are listed in the following table:

64-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 informationMicrosoft Windows Installer .msp file informationAfter the hotfix package is installed, the global version of this hotfix package has the file attributes, or a later version of the file attributes, that are listed in the following table: