CRS Can Lock Files Even When Folder Is Excluded

Last reviewed: February 27, 1998
Article ID: Q181830

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

An application that opens and closes the file with a write lock may fail when the Content Replication System (CRS) is running in the same folder.

CAUSE

The CRS locks all changed files in the configured folder hierarchy for a short time. This can be a problem if CRS is configured to run in Automatic mode, because it will always be running. Each time a file is closed, CRS will open the file to check whether it should be replicated. Excluding the folder does not change this behavior.

WORKAROUND

To work around this problem, create a folder structure that does not include any folders that potentially have locking conflicts.

STATUS

This is by design.

Additional query words: replicate MCIS
Keywords : kbbug2.00 ciscrs kbbug1.00
Version : WINNT:2.0
Platform : winnt
Hardware : ALPHA PPC x86
Issue type : kbprb
Solution Type : kbnofix

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: February 27, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.