An event ID 6002 that references Distributed File System replication is logged several times a day on a Windows Server 2003 R2-based computer

Symptoms

The following event ID 6002 that references Distributed File System replication (DFSR) is logged in the Application log several times a day on a Windows Server 2003 R2-based computer:

Event Type: Error
Event Source: DFSR
Event Category: None
Event ID: 6002
Date: Date
Time: Time
Computer: Computer_Name
Description: The DFS Replication service detected invalid msDFSR-Subscriber object data while polling for configuration information.
Additional Information:
Object DN: CN=2762160d-2aea-4aec-8076-635e0a33cd5c,CN=DFSR-LocalSettings,CN=KFS1,CN=Computers,D C=Domain_Name,DC=Root_Domain
Attribute Name: msDFSR-MemberReference
Domain Controller: Domain_Controller_Name.Domain_Name.Root_Domain
Polling Cycle: 60 minutes

Cause

This issue occurs because of an invalid DFSR object in the Active Directory directory service. Invalid DFSR objects can occur if you select the Delete the namespace folders and associated replicated folders option in the DFS Management snap-in. Because that option may cause objects that are orphaned in Active Directory, we recommend that you first delete the replication group from the DFS Replication node in DFS Management. Then, delete the DFS Namespace.


Resolution

Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.

To resolve this issue, remove the object that is the cause of the error by verifying DFS subscriptions. To do this, follow the steps in the "Connect to Active Directory" and "Remove the invalid object" sections.

Note These steps only resolve the issue in which an invalid object exists in the Active Directory directory. The steps do not resolve replication issues.

Connect to Active Directory

1. On a server that has the Windows Support Tools installed, open a command prompt. To download the Windows Server 2003 Support Tools, visit the following Microsoft Web site:
   http://www.microsoft.com/downloads/details.aspx?FamilyID=96a35011-fd83-419d-939b-9a772ea2df90&displaylang=en
2. Move to the Drive_Letter:\Program Files\Support Tools folder.
3. Type adsiedit.msc, and then press ENTER.
4. On the Action menu, click Connect to.
5. In the Connection Settings dialog box, type any name that you want to name this connection in the Name box.
6. In the Connection Point area, click Select a well known Naming Context, and then click Domain.
7. In the Computer area, click Select or type a domain or Server, and then type the fully qualified domain name (FQDN) of the server. Or, you can click Default (Domain or Server that you logged in to), if this option is appropriate for your situation.
8. Click OK.

Remove the invalid object

1. Expand Domain [Server_Name.Domain_Name.Root_Domain].
2. Expand DC=Domain_Name,DC=Root_Domain.
3. Expand CN=Computers.
4. Expand the node for the computer that is logging the errors. For example, expand CN=Computer_Name, where Computer_Name is the name of the server that is logging the errors.
5. Expand CN=DFSR-Local Settings.
6. Under the CN=DFSR-Local Settings node, click each object in the navigation pane until you see an object in the details pane that has a GUID that matches the one that you observed in the event log. For example, to match the event that is listed in the "Symptoms" section, you should see an object that has the following distinguished name:
   CN=2762160d-2aea-4aec-8076-635e0a33cd5c,CN=DFSR-LocalSettings,CN=Computer_Name,CN=Computers,DC=Domain_Name,DC=Root_Domain
7. Right-click the object that you identified in step 5, click Delete, and then click Yes.
8. Exit ADSI Edit.

From: http://support.microsoft.com/kb/953527