Description of the SharePoint Server 2007 Cumulative Update Server Hotfix Package (Coreserver.msp): April 30, 2009

This article describes the Microsoft Office SharePoint Server 2007 issues that are fixed in the Office SharePoint Server 2007 hotfix package that is dated April 30, 2009.

• 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

• On the Content Deployment Job settings page, the sub-sites that start with common prefix lose the selected flag. For example, if you select http://site/xyz, http://site/xyz2, http://site/xyz_2, only http://site/xyz will be selected.
• Content deployment for a large site collection may stay in the export phrase for several days without finishing. This issue occurs when the size of the site collection is larger than 10 GB.
• Navigation Links are deleted if a user who does not have permissions to see all navigation links modifies the navigation.
• After a reghost operation (Reghost.aspx) on a publishing Web, all files that have been customized at least once will have a hardcoded size of 200 bytes in the alldocs table after these files are restored to the original versions. This causes Blobcache to save only the first 200 bytes of the affected files to the cache. This behavior causes invalid images, .css files, and corrupt .js files served to visitors.The Blobcache reset is not enough. You must modify the files to have the correct size information in the alldocs table.
• When you use the Microsoft Office SharePoint Server publishing APIs to store and retrieve values, the PortalListItemSiteMapNode object returns incorrect Cachefield values.
• Page scheduling notifications do not work on on the Pages library with default settings when the out of the box Approval workflow is enabled.
• If you schedule a page publish, the page is not published even after the scheduled start time. This issue occurs because that the GetChanges stored procedure has a limit of retrieving at most 1000 items per query. When there are more than 1000 changed items in a deployment, any items over 1000 will be omitted.
• When you try to browse to a site if the site collection has more than 10000 ACL cache entries, you receive the following error message:
  Attempt to release mutex not owned by caller. (Exception from HRESULT: 0x00000120)
• In the Content Query Web Part, if you apply audience filtering and limit the number of items to display a certain value, the Content Query Web Part may show fewer items than you set. For example, if you set the limit of the number of items to display to 5, the Content Query Web Part may display only 3 items.
• Output caching does not work when a web part is configured to target more than one audience. If you have two audiences (Audience 1 and Audience 2), the rendering of the page may based on the user being a member of Audience 1, but not a member of Audience 2. If another user is a member of Audience 2, but not Audience 1, this user sees a different page.
• The Variation Site propagation operation and the create hierarchies operation fail if dependent features are activated manually on source site and not as part of the site template or a staple feature.
• The value selected in the entity picker dialog box is not displayed in the column after you click OK in the entity picker dialog box. This behavior only occurs in FireFox 2, Firefox 3, Safari, and Chrome.
• You backup Microsoft Office SharePoint Server (MOSS) 2007 content database through SQL Server Then, you upgrade to MOSS 2007 SP1. When you restore the content database by using the stsadm -o addcontentdb command, data loss may occur.
• Users that have comma (,) in the display name cannot be imported in the Active Directory Resource setup.
• When you use the WSRP Consumer Web part, the JSessionID value is not maintained for the duration of the session. Instead, a new JSessionID value is generated for each search attempt that is performed.
• You use Internet Explorer 8 to edit content in a field control in a MOSS 2007 site. If you close the browser or navigate to a different page without saving the content you edited in the field control, you receive an error message that states that the page could not be saved automatically. The page actually may have saved correctly, but if a validation error occurs, changes that you made to content will be lost.
• When you create a non-English Search Center site collection, search scopes are missing. Additionally, a dropdown list does not appear. Only the "this site" string appears. For example, this issue occurs in a French Search Center site collection.
• User profile properties that are set as required can be saved without values.
• The Content Deployment job randomly fails right after it enters the import phase. When this issue occurs, specific error information appears in the Content Deployment job report.
• 960254

  (http://support.microsoft.com/kb/960254/ )

  Error message when you click Checked out to me in the "Manage Content and Structure" page after you filter the picture library by a custom column: "Cannot find column [repro]"

Issues that this hotfix together with hotfix 968857 fix

• 970155

  (http://support.microsoft.com/kb/970155/ )

  Error message when you run a full crawl on Business Data Catalog (BDC) data source in Office SharePoint Server 2007: "0X80040E14"
• 970113

  (http://support.microsoft.com/kb/970113/ )

  A discussion board item does not index when a crawl is run against the site if the subject contains a period (.)
• 970003

  (http://support.microsoft.com/kb/970003/ )

  The filter daemon process crashes when Office SharePoint Server 2007 crawls Office 2007 documents
• 970108

  (http://support.microsoft.com/kb/970108/ )

  By default, if you use the CONTAINS Predicate, the search terms in the CONTAINS predicate are hit-highlighted
• 970010

  (http://support.microsoft.com/kb/970010/ )

  The thesaurus is not applied when you perform a search after you type text in the "All of these words" text box or in the "The exact phrase" text box in SharePoint Server 2007
• 968845

  (http://support.microsoft.com/kb/968845/ )

  Office SharePoint Server 2007 cannot index Office SharePoint Server 2003 portal listings
• 969401

  (http://support.microsoft.com/kb/969401/ )

  Search term variants are not highlighted in the search results if you enable search term stemming in Office SharePoint Server 2007
• 969103

  (http://support.microsoft.com/kb/969103/ )

  The System.IO.PathTooLong exception occurs when you issue a public "DataSet QueryEx(string queryXml)" method that includes "HitHighlightedSummary" in your Windows SharePoint 3.0-based application

Note To resolve these issues, you must install both hotfix 968857 and hotfix 968859. For more information about hotfix 968857, 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

To install this hotfix, you must have 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: