This article describes the Microsoft Office SharePoint Server 2007 issues that are fixed in the Office SharePoint Server 2007 hotfix package that is dated August 26, 2008.

• The issues that the hotfix package fixes.
• The prerequisites for installing the hotfix package.
• Whether you must restart the computer after you install the hotfix package.
• Whether the hotfix package is replaced by any other hotfix packages.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

Issues that this hotfix package fixes

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

• When you edit a navigation link in a SharePoint Server 2007 site, each edit may cause the query string part of the link to be doubled.
  
  For example, the link /newtestsite/_layouts/viewlsts.aspx?ShowSites=1 becomes /newtestsite/_layouts/viewlsts.aspx?ShowSites=1?ShowSites=1. If you continue to edit the navigation link, it will become very long. Finally, it will be too long to edit.
• You use the Collaboration Portal template to create a SharePoint Server 2007 site collection. Then, numbers of log entries for the site collection are logged in the content and structure log. In this case, when you try to check the content and structure log again under Site Administration, you receive the following error message:
  server is out of memory error
• You use the Publishing Portal template to create a SharePoint Server 2007 site collection. When you use Windows Explorer to create a new folder for the site collection, the application event log is filled with thousands of error events.
• When you use Group Policy on a SharePoint Server 2007 server to enable the Federal Information Processing Standards (FIPS), Event ID 6482 is logged in the event log.
• Consider the following scenario:
  • In Shared Services Provider (SSP), you import audience members from a security group that is in an organizational unit (OU) in an Active Directory directory service.
  • You move the security group to a new OU within Active Directory.
  • In SSP, you try to import the audience members from the security group again.
  In this scenario, when you try to search for the security group, the security group is located under the old OU.
• Consider the following scenario:
  • You enable advanced usage analysis logging on a portal.
  • The SharePoint site contains a document that has a full file URL that exceeds 260 characters.
  • When the document is accessed by users, or the document is crawled by the SharePoint search process on a particular day, visits to the site on that particular day are logged.
  In this scenario, when you open Site usage reports, usage for that particular day may have a value of 0.
• In a SharePoint Server 2007 site collection, you create a subsite. When you delete the navigation heading of the subsite, and then you move the subsite, the URL for the subsite is not updated in the quick-launch menu.
• On a SharePoint site, you add a Web Server Control in a Web page to display the last time that the Web page was modified. After you update the Web page, the last-modified time is updated as expected. However, the last-modified time is not displayed in the time zone that the SharePoint site is set to use.
• The procedure GetListItemWorkflows is called unexpectedly every time that you edit a list item on a site collection.
• On a SharePoint site, when you try to change the source data of a Categories Web Part, a JavaScript error occurs unexpectedly.
• Consider the following scenario:
  • In a SharePoint site, you add two "This Week In Pictures" Web Parts on a Web page.
  • These two Web Parts are linked to different picture libraries of a SharePoint Server 2007 site.
  In this scenario, when you try to view the slide show of a Web Part, the pictures that are displayed are from the picture library in another Web Part.
• In SharePoint Server 2007, the page editing toolbar is not displayed for a page that uses a plus sign (+) in its URL.
• In the site manager page of a SharePoint site, when you try to copy more than 50 items in a document library, you may receive the following error message:
  You may re-try the operation, and you may need to clean up the half-created data first before re-trying. If the problem persists, please contact your system administrator.
• A user created a page in a SharePoint Server 2007 site collection. After that, the user was removed from the site collection. In this case, when you try to view the page settings of the published page, you receive the following error message:
  User cannot be found
• You configure SharePoint Server 2007 to crawl a Lotus Notes content source in which a Lotus Notes document contains some attachments. During the crawl, the Windows API GetTempFileName is called to generate the temporary files to temporarily store attachments. However, those temp files are not removed as expected after the crawl.
  
  In this case, there are too many temp files in the temp folder. Therefore, the calls to GetTempFileName become very slow. The crawl operation takes longer to finish.
• Consider the following scenario:
  • In SharePoint Central Administration, you use the Collaboration Portal template to create a SharePoint Server 2007 Web site.
  • The URL of the Web site uses managed path/sites formatting.
    
    For example, the URL may be http://servername/sites/collaborationportal.
  • You delete the Top Sites Web Part, and then you add it again on a Web page in the Web site.
  When you try to edit the Web Part, you receive the following error message:
  An unexpected error has occurred.
