This article describes the Microsoft Office SharePoint Server 2007 issues that are fixed in the Office SharePoint Server 2007 hotfix package that is dated February 23, 2010.

• 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

• You filter items in a document library by using a value in a Lookup column. In this case, no items are displayed.
  
• You enable the Federal Information Processing Standard (FIPS) algorithm. Then, you visit a page that contains a Summary Links Web part that contains one or more links. In this case, an InvalidOperationException exception is thrown. Additionally, you receive the following error message:
  This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
• Under a heavy load, a deadlock occurs in the Blobcache.
  
• Cascading style sheet (.css) files are not imported after the first full deployment as expected.
  
• When you publish a variation page, you receive the following error message:
  An error occurred trying to publish this page on the set schedule. Republish the page with a new date or view the log if the problem continues.
  
  This issue occurs when the scheduled publish date for the variation page is invalid.
  
• You convert a List View Web part from a document library view to XLST data view in Office SharePoint designer. Then, you access that document library from the Content and Structures page. In this case, an access violation exception occurs.
  
  This access violation exception also occurs when you access the document library to add an image when you edit a page in the site collection.
  
• You cannot customize an RSS viewer Web part. When you click Modify My Web Part, you receive the following error message in the tool pane:
  An error has occurred.
• When you change the visibility of some profile properties on your MySite, you receive the following error message:
  An unknown user profile error has occurred. Try recreating this user profile or updating this user profile from the directory service to resolve this problem.
• Certain Norwegian compound words such as "tusenÃ¥rssteder" cause the word-breaker to fail. Additionally, the following error message is logged in the Crawl log:
  Exception from HRESULT: 0xC0000005
• When a template is set to the Article Page content type in the source variation, only the template propagates. Additionally, the variation propagation of a page fails without an error message or a warning message in the Variation log.
  
• You experience the following issues:
  • A child site collection contains more than 51 search keywords. You visit the next page by using the arrow on the top of the Manage Keywords page of the child site collection. In this case, the Manage Keywords page of the parent site collection is displayed.
  • When you search for a keyword on the Manage Keywords page of a child site collection, the search is performed on the parent site collection.
• You install the hotfix packages that are described in Microsoft Knowledge Base articles 973409 and 973410. When you use the Stsadm.exe -o migrategroup command to change the name of an Active Directory security group, you receive the following error message:
  Error to migrate user profile
  
  Additionally, the following error message is logged in the Unified Logging Service (ULS) log:
  Could not find stored procedure 'dbo.profile_MigrateGroupAccount'
• You try to access a site by clicking View My Site in Microsoft Office Outlook. This site belongs to a user who has an apostrophe in his e-mail address. In this case, you receive the following error message:
  User not found.
• Consider the following scenario. You search for a person and view the result by using the Relevance view or the Social Distance view. The Add to My Colleague link is available for that person. Then, you click the link in the Social Distance view to add that person to My Colleagues. In this scenario, the link still appears for that person in the Relevance view.
  
• Certain applications such as the Hotmail application crash in the NaturalLanguage6.dll file.
  

• 980477  (http://kbalertz.com/Feedback.aspx?kbNumber=980477/ ) Error message when you use the “stsadm.exe -o migrateuser” command to change the name of an Active Directory security group in Microsoft Office SharePoint Server 2007: "Error to migrate user profile"
• 980478  (http://kbalertz.com/Feedback.aspx?kbNumber=980478/ ) Error message when you access an Office SharePoint Server 2007 site by clicking “View My Site” in Office Outlook: "User not found"
• 980480  (http://kbalertz.com/Feedback.aspx?kbNumber=980480/ ) An application crashes when you run the application to implement word breaking in Office SharePoint Server 2007

This hotfix package together with hotfix package 978389 fixes the following issues:

• 979157  (http://kbalertz.com/Feedback.aspx?kbNumber=979157/ ) No search results are returned when you search for content in an Office SharePoint Server 2007 site that contains German umlauts in the URL
• 979353  (http://kbalertz.com/Feedback.aspx?kbNumber=979353/ ) The "quickdeployjobs" property in a target site is overwritten in Office SharePoint Server 2007
• 980041  (http://kbalertz.com/Feedback.aspx?kbNumber=980041/ ) When a draft version (0.x) of a page is crawled in Office SharePoint Server 2007, subsequent incremental crawls ignore that page when it is published to a major version (1.x)
• 979814  (http://kbalertz.com/Feedback.aspx?kbNumber=979814/ ) The Manage Content Source page times out intermittently in Office SharePoint Server 2007
• Offline files are crawled unexpectedly in Office SharePoint Server 2007   (http://kbalertz.com/Feedback.aspx?kbNumber=Offline files are crawled unexpectedly in Office SharePoint Server 2007/ ) To be written

For more information, 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 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.

Prerequisites

You must have 2007 Microsoft Office Servers Service Pack 2 or 2007 Microsoft Office Servers Service Pack 1 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

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.

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 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.

x86

Download information



Microsoft Windows Installer .msp file information



After 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:



x64

Download information



Microsoft Windows Installer .msp file information



After 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:

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: