• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 652
  • Last Modified:

NTDS Replication Error -- URGENT!

I'm receiving errors with regards to Active Directory. My C: drive became full on my server, and in order to enlarge the C: drive I will have to take the server down (this will need to be done off hours), so in the mean time I uninstalled some unnecessary applications (MS Office) and freed up over 1GB of space. I keep on receiving the following error messages in my Directory Service Event log:

3/19/2007      10:53:20 AM       
NTDS Replication      
Error      Replication       1480      
Replication error: The directory replication agent (DRA) couldn't update object CN={{USERNAME}},CN=Users,DC={{DOMAIN}},DC=com (GUID 3a14c5e4-b115-4ff5-b653-43f1d9f37a3b) on this system with changes which have been received from source server 86a15b08-4f93-413a-bc38-69bd58117c2a._msdcs.{{DOMAIN}}.com. The disk containing the database is full.

And the following error message in my DNS Event Log:
3/19/2007      8:26:15 AM      
Error      None      4015      
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The event data contains the error.

Can someone help me resolve these issues, are they inter-related?
  • 2
  • 2
1 Solution
maidstoneAuthor Commented:
I have two domain controllers (both running Windows 2000). This error message is appearing on the main dc. the second dc we recently migrated it to a virtual machine, probably around the same time as when this issue began to occur.
Kini pradeepIT Technology Senior ConsultantCommented:
what is the size of the Active directory database ?
that would be C;\winnt\ntds\Ntds.dit.
now boot in AD restore mode and perform the following steps to check the database integrity.
type ntdsutil files integrity.
if it completes without any errors reboot in the normal mode.
if it does return errors perform the semantic database analysis .
ntdsutil "sem d a" go
if any error detected then type
ntdsutil "sem d a" "go f"
and you might have to perform an offline defrag of the AD database.
also once you have booted in the normal mode make sure that the replication is working fine, if the Dc's are in the same site then check replication using the AD sites and services.
else use replmon.
can you also run Dcdiag /v and pipe it into a text file and please post the Dcdiag.

Note: please make sure that you have a good backup before performing the offline defrag and also maintain the original ntds.dit before replacing it with the defragged one.
maidstoneAuthor Commented:
Thanks for your response.
I was able to rectify this issue by rebooting my system and going into Directory Services Restore Mode and ensuring there was enough space on C:
Kini pradeepIT Technology Senior ConsultantCommented:
Np, YW
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now