You are currently offline, waiting for your internet to reconnect

The ConflictAndDeleted folder size may exceed its configured limitation in Windows Server 2003

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

SYMPTOMS
In Windows Server 2003, the size of the ConflictAndDeleted folder may exceed its configured limitation. By default, the limitation of the ConflictAndDeleted folder is 660 megabytes (MB). When this problem occurs, the ConflictAndDeleted folder may exhaust available disk space on the volume on which the folder resides. Additionally, the Distributed File System (DFS) Replication service cannot replicate any files.
CAUSE
This problem occurs because the ConflictAndDeletedManifest.xml file is corrupted. This file stores information about the current contents of the ConflictAndDeleted folder. The DFS Replication service writes to the ConflictAndDeletedManifest.xml file when files are added or removed from the ConflictAndDeleted folder.
RESOLUTION
To resolve this problem, delete the contents of the ConflictAndDeleted folder and the ConflictAndDeletedManifest.xml file by using WMIC commands. To do this, dump the GUID of the replicated folder that contains the corrupted file.
  1. Dump the GUID of the Replicated Folders on the member that has the corrupted ConflictAndDeletedManifest.xml file. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. Type the following command at the command prompt:
      wmic /namespace:\\root\microsoftdfs path dfsrreplicatedfolderconfig get replicatedfolderguid,replicatedfoldername
      Note If you have not run a WMIC command on the server before, a short pause will occur while WMIC is installed.
    3. After you run the command, you will see output that is similar to the following:
      ReplicatedFolderGuidReplicatedFolderName
      BB42F08D-BEBC-4331-90E1-786F80CBA30BSampleFolder1
      DCC81DB4-F90F-4084-819F-A190B54C8FC2SampleFolder2
      D11358E6-CD3A-4B2D-8C4A-6A73A44CBF99SampleFolder3
      Locate the GUID of the replicated folder that contains the corrupted ConflictAndDeletedManifest.xml file.
  2. Delete the contents of the ConflictAndDeleted folder, including the ConflictAndDeletedManifest.xml file. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. Type the following command at the command prompt:
      wmic /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo where "replicatedfolderguid='<GUID>'" call cleanupconflictdirectory
      Note Replace <GUID> with the GUID of the replicated folder that has the problem. No other changes are necessary for this command.

      For example, if you need to fix the Replicated Folder "SampleFolder1" from step c, you would use the following command:
      wmic /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo where "replicatedfolderguid='BB42F08D-BEBC-4331-90E1-786F80CBA30B'" call cleanupconflictdirectory
      Depending on the size of the ConflictAndDeleted directory, this may take a few minutes. If no conflicts or deletions are occurring when you run the command, the ConflictAndDeleted directory will be empty and the ConflictAndDeletedManifest.xml will be deleted. If conflicts or deletions are occurring when you run the command, some files will remain in the ConflictAndDeleted folder, including the ConflictAndDeletedManifest.xml file. However, the size will be much smaller and the total size of the ConflictAndDeleted folder will be below the quota high water mark.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 951010 - Last Review: 10/22/2008 06:27:56 - Revision: 2.0

Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems, Microsoft Windows Server 2003, Datacenter x64 Edition, Microsoft Windows Server 2003, Enterprise x64 Edition, Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems, Microsoft Windows Server 2003, Standard x64 Edition, Microsoft Windows Server 2003, Standard Edition (32-bit x86)

  • kbexpertiseinter kbtshoot kbprb KB951010
Feedback
s"> e; " src="https://c1.microsoft.com/c.gif?DI=4050&did=1&t=">arClickTracking = 1; var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write(" var Route = "76500"; var Ctrl = ""; document.write(" 1&t=">