This article was previously published under Q314446
This article has been archived. It is offered "as is" and will no longer be updated.
The HasMasterNCs attributes for server objects in the configuration container may become damaged. Also, values for attributes of objects in an LDIFDE export may consist of seemingly random characters beginning with "REM9" instead of the expected LDAP object name.
This problem may occur after you rebuild a domain tree by using the same name as a recently-removed domain tree. This creates a problem if you use the name before the deletion of the original domain tree has had an opportunity to replicate to all domain controllers and global catalogs in the forest. When a cross ref object is created for the root of a new domain tree (dc=ntdev,dc=microsoft,dc=com is one tree, dc=tree,dc=net is another) it does not initially have a GUID in the ncname attribute. This symptom occurs if an ncname without a GUID replicates into a domain controller that already holds the domain with the same name.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later: