Description of the SharePoint Server 2007 cumulative update package (MOSS server-package): December 16, 2008

Cumulative update packages for SharePoint Server 2007 contain hotfixes for the SharePoint Server 2007 issues that have been fixed since the release of SharePoint Server 2007.

Note This build of the cumulative update package is also known as build 12.0.6335.5000.

We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SharePoint Server 2007 fix release.

Important notes about the cumulative update package

• The 2007 Office hotfixes are now multilanguage. Therefore, there is only one cumulative hotfix package for all languages.
• One cumulative hotfix package includes all the server component packages. The cumulative update package updates only those components that are installed on the system.

Issues that this hotfix package fixes

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

• 
  
  Consider the following scenario:
  • You publish a SharePoint Portal Server 2007 publishing portal site through Microsoft Internet Security and Acceleration (ISA) Server 2006.
  • The Web application that hosts the publishing portal site is configured to use Allow Anonymous Access and Windows Authentication (NTLM).
  • Output caching is enabled on the publishing portal site through ISA Server 2006, but output caching fails.
  If you press F5 in Internet Explorer to refresh the Web page, the date on the output page is updated. The date should remain constant for the period of time in which the cache is not invalidated. To see the date on the output page in Internet Explorer, right-click the Web page, click View Source, and search for the code that resembles the following:
  Rendered using cache profile:Public Internet (Purely Anonymous) at: 2008-10-10T12:00:57
• You add the Scheduling Start Date field and the Scheduling End Date field to a Web page. If you try to publish a page that contains an Immediately option, you may receive the following error message:
  You must specify a valid date within the range of xxx and xxx.
• When you review a document library by using Site Content and Structure, filtering does not work when the column value contains a semicolon (;).
• If you configure the Max. Cache Size setting of the Site collection object cache to more than 2000, an integer overflow exception may occur. You may receive an error message that resembles the following:
  Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.
• Non-core search Web part queries are not recorded into usage logs.
• You add the Scheduling Start Date field and the Scheduling End Date field to a Web page. You set the values for the Scheduling Start Date field and the Scheduling End Date field, and then you wait until the Web page expires. When you try to publish the Web page, you may receive the following error message:
  The end date of a page must be in the future. Please edit the end date and try again.
• Incremental crawls fail to be scheduled when you have multiple Shared Services Providers (SSPs), and one SSP contains many sources.
• You use the Team Site template as the template for the top-level site in Office SharePoint Server 2007. A subsite owner of the top-level site does not have access permissions to the top-level site. When the subsite owner tries to create his or her own subsite, the owner may receive an "Access Denied" error message.
• You may receive an "ELEMENT NOT FOUND (COM-INTEROP):" exception when you are running crawls that overlap. This issue causes the crawls to fail, and the SharePoint server does not index any further documents.
• When you click the Local Office SharePoint Server Sites link in Content Sources, you may receive the following error message:
  Unexpected Error has occurred
• Search returns zero results during an index merge process.
• If you use the SharePoint spelling check Web Service to check the spelling of the input text, the service strips formatting from the input text.
• In a subsite that has space in the URL, you click the HTML source to put the HTML editor for an HTML control in pop-up mode. Then, you take it out of pop-up mode to check the spelling. When you do this, the spelling check fails. Additionally, you receive the following error message:
  Spelling did not complete properly. If this problem persists, notify your system administrator.
• In SharePoint Server 2007, you create a custom router that routes documents to a specific folder in the records center. The router uses metadata on the document to do this. It does not use the content type. However, you cannot change the destination parameter in the IRouter.OnSubmitFile method.
• In Office Outlook 2007, you receive a translation task from a Office SharePoint Server 2007 site or from a Windows SharePoint Services 3.0 site. In this task, you change the workflow status to "In Progress." Then, you notice that the task status is unexpectedly set to "Completed" on the SharePoint site. In this scenario, you cannot complete the workflow of the task when the task status is set to "Completed" on the SharePoint site.
• In an Office SharePoint 2007 Collaboration Portal site, you create a workflow that has the Start this workflow when an item is changed check box selected and that has versioning enabled. When you do this, the status of the workflow is always "In Progress," and the content approval workflow is always "Pending," even after the workflow is approved.
  
  Note If only the Start this workflow when a new item is created check box is selected, this issue does not occur.
• Consider the following scenario:
  1. You add a text box to an InfoPath 2007 form.
  2. You select the Cannot be blank check box in the Tex Box Properties dialog box of the form.
  3. You publish the form to Forms Server 2007.
  4. You customize a Web page to use the XmlFormView ASP.NET control to display the form.
  5. You open the Web page in Internet Explorer.
  In this scenario, the Cannot be blank red asterisk may be displayed outside the text box.
