Target File Locked on Midpoint Prevents Updates from the Source

ID: Q237414

The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

Automatic projects never replicate the contents, and the checkpoints never check the file again to confirm whether it has been updated or not. For example, when you have a source-midpoint-endpoint configuration and you are replicating a file to the midpoint, if you update the file on the source computer as soon as it's done replicating to the midpoint, the file will be locked on the midpoint system, because the midpoint is attempting to replicate the file to the endpoint. When replication from the source to the midpoint occurs, this lock prevents the file from being updated, and further updates are not replicated to the endpoint. This can occur if the network link is slow, because the lock remains in effect while replication is taking place.

Furthermore, the midpoint system will have garbage located in the Crstemp directory that will accumulate while the system remains running. The following file will appear to accumulate:

\crstemp\projectdirname\99\99\file*


CAUSE

PerformMoveTransaction goes through the processing and fails. The routine that performs the MoveFileEx api returns that an ERROR_SHARING_VIOLATION and CRS_ERROR_FILE_MOVE_ERROR has occurred .


WORKAROUND

Updates to project files that are replicated from the source system to the midpoint system cannot occur while replication from the midpoint to the endpoint system is in progress. They must be scheduled synchronously, which typically occurs on a fast local area network (LAN), and thus prevents the problem.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Site Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

   Date      Time                 Size    File name     Platform
   -------------------------------------------------------------
   07/09/99  02:52p  7.0:908.0    457,840 Crsdll.dll    x86
   07/09/99  02:53p  7.0:908.0    754,960 Crsdll.dll    Alpha

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Site Server 3.0.


MORE INFORMATION

The Crs LockedFilesTimeout value is used as a global parameter that applies to all projects located on the system. The project level value will override the global value for the specific project if it is present. The value for LockedFilesTimeOut is read as a String. The fix now includes a 30 second retry period by default.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).


The Global Crs value is located in the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\CRS
Value: LockedFilesTimeOut: REG_SZ: 30000

The Project Specific Crs value is located in the following registry key:
Software\Microsoft\CRS\Projects\Test\LockedFilesTimeOut
Value: LockedFilesTimeOut: REG_SZ: 30000

By default, these values are set to 30000 milliseconds (30 seconds). You can add this value in the registry by adding the Global Crs value and setting it to a string of 60000. This will increase the timeout period to 60 seconds. If locked file symptoms are observed, this value can be increased on Site Server Content Deployment systems.

Summary of a CRS debug log from a midpoint system:
44/28/99 10:01:30 WRN 32 423 Moving c:\ProjectDir\CRSSRV.LOG to c:\CRSTemp\ProjectDir\00\01\0000007
4/28/99 10:01:30 WRN 32 423 MoveFileInternal @E:\inet2fre\pubsys\crs\crsdll\transact.cpp
The process cannot access the file because it is being used by another process.
4/28/99 10:01:30 WRN 32 423 PerformMoveTransaction @E:\inet2fre\pubsys\crs\crsdll\transact.cpp The process cannot access the file because it is being used by another process.
4/28/99 10:01:30 DBG 0 423 EVENT (15119): Failed to move file c:\CRSTemp\ProjectDir\00\03\0000006b.FIL to c:\ProjectDir\CRSSRV.LOG.

Additional query words: 


Keywords          : 
Version           : winnt:3.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: July 30, 1999