Database Issues

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi
I;ve this error coming on to one of my ADC on win2k platform.Bcoz of this
replication is not happening between this and other ADC .Can anyone suggest
remedy for this.
Event Type: Error
Event Source: NTDS Replication
Event Category: (5)
Event ID: 1084
Date: 7/18/2006
Time: 5:53:26 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: INDELADC02
Description:
Replication error: The directory replication agent (DRA) couldn't update
object CN="DOD00001-134168
DEL:09c0b110-cb05-4263-9b57-ed8a7b941dc7",CN=Deleted
Objects,DC=mydomain,DC=com (GUID 09c0b110-cb05-4263-9b57-ed8a7b941dc7) on
this system with changes which have been received from source server
b1c08bb0-9fc3-40c5-acf2-140beca19df4._msdcs.mydomain.com. An error occurred
during the application of the changes to the directory database on this
system.

The error message is:
The replication operation encountered a database error.

The directory will try to update the object later on the next replication
cycle. Synchronization of this server with the source is effectively blocked
until the update problem is corrected.
If this condition appears to be related to a resource shortage, please stop
and restart this Windows Domain Controller.
If this condition is an internal error, a database error, or an object
relationship or constraint error, manual intervention will be required to
correct the database and allow the update to proceed. It is valuable to note
that the problem is caused by the fact that the change on the remote system
cannot be applied locally. Manually updating the objects on the local system
in not recommended. Instead, on the source system (which has the changes
already), try to reverse or back out the change. Then, on the next
replication cycle, observe whether the change can now be applied locally.
The record data is the status code.
Data:
0000: 03 21 00 00 .!..

Rajnish
 
It sounds like you have a corrupted AD partition on this DC or there was an
object deleted that some how was still in use.

Try repairing via the steps outlined in the link below.

http://support.microsoft.com/kb/837932/en-us

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi
Infact we have done this offline defragmaentation and recd this error.

Executing Command: C:\WINNT\system32\esentutl.exe /d
"C:\WINNT\NTDS\ntds.dit" /8
/o /l"C:\WINNT\NTDS" /s"C:\WINNT\NTDS" /t"d:\new\ntds.dit" /!10240 /p


Initiating DEFRAGMENTATION mode...
Database: C:\WINNT\NTDS\ntds.dit
Log files: C:\WINNT\NTDS
System files: C:\WINNT\NTDS
Temp. Database: d:\new\ntds.dit

Defragmentation Status ( % complete )

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
............................Operation terminated with error -1601
(JET
_errRecordNotFound, The key was not found) after 552.484 seconds.


Spawned Process Exit code 0xfffff9bf(-1601)

If compaction was successful you need to:
copy "d:\new\ntds.dit" to "C:\WINNT\NTDS\ntds.dit"
and delete the old log files:
del C:\WINNT\NTDS\*.log
file maintenance:
 
Is it possible for you to demote this dc and then repromote it? This may be
the simplest and easiest route.

You have to make sure you have other gc's online and I would gracefully
transfer and FSMO roles that reside on this dc.

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi
I don't have any issue with demoting it and promoting it.Only issue is it
holds DNS DHCP and operations Masters how to go abt it can u pl provide me
detailed steps to be taken in the regard will be helpful...

Rajnish
 
Well you can check out my website http://www.pbbergs.com
Select articles and then "Decommisssiong a DC" but that assumes that you
will be removing the machine.

I believe if you demote the dc it shouldn't effect dhcp ( I can't say
positive this is the case so you should back it up either way, this is
covered in my document) and if you have multiple dc's with AD integrated dns
just leave this alone. When you repromote the dns should come back with the
promotion. You don't have to remove the o/s you are just going to run
dcpromo to demote and dcpromo to promote. Just make sure when you repromote
that you validate that dns is up and running

The fsmo role movement is covered in KB 255960
You need to make sure you will have a GC available see KB 313994
If this DC is your License manager then you will have to reauthorize, you
have 90 day grace period to do this
If this is your only dns server then there is additional work hopefully
there are at least two and your clients point to both of them
If you end up moving your dhcp services make sure that any helper service
for dhcp points to the new location, but you shouldn't have to move this

Go over all of this carefully and take care to understand to it. I don't
know your environment and I don't know what your skill set is


--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top