CRS: Shrinking Content Forces Content Replication System into a Recovery Loop
Article ID: 179282
Article Last Modified on 11/17/2003
APPLIES TO
- Microsoft Commercial Internet System 1.0 Service Pack 2
- Microsoft Content Replication System
- Microsoft Site Server 2.0 Standard Edition
This article was previously published under Q179282
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:
Additional query words: crs
Keywords: kbbug kbfix kbqfe KB179282