Shrinking Content Forces CRS Into A Recovery Loop

 Last reviewed: March 6, 1998
Article 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

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

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 6, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.