CRS: Automatic Mode Fails to Detect Corrupted Files

 Last reviewed: March 12, 1998
Article ID: Q177738
The information in this article applies to:
  • Microsoft Commercial Internet System 1.0
  • Microsoft Site Server 2.0

SYMPTOMS

Content Replication System (CRS) interprets corrupt files as files locked waiting for the copy to complete.

CAUSE

CRS uses ReadDirectoryW() to receive notifications from Windows NT when a files has been changed. This call will notify CRS about a change that has not yet completed. It will also notify CRS several times about the same file. As a result, CRS caches these entries for a period of time and then start transferring the data. To determine when the file is actually available for transfer, CRS does a "BusyFile" check by opening the file. Unfortunately, the Open call is failing because the file is corrupt and CRS is interpreting it as a large file that is locked pending completion of copy.

STATUS

Microsoft has confirmed this to be a problem in MCIS 1.0 and Site Server. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. 

Keywords          : kbusage kbbug2.00 ciscrs kbbug1.00
Version           : WinNT:1.0,2.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbpending

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

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