The following entries are logged in the Directory Service event log:
Type: Warning
Source: NTDS General
Category: Internal Processing
Event ID: 2066
User: NT AUTHORITY\ANONYMOUS LOGON
Description: Active Directory encountered a failure while attempting to rebuild the quota-tracking
table in the background. Another attempt to resume rebuilding of the quota-tracking table
will be made in %4 seconds.
Additional data:
Error value:
1004 (0x3ec)
JET_wrnColumnNull, Column is NULL-valued
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Type: Error
Source: NTDS General
Category: Internal Processing
Event ID: 1168
User: NT AUTHORITY\ANONYMOUS LOGON
Description: Error 1004(3ec) has occurred (Internal ID 3370c3b).
Please contact Microsoft Product Support Services for assistance.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Type: Error
Source: NTDS General
Category: Internal Processing
Event ID: 1168
User: NT AUTHORITY\ANONYMOUS LOGON
Description: Error 1004(3ec) has occurred (Internal ID 801b6).
Please contact Microsoft Product Support Services for assistance.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The
NTDS dump file (
ntds.dmp) file may contain an entry similar
to:
An online database dump of the NTDS.DIT database for the DC showed the offending object as Bad,
User (see below for details). This object, as you can see below, has NULL ("-") in the 4th column.
The 4th. column is the NCDNT column which references the partition to which the object belongs.
Good, User on the other hand, has an NCDNT value of 3617 which mean it belong to NC whose value is 3617.
9657 7821 52 3617 true - - 3 Good, User Good, User - 655369 893f89cf-09a7-4781-9321-5ff8a65e1bc5 0114253 8981 1 - true - - 3 Bad, User Bad, User - 655369 00dfbaf1-1548-49fe-b4fa-d29b44a76c17 0
This problem is the result of a corrupted NTDS.DIT database on a Windows Server 2003 domain controller
that is configured as a global catalog server.
To resolve this problem, remove the global catalog role from its' computer and reinstall the global catalog role:
See How do I create or move a Global Catalog?
