Target File Locked on Midpoint Prevents Updates from the Source (237414)


The information in this article applies to:

  • Microsoft Site Server 3.0
  • Microsoft Site Server 3.0 Commerce Edition
This article was previously published under Q237414
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

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 .

RESOLUTION

To resolve this problem, obtain the latest service pack for Site Server 3.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

219292 How to Obtain the Latest Site Server 3.0 Service Pack

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.

STATUS

This problem was first corrected in Site Server 3.0 Service Pack 3.

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: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.


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.


Modification Type:MinorLast Reviewed:9/22/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB237414
©2004 Microsoft Corporation. All rights reserved.