CRS: Shrinking Content Forces CRS into a Recovery Loop

ID: Q179282

The information in this article applies to:

Microsoft Commercial Internet System version 1.0 - Microsoft Content Replication System
Microsoft Site Server version 2.0 - Microsoft Content Replication System

SYMPTOMS

Microsoft Content Replication System (CRS) appears to be stuck in a recovery loop causing replications to never complete.

CAUSE

If, between the time CRS first determines a file's attributes and CRS actually replicates the file, the file has been modified so that it is smaller, the destination computer will continue trying to receive the number of bytes equivalent to the original file size. When it doesn't receive the remaining bytes, CRS will wait the value of the ReceiveTimeout (default of 5 minutes) and go into recovery mode. This recovery will loop until the replication is stopped.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Commercial Internet System version 1.0 and Site Server version 2.0. This problem has been corrected in the latest U.S. Service Pack for Site Server 2.0 Service Pack 1. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

Additional query words: crs

Keywords          : kbbug2.00 
Version           : WINNT:1.0,2.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbfix

Last Reviewed: April 17, 1998