HasMasterNCs Attributes for Server Objects in the Configuration Container May Become Damaged (314446)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
This article was previously published under Q314446 SYMPTOMS
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.CAUSE
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.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft 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:
Date Time Version Size File name
--------------------------------------------------------
21-Mar-2002 15:59 5.0.2195.4959 123,664 Adsldp.dll
29-Jan-2002 21:52 5.0.2195.4851 130,832 Adsldpc.dll
29-Jan-2002 21:52 5.0.2195.4016 62,736 Adsmsext.dll
21-Mar-2002 15:59 5.0.2195.5201 356,624 Advapi32.dll
21-Mar-2002 15:59 5.0.2195.4985 135,952 Dnsapi.dll
21-Mar-2002 15:59 5.0.2195.4985 95,504 Dnsrslvr.dll
21-Mar-2002 16:00 5.0.2195.5013 521,488 Instlsa5.dll
21-Mar-2002 15:59 5.0.2195.4951 145,680 Kdcsvc.dll
26-Nov-2001 21:33 5.0.2195.4680 199,440 Kerberos.dll
07-Feb-2002 16:35 5.0.2195.4914 71,024 Ksecdd.sys
14-Mar-2002 23:13 5.0.2195.5080 503,568 Lsasrv.dll
02-Mar-2002 18:32 5.0.2195.5013 33,552 Lsass.exe
07-Dec-2001 21:05 5.0.2195.4745 107,280 Msv1_0.dll
21-Mar-2002 15:59 5.0.2195.4917 306,960 Netapi32.dll
21-Mar-2002 15:59 5.0.2195.4979 360,208 Netlogon.dll
21-Mar-2002 15:59 5.0.2195.5204 917,264 Ntdsa.dll
21-Mar-2002 15:56 5.0.2195.5213 165,648 Ntdsutil.exe
21-Mar-2002 15:59 5.0.2195.5201 386,832 Samsrv.dll
29-Jan-2002 21:52 5.0.2195.4874 128,784 Scecli.dll
21-Mar-2002 15:59 5.0.2195.4968 299,792 Scesrv.dll
30-May-2001 05:03 5.0.2195.3649 3,584 Spmsg.dll
29-Jan-2002 21:52 5.0.2195.4600 48,400 W32time.dll
06-Nov-2001 16:43 5.0.2195.4600 56,592 W32tm.exe
21-Mar-2002 15:59 5.0.2195.5011 125,712 Wldap32.dll
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbWin2kSP4fix kbbug kbDirServices kbenv kbfix kbWin2000sp3fix KB314446 |
---|
|