An Automatic Project Cannot Complete When You Delete a Directory Structure (297859)



The information in this article applies to:

  • Microsoft Site Server 3.0 Commerce Edition

This article was previously published under Q297859

SYMPTOMS

Content deployment projects that are configured for automatic replication may not complete and the following event may be logged that indicates that the project has stopped:
15166: The connection to server 1 for project 2 failed. Will attempt to reestablish session for 3 minutes.

CAUSE

This problem occurs because a child directory that is created as a file is not created in the correct sequence; therefore, it is not found during a recursive delete process.

WORKAROUND

To work around this problem, restart the project.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Site Server service pack that contains this hotfix.

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 about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Date         Time   Version     Size     File name   Platform
   -------------------------------------------------------------
   Apr-12-2001  11:29  7.0.1318.0  458,880  Crsdll.dll  x86
				

STATUS

Microsoft has confirmed that this is a problem in Site Server 3.0.

MORE INFORMATION

A zero byte file that represents a subdirectory may be observed on the endpoint system as a side effect of receiving the directory creation of parent directories following the creation of the child directory.

With the hotfix, CRS handles the failure and finds the subdirectory in this scenario. As a result, the recursive deletion successfully completes, and automatic replication can successfully continue.

The following information is a summary of the events that are involved in reproducing the problem on the endpoint system:

NOTE: A directory structure is replicated from the source system to the endpoint system.
   ...\test2
            \test3
                  ...
				
The following operations occur on the endpoint system:
  • Step 1: Test3 is created as a subdirectory.
  • Step 2: Test2 is created as a directory.
  • Step 3: Test3 is created as a zero byte file.
  • Step 4: The path for test3 was not found during the attempted directory deletion during the recursive delete.
NOTE: For additional information regarding these steps, refer to the Crssrv.log files
  1. DBG 0 108 PreReceiveFile on index 0 file ...\test2\test3, dwType 4, Attributes: 16, Size 0

    DBG 0 108 Created directory ...\test2\test3
  2. DBG 0 108 PreReceiveFile on index 0 file test1\test2, dwType 4, Attributes: 16

    DBG 0 108 Created directory ... \test1\test2

    .
  3. DBG 0 108 PreReceiveFile on index 0 file test1\test2\test3, dwType 0, Attributes: 0, Size 0

    DBG 0 108 Starting Scan on ...\test1\test2\test3
  4. DBG 0 108 Starting Scan on ...\test1\test2\test3

    WRN 3 108 Recursive Delete @e:\inet2fre\core\pubcore\pathname

    The system cannot find the path specified.
  5. DBG 0 230 Begun receiving file ...\test2\test3

Modification Type:MinorLast Reviewed:10/6/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB297859