• In Project Server 2007, you receive the following error message on the proposal page when you enter a text value into a custom cost field:
  Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints. Troubleshoot issues with Windows SharePoint Services.
• When you use a customized tool that is based on Project Server Interface (PSI) to change a task to 100 percent complete, the project start and finish dates are changed incorrectly.
  
• You create a project-level custom field that uses a formula. The formula contains more than two other custom fields. Then, you change the values of the custom fields in Project Web Access. In this scenario, the project-level custom field becomes blank when you publish the changes in Project Web Access.
  
  Note This issue occurs in the pure Korean version of a Project Server 2007 environment and the pure Japanese version of a Project Server 2007 environment.
• In Project Web Access, when you select a project on the Close Tasks to Update page, you receive a "System.OutOfMemoryException" message.
  
• In Project Web Access, if you select the Time entry by Timesheet only. Users will sync to update tasks check box on the Task Settings and Display page, you can make updates to the remaining work in the timesheet. However, you can no longer make any adjustments on the My Tasks page.
  
• The automated approval rule for task re-assignments does not run automatically. You have to manually run the rule.
  
• After one Active Directory directory service account is deleted from the domain controller, the Active Directory sync with Enterprise Resource Pool fails.
  
• If you enter a date on a timesheet that is outside the planned dates, the actuals are lost for the summary tasks when you import the timesheet on the My Tasks page.
  
• If you change a task that already has a baseline set, the time-phased baseline cost values are deleted from the project plan and from the Project Server database when the plan is re-published.
  
  This problem occurs only after you install hotfix 951169 or a Project Server 2007 hotfix that was released after hotfix 951169.
  
• You assign resources to a task that has notifications enabled. Then, you set the Publish column to No. When you save and publish the project plan, the resources receive a notification that they have a new task. However, they should not receive the notification because the task was not published to the Project Server.
  
• When you click Add Lines on the My Timesheet page, an unknown error occurs if a task has no name.
  
• In Project Center, if you want to use a currency symbol that is not a Windows standard, you must change the Windows Regional settings for the locale that is selected in the regional settings of the SharePoint site.
  
• When the default assignment owner reassigns a task, the task reassignment fails, and you receive the following error message:
  The update was not applied due to a conflict.
• If there are only task-level changes, a transaction is thrown away.
  
• Custom fields together with formulas are not available in the My Assignments view.
  

This hotfix also fixes the following issue:

• 955653  (http://support.microsoft.com/kb/955653/ ) You may experience poor performance when you use many SetCell calls in Excel Services

Known issue

Symptoms

After you apply this Cumulative Update, scheduled crawls (incremental or full) never run.

Workaround

Create or edit a daily, weekly, or monthly schedule as you typically would.

• If the Repeat within the day check box is selected, and you already have a repetition interval, you do not have to do anything
• If the Repeat within the day check box is not selected, follow these steps:
  1. Enter 5 minutes in the Run Every text box.
  2. Enter 6 minutes in the For text box.

How to obtain the cumulative update package for SharePoint Server 2007

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.

SharePoint Server 2007 hotfixes that are included in the cumulative update package for the SharePoint Server 2007

This cumulative update package contains all of the .msp files that we have released as hotfixes or as public updates that target SharePoint Server 2007.

Cumulative update package information

Prerequisites

There are no prerequisites for installing this cumulative update package.

Restart requirement

You do not have to restart the computer after you apply this cumulative update package unless there was already a restart pending.

Registry information

The installation of this cumulative update package does not require any registry changes. Individual fixes may use the registry to enable changes which can be found in their respective individual KB articles.

File information

This cumulative update package may not contain all the files that you must have to fully update a product to the latest build. This cumulative update package contains only the files that you must have to correct the issues that are listed in this article.

The global version of this cumulative update package uses a Microsoft Windows Installer package to install the cumulative update 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 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:

Coreserver-x-none.mspCoreservermui-en-us.mspDlc-x-none.mspDlcmui-en-us.mspIfswfe-x-none.mspLpsrvwfe-x-none.mspMsxml5s-x-none.mspPjsrvapp-x-none.mspPjsrvwfe-x-none.mspXlsrvapp-x-none.mspx64

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:

Coreserver-x-none.mspCoreservermui-en-us.mspDlc-x-none.mspDlcmui-en-us.mspIfswfe-x-none.mspLpsrvwfe-x-none.mspMsxml5s-x-none.mspPjsrvapp-x-none.mspPjsrvwfe-x-none.mspXlsrvapp-x-none.msp