Active Directory is curropting

Z

zuhaib

Hi,
I have installed active directory on many servers and on
each server, about after 3 to 6 days, active directory
becomes curropt. Below are the messages that are displayed
in event log. Please advise.
Note: I have not integrated DNS with active directory,
also it is significant to note that the additional domain
controller is working fine and the above problem is
occurring on root domain controllers.

Thanx

---------------------------------------------------

vent Type: Error
Event Source: NTDS ISAM
Event Category: Database Page Cache
Event ID: 404
Date: 3/3/2004
Time: 8:07:27 AM
User: N/A
Computer: APPSRV07
Description:
NTDS (264) Synchronous read page checksum error -1018
((1:483 1:483) (0-145738) (0-209745)) occurred. Please
restore the databases from a previous backup.

-----------------------------------------------------------

Event Type: Error
Event Source: NTDS ISAM
Event Category: Online Defragmentation
Event ID: 705
Date: 3/3/2004
Time: 8:07:27 AM
User: N/A
Computer: APPSRV07
Description:
NTDS (264) Online defragmentation of
database 'C:\WINNT\NTDS\ntds.dit' terminated prematurely
after encountering unexpected error -1018. The next time
online defragmentation is started on this database, it
will resume from the point of interruption.

-----------------------------------------------------------

Event Type: Error
Event Source: NTDS General
Event Category: (18)
Event ID: 1126
Date: 3/3/2004
Time: 8:07:42 AM
User: Everyone
Computer: APPSRV07
Description:
Unable to establish connection with global catalog.

-----------------------------------------------------------

Event Type: Information
Event Source: NTDS KCC
Event Category: (1)
Event ID: 1308
Date: 3/3/2004
Time: 9:42:40 AM
User: N/A
Computer: APPSRV07
Description:
The Directory Service consistency checker has noticed that
2 successive replication attempts with CN=NTDS
Settings,CN=APPSRV04,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=pndy,DC=mil have failed
over a period of 63269 minutes. The connection object for
this server will be kept in place, and new temporary
connections will established to ensure that replication
continues. The Directory Service will continue to retry
replication with CN=NTDS
Settings,CN=APPSRV04,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=pndy,DC=mil; once
successful the temporary connection will be removed.

-----------------------------------------------------------

File replicaiton service Log

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 3/3/2004
Time: 9:41:13 AM
User: N/A
Computer: APPSRV07
Description:
The File Replication Service is having trouble enabling
replication from APPSRV04 to APPSRV07 for
c:\winnt\sysvol\domain using the DNS name
appsrv04.pndy.mil. FRS will keep retrying.
Following are some of the reasons you would see this
warning.

[1] FRS can not correctly resolve the DNS name
appsrv04.pndy.mil from this computer.
[2] FRS is not running on appsrv04.pndy.mil.
[3] The topology information in the Active Directory for
this replica has not yet replicated to all the Domain
Controllers.

This event log message will appear once per connection,
After the problem is fixed you will see another event log
message indicating that the connection has been
established.
Data:
0000: 00 00 00 00 ....

-----------------------------------------------------------

System Log

Event Type: Error
Event Source: SAM
Event Category: None
Event ID: 16650
Date: 3/3/2004
Time: 9:46:39 AM
User: N/A
Computer: APPSRV07
Description:
The account-identifier allocator failed to initialize
properly. The record data contains the NT error code that
caused the failure. Windows 2000 will retry the
initialization until it succeeds; until that time, account
creation will be denied on this Domain Controller. Please
look for other SAM event logs that may indicate the exact
reason for the failure.
Data:
0000: a7 02 00 c0 §..À
 
D

Don Hacherl [Msft]

You have an unreliable disk and/or disk controller. Checksums that were
passing when data was written to disk are failing when the data is being
read back. You should consult with your hardware supplier.

If it's still possible to recover the database (that is, if non-redundant
data has not already been lost) then you can do so by doing an offline
defrag. If the offline defrag fails with a -1018 error as well then you
will need to restore that DC from a backup.

