CRS: CRS Locks Small Files When Network Fails in FastMode

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

SYMPTOMS

During a Content Replication System (CRS) replication, if there is a momentary network problem that causes the destination computer or source computer to not see the other computer, CRS will not release the lock on the file or files being replicated. When you go to the source or destination and check the file, it is in use by the CRS service.

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:

SERVPACK

MORE INFORMATION

When a connection is ended in framed mode, the file on which the connection ended is left in the transaction log. When the connection is reestablished, a second file is created with valid content. This has the a side effect of creating two transactions for the same file and making the file counters off by the number of files that it had problems transmitting. However, all of the content is correct, and rollbacks are reserved correctly.

Additional query words:

Keywords : kbbug2.00
Version : winnt:1.0,2.0
Platform : winnt
Issue type : kbbug