• In SSP, you import the user profiles from an Active Directory directory service. You map the Assistant property of the user profiles to the Assistant property of the user in Active Directory.
  
  When you check the imported user profiles in SSP, the value of the Assistant property of the user profiles displays the distinguished name (also known as DN) instead of the actual user name.
• The spelling checker (spellcheck.asmx) cannot auto-detect the language for certain strings. For example, when you use the spelling checker to check the spelling of the string "New Day January," you receive the following error message:
  Spell checking is not available for the default language. Use one of the following languages and click OK to continue spelling, or click Cancel to stop
• Consider the following scenario:
  • A SharePoint Server 2007 farm contains one index server and one query server.
  • You change the index server to perform both the Indexer role and the Query role.
  In this scenario, when you change the index server to the Indexer role only, the query server will not be reinitialized.

This hotfix package, together with hotfix 956057, also fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

• When you perform a full-text query, you cannot use the equal sign (=) in the column of the Number type.
• On a SharePoint site, when you search for a common Chinese name, you receive the following misleading message:
  The query you typed contains only words to exclude from results. Type one or more search words to include, and then retry your search.
• A full crawl may take several weeks to be completed. Additionally, the crawl may stop responding, and you cannot stop it or cancel it.
• After you install the following post-Service Pack 1 hotfix packages, you cannot use the Search Web service on the encoded paths. For example, the encoded path can be http://servername/shared%20documents.
  
  For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  941274  (http://kbalertz.com/Feedback.aspx?kbNumber=941274/ ) Description of the SharePoint Server 2007 and SharePoint Server 2007 for Search post-2007 Office servers Service Pack 1 hotfix package: January 31, 2008
  941422  (http://kbalertz.com/Feedback.aspx?kbNumber=941422/ ) Description of the Windows SharePoint Services 3.0 post-Service Pack 1 hotfix package: January 31, 2008
• You create a custom security trimmer, and then you register it to two Shared Services Providers (SSPs). When you search programmatically against one of the SSPs, the correct search results are displayed, and all the security trimmed URLs from this SSP are available.
  
  If you search programmatically on the other SSP during the same session, the correct search results are displayed as expected. However, the URLs that are passed to the security trimmer are from the previous SSP.
• Consider the following scenario. You develop a solution that is based on Windows SharePoint Services 3.0. The basis of the solution is a custom security trimmer. Then, you add items to a list and modify the permission on these items. In this scenario, when you try to search items from the list, the items in the search results do not have a title. Additionally, the URLs are invalid.
• Queries that have stemmed words take longer to return the results.
  
  For example, a query for zone takes 5 seconds. However, a query for zone 2 takes 15 seconds. The number 2 in zone 2 can be seen as the stemmed word for the query.
• When you try to crawl a content source, the offline files in the content source are indexed unexpectedly. The offline files are the files that have the PR_FILE_ATTRIBUTE_OFFLINE attribute set.
  
  Note After you apply the hotfix, offline files will are not indexed any longer.
• You experience the following symptoms after you start a crawl:
  • Event ID 9502 is repeatedly logged in the Application log.
  • The Mssearch.exe process reaches more than 80 percent CPU usage consistently.
  This issue may occur if invalid content is crawled.
• When you configure the "Search Core Results" Web Part to return a custom managed property of the type Date and Time, only the date part is returned. This issue occurs regardless of how you configure the "Search Core Results" Web Part.

Note To resolve these issues, you have to install both hotfix package 956056 and hotfix 956057.

For more information about hotfix 956057, click the following article number to view the article in the Microsoft Knowledge Base:

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 does not replace a previously released hotfix.

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 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 correct the issues that are listed in this article.

The global version of this hotfix package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it 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.

32-bit hotfix file information

Download informationMicrosoft 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:

64-bit hotfix file information

Download informationMicrosoft 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:Additional notes

• For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
• For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
  824684  (http://kbalertz.com/Feedback.aspx?kbNumber=824684/ ) Description of the standard terminology that is used to describe Microsoft software updates