Via the ECM Team and SharePoint Team Blog

SharePoint related Infrastructure updates are now available for download.

To understand the issues fixed in these releases please read the following blog posts.

Content Deployment and Infrastructure Update - ECM Team Blog

It is strongly recommended that you install Windows SharePoint Services 3.0 Service Pack 1 and Office Servers Service Pack 1 before installing the Infrastructure Update for Microsoft Office Servers (KB951297) and the Infrastructure Update for Windows SharePoint Services 3.0 (KB951695).

The installation process will incur server and farm downtime that you will need to plan for – updates should be installed on all servers in a farm. Please refer to the TechNet SharePoint Service Pack 1 deployment article.

 

The Infrastructure Update for Microsoft Office Servers (KB951297) applies to:

• Microsoft Office SharePoint Server 2007
• Microsoft Office Project Server 2007
• Microsoft Search Server 2008
• Microsoft Search Server 2008 Express

The Infrastructure Update for Windows SharePoint Services 3.0 (KB951695) applies to:

• Windows SharePoint Services 3.0

The Infrastructure Update for Microsoft Office Project 2007 (KB951547) applies to:

• Microsoft Office Project Professional 2007

Read the detailed post about the Infrastructure update on the SharePoint Team Blog.

Here is a summary of the Content Deployment issues addressed in the Infrastructure Update:

Incremental bug fixes:

• Incremental import can fail if a feature with a custom content type has been reactivated on the destination.
• Unpublished pages do not get unpublished on the destination.
• Reinheriting permissions on the source does not propagate incrementally.
• Deleting a permission level on the source causes a "Permission level cannot be found." exception during incremental import.
• Incremental behavior with the Recycle Bin improved. Incremental import fails with a "FatalError: You cannot perform this action on a checked out document." exception.
• "Violation of PRIMARY KEY constraint" error during export.
• Document "Title" field does not get deployed by incremental deployment in some cases.
• In some cases, making permissions changes on the source or destination will result in a "The specified name is already in use." error.
• Deleting or renaming an item then creating one with the same name causes incremental deployment to fail.
• Incremental deployment fails when pages have independent permission settings.
• Deleting a file and folder can cause incremental deployment to fail in some cases.

Other bug fixes:

• Removing a User from a group does not propagate to the destination during incremental deployment.
• Some source web settings related to search are not propagated to the destination.
• Content Deployment can time out incorrectly on large deployment jobs.
• Miscellaneous SQL deadlocks.
• Quick deployment jobs behave incorrectly when Variations is used.
• Quick deployment fails when pages are Quick Deployed while the Quick Deploy job is running.
• Running One-time jobs manually can fail.
• In some cases, a content deployment job can get stuck in a "Preparing" state forever.
• Deployment sometimes unghosts items that are ghosted on the source.
• Custom master page settings on the source are not propagated to the destination during deployment.
• Content deployment fails when compression is disabled.