The delta file merge process fails when the "Enable binary differential replication" option is enabled in a System Center Configuration Manager 2007 SP2 environment


Consider the following scenario:

  • You create a package on a Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2) site server.

  • You click to select the Enable binary differential replication check box on the Data Source tab of the Properties dialog box for the package.

  • Some files in the package are larger than 4 gigabytes (GB).

In this scenario, the delta file merge process fails for the larger files. Additionally, an error message that resembles the following is logged in the Distmgr.log file:

Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER
merging temp-delta-00000c48-00000001.rdc to file_name SMS_DISTRIBUTION_MANAGER 
merging temp-delta-000012d4-00000000.rdc to file_name SMS_DISTRIBUTION_MANAGER 
Delta file size: 3110003835 SMS_DISTRIBUTION_MANAGER
Remote file size: 15671835836 SMS_DISTRIBUTION_MANAGER
Failed to set the file pointer to the end of the file. Error 87 SMS_DISTRIBUTION_MANAGER
Failed to copy new chunk of length 28901 from the delta file. Error code 0x80070057 SMS_DISTRIBUTION_MANAGER
Failed to copy chunks to temp file. Error code 0x80070057 SMS_DISTRIBUTION_MANAGER
UpdateStagedFile failed; 0x80070057 SMS_DISTRIBUTION_MANAGER
UpdateStagedFolderRdcW failed; 0x80070057 SMS_DISTRIBUTION_MANAGER
Cannot copy package package_name from file_name to file_path, Win32 Error = 0 SMS_DISTRIBUTION_MANAGER 
Failed to copy package package_name from file_name to MSWNET:["SMS_SITE=CEN"]file_path SMS_DISTRIBUTION_MANAGER 


This problem occurs because the distribution manager does not handle the file pointer for the end of the file (EOF) correctly for files that are larger than 4 GB.


To resolve this problem, install the following hotfix rollup package on the affected System Center Configuration Manager 2007 SP2 primary site server, secondary site server, and remote provider roles. The installation wizard for the package creates another package for clients. To deploy the package to all clients after you run the package on the primary site server, you have to create an advertisement.

Note The following hotfix package can be installed on a System Center Configuration Manager 2007 SP2 site server that is running an x86-based or x64-based version of an operating system:

For more information about how to deploy a hotfix package to the System Center Configuration Manager 2007 SP2 site server, click the following article number to view the article in the Microsoft Knowledge Base:

2477182 System Center Configuration Manager 2007 Hotfix Installation Guidance

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 the problem 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, go to the following Microsoft website: 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.


To apply this hotfix, you must have Service Pack 2 for System Center Configuration Manager 2007 installed.

Registry information

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

Restart information

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

Note We recommend that you close the Configuration Manager Administration Console before you install this hotfix package.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it 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.

File name

File version

File size























Not applicable




Not applicable


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


See the following topics on the Microsoft TechNet website:

About Binary Differential Replication

How to Modify a Package

Package Name Properties: Data Source Tab
See also the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!