Re: Replication problems

Kim,

Be careful when stating "the replication folder". This might confuse some
people.

There are two types of replication within Active Directory: AD Replication
(read: ntds.dit) and FRS (File Replication Services).

I am assuming that you did not use ntdsutil to move ntds.dit (typically
located in C:\Windows\NTDS) and everything with that *BUT* that you moved
FRS from the C:\ Drive to the D:\, correct? In doing so you used something
similar to this:

http://support.microsoft.com/kb/291823
http://www.ms-mvps.com/Windows/movefrsfolder1.htm

Thanks,

--
Cary W. Shultz
Roanoke, VA 24012

<kimsmith7752@xxxxxxxxx> wrote in message
news:1181559581.100201.199970@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jun 11, 6:27 am, "Jorge Silva" <jorgesilva...@xxxxxxxxxxx> wrote:
Hi Joao
Sounds like your DC failed to replicate whithin the Tombstonelifetime
period, generally the best option is to demote (perform metadata cleanup)
the LESS updated DC seize any fsmo roles helded by that DC and then using
the dcpromo /forceremoval switch take the AD off that DC and then add it
again the Domain as normal process. In future pay a litle more attention
to
the replication process ny monitring that operation(s).
also ahave a look
at:http://technet2.microsoft.com/windowsserver/en/library/34c15446-b47f-...

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"Joao Luis Rita" <JoaoLuisR...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
messagenews:86EE3538-F588-4F5B-A868-9D4CA07DF4DE@xxxxxxxxxxxxxxxx



Hello all

I need some ideas for the following problems.

We have 2 main Windows 2003 servers, PDC1 and PDC2 (service pack 1). A
few
days ago, the 2 servers apparently stopped replicating each other. Some
users
couldn't log in, others received messages stating their PC account
didn't
exist. I checked the users/computers listings on the servers and some
PCs
are
in PDC2 while not being in PDC1. I checked the event viewer: the
"directory
service" log is full of replication errors. All the errors fall in 3
events
IDs-1864, 2042, 2092. I've checked Technet, and all seem to point to
firewall
problems. However we have no firewall between these servers...

I've been forced to shutdown PDC2 to stop all these errors.
Unfortunately,
the person that usually handles these problems is on vacation, and
after
2mn
on the phone he said he may have to format/reinstall PDC2, when he
returns...

Anyone has any ideas about this? I'd like to avoid the whole
format/reinstall...

Any way we can maybe force a replication, using PDC1 as base (it seems
to
have the most updated listings)?- Hide quoted text -

- Show quoted text -

I was having a similar problem where my C: drive filled up and left
less than 600 mB of free space.
This DC was tombstoned for awhile before I started working here. I
just had to demote the DC and
clean up the C: drive to provide more space. The I had to do the
metadata cleanup first, then promote the box.
It still had some problems with low disk space on C: drive so I
changed the replication folder to D: which had tons of space and all
is well today.



.

Relevant Pages

  • Re: Database replicator
    ... Replication is the the exact copying of something, and it does not state implicitly if just a part or the whole is copied. ... Stating "it's a whole table or nothing" would indicate the latter, not the former, and I long ago stopped trying to think for others and try to interpret intent of what was meant, since I have found that my assumptions were sometimes wrong and it has cost me. ... Jonathan has clarified himself we are on the same page, ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Operations Master Replication Issue Event ID 13562
    ... my understanding of this issue is: The FRS replica fails ... and you cannot transfer the FSMO to another server. ... seize the FSMO roles to other domain controller and then refer to KB312862 ... >> This server and others are having problems with replication. ...
    (microsoft.public.win2000.active_directory)
  • RE: Replication works off and on after upgrading to 2003 from 2000 server?
    ... I understand the issue is that after upgrading your domain controller to ... FRS can not correctly resolve the DNS name for server 2 from server 1. ... unable to complete the RPC connection to a specific replication partner. ... Since FRS servers gather their replication topology information from their ...
    (microsoft.public.windows.server.migration)
  • Re: NtFrs Replication Errors for deleted link
    ... FRS relies on essential containers, objects, and attributes stored in Active ... Directory and replicated among domain controllers in a given domain. ... Want to learn more about Windows Server file and storage technologies? ... Replication Service while polling the Domain Controller ...
    (microsoft.public.windows.file_system)
  • re:DNS / Netlogon problem
    ... trouble enabling replication from CRCAD1 to CRCAD for ... FRS can not correctly resolve the DNS name ... Controllers. ... message indicating that the connection has been established. ...
    (microsoft.public.windows.server.dns)