Article ID: 268995 - View products that this article applies to.
This article was previously published under Q268995
This article has been archived. It is offered "as is" and will no longer be updated.
A Windows 2000 domain controller may stop responding (hang) while replicating schema updates to other domain controllers in the domain and log event ID 1153. This event states that a class identifier has a superclass that is invalid, for example:
Note that this problem can occur after you install Microsoft Exchange 2000 Server on the domain controller.
Event Type: Error
Event Source: NTDS General
Event Category: (9)
Event ID: 1153
Time: 1:24:10 PM
Class identifier 1285129064 (class name msExchRecipientPolicy) has an invalid superclass 1285129062. Inheritance ignored.
NOTE: On a Windows 2000-based domain controller, when you open the Active Directory Users and Computers snap-in, you may receive the following error message:
Naming information cannot be located because: the search failed to retrieve attributes from the database.
This problem occurs when a replication rule in the Ntdsa.dll code is changed to allow the replication of a class whose superclass has not yet replicated.
In versions of Windows 2000 before you apply this hotfix, the Ntdsa.dll file stopped replicating a class if a superclass did not replicate.
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 the Microsoft Knowledge Base:
260910The English-language version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
Date Time Version Size File name ------------------------------------------------------ 07/17/2000 06:24p 5.0.2195.2103 906,512 Ntdsa.dll 07/12/2000 08:01p 5.0.2195.2103 378,640 Samsrv.dll 01/25/01 2:24p 5.0.2195.2842 130,320 adsldpc.dll 01/25/01 2:24p 5.0.2195.2835 348,944 advapi32.dll 01/25/01 2:23p 5.0.2195.2816 502,032 instlsa5.dll 01/25/01 2:24p 5.0.2195.2842 140,560 kdcsvc.dll 01/17/01 1:17p 5.0.2195.2842 198,928 kerberos.dll 12/19/00 9:13p 5.0.2195.2808 69,456 ksecdd.sys 01/25/01 2:24p 5.0.2195.2816 484,112 lsasrv.dll 01/02/01 8:45a 5.0.2195.2816 33,552 lsass.exe 01/23/01 5:06p 5.0.2195.2850 108,816 msv1_0.dll 01/25/01 2:24p 5.0.2195.2844 912,656 ntdsa.dll 01/25/01 2:24p 5.0.2195.2780 363,280 samsrv.dll 01/15/01 9:39a 5.0.2195.3140 3,584 spmsg.dll
To work around this problem, demote the domain controller and then promote the domain controller.
Microsoft 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 2.
Contact us for more help
Connect with Answer Desk for expert help.