Open Software Solutions

On a Windows Server 2008-based computer, when you try to browse a DFS namespace from the DFS Management Tool, the operation may fail. Additionally, you receive the following error message:

When this issue occurs, event 14547 is logged in the event log:

Log Name: System
Source: Microsoft-Windows-DfsSvc
Event ID: 14547
User: N/A
Computer: computer name
Description: A Distributed File System (DFS) folder was created with conflicting descriptions. This can occur if two administrators on different namespace servers create conflicting folder structures at approximately the same time. Namespace: domainname public1 DFS folder path: test2 .DFSFolderLink DFS folder 1: link-017c585e-18bc-4412-bd11-15bb1f982e32 DFS folder 2: link-3ab25a17-d094-4979-8b66-e1c59e553d36

This event means that on the namespace domianname public1, two DFS folders were created that have the name test2.

The DFS folder 1 identification information is link-017c585e-18bc-4412-bd11-15bb1f982e32.

The DFS folder 2 identification information is link-3ab25a17-d094-4979-8b66-e1c59e553d36.

This issue occurs when two administrators on different namespace servers create a DFS folder that has the same name. In this case, you have to determine which folder you want to delete.

To resolve this issue, follow these steps:

1. On the server that holds the primary domain controller (PDC) role, start Active Directory Service Interfaces (ADSI) Editor. To do this, click Start, click Run, and then type Adsiedit.msc.
2. In ADSI Editor, connect to the default naming context.
3. Under the domain name, expand CN=System, expand CN=DFS-Configurations, and then expand the DFS Namespace that is specified in the event log.
4. Double-click the DFS Namespace. This time, you will see the DFS folders that are listed in the event log in the right pane of the ADSI Editor. These folders are distinguished by their GUIDs in the following format:
   link-GUID

   Examples:
   link-017c585e-18bc-4412-bd11-15bb1f982e32
   link-3ab25a17-d094-4979-8b66-e1c59e553d36

5. Delete one of the folders.
6. If this issue still exists, restart the DFS service on the DFS member server. Then, try to access the DFS namespace from the DFS management Tool.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.