Errors in Directory Service Event Viewer
- From: "Matthew Clark" <MD-Clark@xxxxxxx>
- Date: Tue, 2 Aug 2005 11:51:08 -0500
We have 1 domain located in 2 sites (In location and AD). In one site, we
are getting many errors in the Directory Service Event log. I have been
doing Google searches and not come up with any concrete fixes or
explinations. Does anyone have any suggestions for me? Here are a few of
the errors... Thanks in advance...
Event Type: Error
Event Source: NTDS ISAM
Event Category: Database Page Cache
Event ID: 474
Date: 8/2/2005
Time: 11:19:34 AM
User: N/A
Computer: XXXXXXXXXXXXXX
Description:
NTDS (720) NTDSA: The database page read from the file "E:\NTDS\ntds.dit" at
offset 106405888 (0x000000000657a000) for 8192 (0x00002000) bytes failed
verification due to a page checksum mismatch. The expected checksum was
1790885907 (0x6abec013) and the actual checksum was 1212292351 (0x48421cff).
The read operation will fail with error -1018 (0xfffffc06). If this
condition persists then please restore the database from a previous backup.
This problem is likely due to faulty hardware. Please contact your hardware
vendor for further assistance diagnosing the problem.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 8/2/2005
Time: 11:09:32 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: XXXXXXXXXXXXX
Description:
The Knowledge Consistency Checker (KCC) has detected problems with the
following directory partition.
Directory partition:
DC=ad,DC=XYX,DC=eXYX
There is insufficient site connectivity information in Active Directory
Sites and Services for the KCC to create a spanning tree replication
topology. Or, one or more domain controllers with this directory partition
are unable to replicate the directory partition information. This is
probably due to inaccessible domain controllers.
User Action
Use Active Directory Sites and Services to perform one of the following
actions:
- Publish sufficient site connectivity information so that the KCC can
determine a route by which this directory partition can reach this site.
This is the preferred option.
- Add a Connection object to a domain controller that contains the directory
partition in this site from a domain controller that contains the same
directory partition in another site.
If neither of the Active Directory Sites and Services tasks correct this
condition, see previous events logged by the KCC that identify the
inaccessible domain controllers.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 2108
Date: 8/2/2005
Time: 11:12:04 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: XXXXXXXXXXXXXXXXXXx
Description:
This event contains REPAIR PROCEDURES for the 1084 event which has
previously been logged. This message indicates a specific issue with the
consistency of the Active Directory database on this replication
destination. A database error occurred while applying replicated changes to
the following object. The database had unexpected contents, preventing the
change from being made.
Object:
CN=USER1,OU=STUDENTS,OU=XYX,DC=ad,DC=XYX,DC=XYX
Object GUID:
1f739ca6-0dd5-4976-9f1f-e0eedd2a41b0
Source domain controller:
ed129500-dc01-4178-b091-06f1b34cac5e._msdcs.ad.wiu.edu
User Action
Please consult KB article 837932, http://support.microsoft.com/?id=837932.
A subset of its repair procedures are listed here.
1. Confirm that sufficient free disk space resides on the volumes hosting
the Active Directory database then retry the operation. Confirm that the
physical drives hosting the NTDS.DIT and log files do not reside on drives
where NTFS compression is enabled. Also check for anti-virus software
accessing these volumes.
2. It may be of benefit to force the Security Descriptor Propagator to
rebuild the object container ancestry in the database. This may be done by
following the instructions in KB article 251343,
http://support.microsoft.com/?id=251343.
3. The problem may be related to the object's parent on this domain
controller. On the source domain controller, move the object to have a
different parent.
4. If this machine is a global catalog and the error occurs in one of the
read-only partitions, you should demote the machine as a global catalog
using the Global Catalog checkbox in the Sites & Services user interface.
If the error is occurring in an application partition, you can stop the
application partition from being hosted on this replica. This may be changed
using the ntdsutil.exe command.
5. Obtain the most recent ntdsutil.exe by installing the latest service
pack for your operating system. Prior to booting into Directory Services
Restore Mode (DSRM), verify that the DSRM password is known. Otherwise reset
it prior to restarting the system.
6. In DSRM, run the NT CMD prompt, run "ntdsutil files integrity". If
corruption is found and other replicas exist, then demote replica and check
your hardware. If no replicas are present, restore a system state backup and
repeat this verification.
7. Perform an offline defragmentation using the "ntdsutil files compact"
function.
8. The "ntdsutil semantic database analysis" should also be performed. If
errors are found, they may be corrected using the "go fixup" function. Note
that this should not be confused with the database maintenance function
called "ESE repair", which should not be used, since it causes data loss for
Active Directory Databases.
If none of these actions succeed and the replication error continues, you
should demote this domain controller and promote it again.
Additional Data
Primary Error value:
1127 While accessing the hard disk, a disk operation failed even after
retries.
Secondary Error value:
-1018 JET_errReadVerifyFailure, Checksum error on a database page
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
.
- Follow-Ups:
- Re: Errors in Directory Service Event Viewer
- From: SIME U via WinServerKB.com
- Re: Errors in Directory Service Event Viewer
- Prev by Date: Re: Second DC
- Next by Date: RE: GP won't apply
- Previous by thread: Combine multiple forests into one single forest???
- Next by thread: Re: Errors in Directory Service Event Viewer
- Index(es):
Relevant Pages
|