Content Publishing Directories on Destination Are Not Deleted When Using Filters

ID: Q235354

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

With Content Publishing, directories in a project destination that do not exist on a source are deleted when you use filters.


CAUSE

This behavior is by design.


WORKAROUND

To work around this problem, remove the filter.


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
   -------------------------------------------------------------
   05/21/99  06:59p               753,936 Crsdll.dll    Alpha
   07/02/98  03:27p                   913 Eula.txt      Alpha
   05/26/99  06:15p                   333 Readme.txt    Alpha
   01/27/99  02:56p                80,144 Update.exe    Alpha
   05/26/99  06:12p                 1,785 Update.inf    Alpha

   05/21/99  06:58p               457,328 Crsdll.dll    x86
   07/02/98  03:27p                   913 Eula.txt      x86
   05/26/99  06:15p                   333 Readme.txt    x86
   01/27/99  02:02p                62,544 Update.exe    x86
   05/26/99  06:12p                 1,785 Update.inf    x86

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

A registry parameter has been added to change the default behavior.

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).

  1. Start Registry Editor (Regedt32.exe).


  2. Locate the following key in the registry: 
    
   HKEY_LOCAL_MACHINE\software\microsoft\crs


  3. On the Edit menu, click Add Value, and then add the following registry value: 


    4. 
   Value Name: ForceDirectoryDeletion
   Data Type:  REG_DWORD
   Value:      0 or 1
  4. Quit Registry Editor.


If this key is set to 1, the default behavior is changed and the filters are ignored during the ProcessDirectory call so that directories are always deleted on the destination when they do not exist on the source. If the registry key is set to 0 (or does not exist) the default behavior is used.

Additional query words: 


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

Last Reviewed: July 2, 1999