Issue that the hotfix package fixes

This hotfix package fixes the following issue that was not previously documented in a Microsoft Knowledge Base article:

• When you run the "Source to Target" deployment job to deploy custom content on a Windows SharePoint Services 3.0 site, such as a document library, the deployment job is not completed successfully. Instead, you receive an error message that resembles the following error message:
  The file "http://tx1mr1d:91/Documents/test1.doc" is not checked out. You must first check out this document before making changes.
  
  at Microsoft.SharePoint.Library.SPRequest.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId, Boolean bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarProperties, Boolean bCheckOut, Boolean bCheckin, Boolean bMigration, Boolean bPublish)
  at Microsoft.SharePoint.SPListItem.AddOrUpdateItem(Boolean bAdd, Boolean bSystem, Boolean bPreserveItemVersion, Boolean bNoVersion, Boolean bMigration, Boolean bPublish, Boolean bCheckOut, Boolean bCheckin, Guid newGuidOnAdd, Int32& ulID, Object& objAttachmentNames, Object& objAttachmentContents, Boolean suppressAfterEvents)
  at Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration, Boolean bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin, Boolean suppressAfterEvents)
  at Microsoft.SharePoint.SPListItem.Update()
  at Microsoft.SharePoint.Deployment.ImportObjectManager.FixBrokenLookupInListItem(ListItemLookup brokenField)
  at Microsoft.SharePoint.Deployment.ImportObjectManager.FixBrokenLookup(DeploymentLookupField brokenField)
  at Microsoft.SharePoint.Deployment.ImportObjectManager.FixBrokenLookupsForObject(Guid sourceObjectId, Dictionary`2 brokenFieldMap)
  at Microsoft.SharePoint.Deployment.ImportObjectManager.FixBrokenLookupsForListItem(Guid sourceLookupItemId)
  at Microsoft.SharePoint.Deployment.ListItemSerializer.FixBrokenLookups(SPListItem listItem, SerializationInfoHelper infoHelper)
  at Microsoft.SharePoint.Deployment.ListItemSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
  at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType, Boolean isChildObject)
  at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope)
  at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)
  at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)
  at Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader)
  at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()
  at Microsoft.SharePoint.Deployment.SPImport.Run()
  
  date time Content deployment job 'Remote import job for job with sourceID = Source_ID' failed.The exception thrown was 'Microsoft.SharePoint.SPException' : 'The file "http://path/filename" is not checked out. You must first check out this document before making changes.'

A new operation has been added to the Stsadm.exe tool

Microsoft has added a new operation to repartition a site collection in a content database. This new operation is included in this hotfix package.

For more information about the new operation in the Stsadm.exe tool, 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.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

Post-installation information

After you apply this hotfix package, you must run the "SharePoint Products and Technologies Configuration Wizard." To do this, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.

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.

32-bit hotfix package

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

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 package

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

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