Issues that the hotfix package fixes

This hotfix package fixes the following issues:

This hotfix package also fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

• You receive an HTML rendering error message when you search for folders or for files if a folder name contains a period as the last character of the folder name
  
  When a crawl is run on folders that contain a period as the last character of the folder name, the folders are crawled successfully. However, when you search for the folder or for a file that the folder contains, you receive an HTML rendering error message.
• DACL information is not processed during an incremental crawl
  
  If changes are made to the discretionary access control list (DACL), the DACL information is processed when a crawl is performed. However, if an incremental crawl is performed, the DACL information is not processed.
• Error message when you try to refine the search results in a SharePoint Server 2007 site collection: "No results matching"
  
  You perform a search in a SharePoint Server 2007 site collection. When you try to refine the search by clicking a link in the search results, the Web page for the refined search results is blank. Additionally, you receive the following error message:
  No results matching.
• The first user who visits his or her "My Site" Web site after IIS has been reset sets the path that all users will use
  
  You have users who visit their "My Site" Web site on a server that is running SharePoint Server 2007. You reset Internet Information Services (IIS). After you do this, the first user who visits his or her "My Site" Web site after IIS has been reset sets the path that all users will use.
  
  For example, the first user visits the Web site by using the NetBIOS path. In this case, all users who visit their "My Site" Web site will visit the site by using the NetBIOS path.
  
  Conversely, if the first user visits his or her "My Site" Web site by using the fully qualified domain name (FQDN) path, all users who visit their "My Site" Web site will visit the site by using the FQDN path.
• Error message when you search for a single word during a BDC search in a SharePoint Server 2007 production farm: "No results matching your search were found"
  
  You run a search on a Business Data Catalog (BDC) data source that is contained in a SharePoint Server 2007 production farm. If you search for a single word, you receive the following error message:
  No Results matching your search were found.
• You receive an error message when you type the appropriate language text for "Yes" or for "No" in a KPI in a Web site that was created in a language other than English
  
  You have a SharePoint Server 2007 Web site that was created in a language other than English. The Web site uses a key performance indicator (KPI) that contains a Yes/No column. When you type the appropriate language text for "Yes" or for "No" in the Yes/No column, you may receive the following error message:
  Filter value is not a valid Yes/No value. Specify Yes or No.
• A URL is saved as an HTTP link instead of as an HTTPS link if a reverse proxy server is used
  
  You deploy SharePoint Server 2007 in an extranet environment that uses a reverse proxy server. When the user types in the public URL, the server that is running SharePoint Server 2007 receives the Web request as a different internal URL.
  
  If the user clicks Add to My Links to save the URL, the URL is saved as an HTTP link instead of as an HTTPS link.
• Changes in a user's Active Directory account are not saved in the user's custom profile
  
  You create a custom user profile in SharePoint Server 2007. You map the properties of the custom profile to the properties of the user's Active Directory directory service account. When a change is saved in the user's Active Directory account, the change is not saved in the custom profile.
• Error message when you try to view the result properties of a KPI: "Incorrect function"
  
  When you try to view the result properties of a key performance indicator (KPI), the results are not displayed. Instead, you receive the following error message:
  Incorrect function (Exception from, HRESULT:0x80070001)
• A full crawl to crawl .pdf files may stop unexpectedly when an .ocn file is embedded in a .pdf file
  
  When a full crawl is performed to crawl .pdf files in a SharePoint Server 2007 site collection, the crawl may stop unexpectedly. Additionally, CPU usage may increase to 100 percent. This issue may occur when an .ocn file is embedded in a .pdf file.
• Cookies that should be retrieved and saved are not found in Forms-Based Authentication content
  
  When a crawl is performed on Forms-Based Authentication content, cookies that should be retrieved and saved are not found.
• A contact's name is not resolved after you add a keyword to the contact if the contact's Active Directory display name contains a comma
  
  You use the Site Collection Administration feature to add a keyword to a contact whose Active Directory display name contains a comma. Then, you try to edit the contact's keyword again on the Search Keyword Web page.
  
  When you do this, the contact's name is not resolved, and the contact information is missing. You must type the contact information to save the changes to the contact's keyword.
• Error message when you try to edit the keywords for a SharePoint Server 2007 site collection: "Access denied"
  
  You add keywords to a SharePoint Server 2007 site collection. When you try to edit the keywords, you receive the following error message:
  Access denied.
• Error message when you try to discard changes to a published Web page in a SharePoint Server 2007 site collection: "Cannot find server or DNS error"
  
  You run SharePoint Server 2007 in an environment that uses a router or other hardware to perform load balance work on servers. You try to edit a published Web page in a SharePoint Server 2007 site collection. When you do this, the Web page is in a "checked-out" state. When you try to discard changes to the Web page, you receive the following error message:
  Cannot find server or DNS error.
• Error message when you try to create a hierarchy for a SharePoint Server 2007 site collection: "Out of memory"
  
  When you try to create a hierarchy for a SharePoint Server 2007 site collection, the process may not finish. Additionally, you receive the following error message:
  Out of memory
• Memory usage for the OSearch process increases every time that a crawl is run
  
  Every time that a crawl is run to crawl site collections, memory usage for the OSearch process (Msssearch.exe) increases.
• It takes longer than expected to open an item or to save changes to an item in a custom list
  
  When you try to edit or to save changes to an item in a custom list, it takes longer than expected to open the item or to save the changes.

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.
The post-2007 Office servers SP1 hotfix package is supported for installation on the release version of the 2007 Office servers or on the 2007 Office servers SP1. However, the hotfix package is not a superset to the 2007 Office servers SP1. Therefore, you can install the hotfix package before you install the service pack. However, you still have to install the service pack at the same time or at a later date.

The deployment steps and requirements that are described in the documentation for how to deploy updates are the same as the steps and requirements to install the service pack.

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 informationSharePoint Server 2007 Web front-end server

Microsoft Windows Installer .msp file informationAfter the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table: Additionally, the following files are installed when you install the Spswfe.msp file. SharePoint Server 2007 for Search

Microsoft Windows Installer .msp file informationAfter the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table: Additionally, the following file is installed when you install the Osrchapp.msp file. SharePoint Server 2007 for Search Web front-end server

Microsoft Windows Installer .msp file informationAfter the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table: Additionally, the following files are installed when you install the Osrchwfe.msp file.

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 informationSharePoint Server 2007 Web front-end server

Microsoft Windows Installer .msp file informationAfter the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table: Additionally, the following files are installed when you install the Spswfe.msp file. SharePoint Server 2007 for Search

Microsoft Windows Installer .msp file informationAfter the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table: Additionally, the following file is installed when you install the Osrchapp.msp file. SharePoint Server 2007 for Search Web front-end server

Microsoft Windows Installer .msp file informationAfter the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table: Additionally, the following files are installed when you install the Osrchwfe.msp file.