--
Don Hacherl
Active Directory Development
This posting is provided "AS IS" with no warranties, and confers no rights.


Hi,
I have installed active directory on many servers and on
each server, about after 3 to 6 days, active directory
becomes curropt. Below are the messages that are displayed
in event log. Please advise.
Note: I have not integrated DNS with active directory,
also it is significant to note that the additional domain
controller is working fine and the above problem is
occurring on root domain controllers.

Thanx

---------------------------------------------------

vent Type: Error
Event Source: NTDS ISAM
Event Category: Database Page Cache
Event ID: 404
Date: 3/3/2004
Time: 8:07:27 AM
User: N/A
Computer: APPSRV07
Description:
NTDS (264) Synchronous read page checksum error -1018
((1:483 1:483) (0-145738) (0-209745)) occurred. Please
restore the databases from a previous backup.

-----------------------------------------------------------

Event Type: Error
Event Source: NTDS ISAM
Event Category: Online Defragmentation
Event ID: 705
Date: 3/3/2004
Time: 8:07:27 AM
User: N/A
Computer: APPSRV07
Description:
NTDS (264) Online defragmentation of
database 'C:\WINNT\NTDS\ntds.dit' terminated prematurely
after encountering unexpected error -1018. The next time
online defragmentation is started on this database, it
will resume from the point of interruption.

-----------------------------------------------------------

Event Type: Error
Event Source: NTDS General
Event Category: (18)
Event ID: 1126
Date: 3/3/2004
Time: 8:07:42 AM
User: Everyone
Computer: APPSRV07
Description:
Unable to establish connection with global catalog.

-----------------------------------------------------------

Event Type: Information
Event Source: NTDS KCC
Event Category: (1)
Event ID: 1308
Date: 3/3/2004
Time: 9:42:40 AM
User: N/A
Computer: APPSRV07
Description:
The Directory Service consistency checker has noticed that
2 successive replication attempts with CN=NTDS
Settings,CN=APPSRV04,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=pndy,DC=mil have failed
over a period of 63269 minutes. The connection object for
this server will be kept in place, and new temporary
connections will established to ensure that replication
continues. The Directory Service will continue to retry
replication with CN=NTDS
Settings,CN=APPSRV04,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=pndy,DC=mil; once
successful the temporary connection will be removed.

-----------------------------------------------------------

File replicaiton service Log

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 3/3/2004
Time: 9:41:13 AM
User: N/A
Computer: APPSRV07
Description:
The File Replication Service is having trouble enabling
replication from APPSRV04 to APPSRV07 for
c:\winnt\sysvol\domain using the DNS name
appsrv04.pndy.mil. FRS will keep retrying.
Following are some of the reasons you would see this
warning.

[1] FRS can not correctly resolve the DNS name
appsrv04.pndy.mil from this computer.
[2] FRS is not running on appsrv04.pndy.mil.
[3] The topology information in the Active Directory for
this replica has not yet replicated to all the Domain
Controllers.

This event log message will appear once per connection,
After the problem is fixed you will see another event log
message indicating that the connection has been
established.
Data:
0000: 00 00 00 00 ....

-----------------------------------------------------------

System Log

Event Type: Error
Event Source: SAM
Event Category: None
Event ID: 16650
Date: 3/3/2004
Time: 9:46:39 AM
User: N/A
Computer: APPSRV07
Description:
The account-identifier allocator failed to initialize
properly. The record data contains the NT error code that
caused the failure. Windows 2000 will retry the
initialization until it succeeds; until that time, account
creation will be denied on this Domain Controller. Please
look for other SAM event logs that may indicate the exact
reason for the failure.
Data:
0000: a7 02 00 c0 §..À
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Active directory problem 4
active directory replication not worked 4
Active Directory Replication Problem... 0
Active Directory Replication Oddity 1
Active Directory and DNS errors 11
AD Replication Problem 2
Active problem 3
NtFrs Conflict..........Help Please 0

Top