RE: Replication error
- From: rsys <rsys@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 22 Mar 2007 08:42:13 -0700
thanks, I also felt reinstalling the server may be the easiest option.
The admin at the remote site ran dcpromo on the problematic server, and
removed (demoted) AD from the server. Then he reinstalled the server (OS)
with the same name (same machine) and now the next step is running dcpromo on
the server to make into a DC again.
At this stage, when I look at Active Directory Sites and Services (from
other working DCs), I still see the problem DC listed under 'servers'. But
when I double-click on it, it doesn't show any NTDS settings underneath. I
hope this ok.
Now, I will go ahead & do dcpromo on it. Please let me know if I am on the
right track..or if I missed anything.
Thanks, again.
"DanJ" wrote:
Hi,.
There are a couple of Knowledgebase articles that may be of use... although
you may have already seen them:
http://support.microsoft.com/kb/317097/en-us
http://support.microsoft.com/kb/285858/en-us
I'm not sure if you've already seen these... so you might find that they're
no good at all. Does the Server perform any other task other than DC? If it
doesn't serve any other critical services and/or you can afford downtime,
removing Directory Services (DCPROMO) may be an option, then promote the
server to Domain Controller Status again (DCPROMO) may be an option.
One point to note though... if the DCPROMO to remove Directory Services
(Demotion) fails, then you may need to the take the server off the network,
perform a DCPROMO /FORCEREMOVAL, then clean up the entries in the existing
directory service (including a possible metadata cleanup)... then after all
that, promote the server again.
Sorry this is long winded... others may have better suggestions, but after
many failed attempts at fixing a similar problem, removing Directory Services
worked for me on one particular server.
Cheers
Dan
MCSE, MCSA, CNA
"rsys" wrote:
hi,
Windows 2000 AD, with 4 DCs. Two of them running Windows 2000 server SP4 and
two other running windows 2000 advanced server SP4. The problem is there in
one of the advanced servers.
There is a replication error in one of the DCs, event ID 1084, which is
preventing successful replication.
Replication error: The directory replication agent (DRA) couldn't update
object CN="FF045B48C7EC4DD89FE41C4F08406F4FD80D547A155411DB9C9C000272B009F9
DEL:9974fc42-38f1-47bd-bf4d-5db6e274c211",CN=Deleted
Objects,DC=company,DC=net (GUID 9974fc42-38f1-47bd-bf4d-5db6e274c211) on this
system with changes which have been received from source server
49677cba-57e6-4315-99ba-56c3700992bd._msdcs.company.net. 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.
From my side, I did the following.
Used ldp on the server which has the problem, and searched for the GUID
mentioned in the error. But it is unable to find any match for this GUID. I
also did this on the source server mentioned above, but still no match.
I checked, and double-checked all the ldp syntax, so that part is correct
for sure.
What did I miss? How else can I possibly resolve this error? Incidentally
this error is there in only one DC, all other DCs are just fine.
As always, Thanks a lot for all your help!
- Prev by Date: Re: Local admin through group policy and keep admin on local machine?
- Next by Date: Re: Design OU & Group structure for University Environment
- Previous by thread: Design OU & Group structure for University Environment
- Next by thread: Replication Error
- Index(es):
Relevant Pages
|
