Content Deployment Shutdown During Replication Causes File Corruption

• Microsoft Site Server version 3.0

SYMPTOMS

Content Deployment may produce file corruption on the end-point server if the source server fails during replication. When large files are being replicated and the source server fails in the process of replicating this file, the replicated file is copied to the destination directory when the system is restarted. However, the size of the destination file does not match the source file size.

CAUSE

During the file copy, the destination computer contains a partially copied file in the Crstemp directory. The file remains in this directory when the source Content Deployment server is shut down. When the source server is restarted, the source Content Deployment server completes the project. This results in the partially-copied file being approved by the source and the file placed on the destination computer as a partial file.

RESOLUTION

To resolve this problem, obtain the latest service pack for Site Server 3.0. For additional information, please see the following article in the Microsoft Knowledge Base:

Q219292 How to Obtain the Latest Site Server 3.0 Service Pack

STATUS

This problem was first corrected in Site Server 3.0 Service Pack 3.

MORE INFORMATION

Content Deployment has been modified so that the saved information stored in the package file is used to validate the final attributes, including the size of the valid end-point file, as opposed to referring to the resulting file attributes. As a result, if a corrupt or partial file is detected, replication is initiated and the file is copied successfully.

Additional query words:

Keywords : SS3SP3Fix
Version : winnt:3.0
Platform : winnt
Issue type : kbbug