Frame Mode Replications Go into Session Timeout

Last reviewed: March 6, 1998
Article ID: Q179280

The information in this article applies to:

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

SYMPTOMS

When you run Content Replication System (CRS) in frame mode, the following sequence of events may occur:

Transaction is created and transfer of file is started.
After losing connection with the source computer, the destination computer reports event 15162 in the event log:
```
      Waiting to abort project %projectname%
```
The source computer reports event 15163 in the event log after a five- minute delay:
```
      Resuming replication for project %projectname%
```

Source computer immediately recovers on first try and reports event 15166:

      The connection to server %servername% for project %projectname%
      failed. Will attempt to reestablish session for 30 minutes.

If multiple CRS projects are replicating, only one of the replications may report a problem. CRS continues to replicate other projects to the same computer , even while the five-minute ReceiveTimeout is being expired by the replication in question.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Commercial Internet Server 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          : kbother kbbug2.00 kbbug1.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.