Re: AD/AM Replication Problem

Tech-Archive recommends: Speed Up your PC by fixing your registry

Sorry for not specifying.. this is just a test environment. We have
the 2 ADAM servers replicating and are failovers so when this one
stopped, all of our applications then failed over to the other one
which is why it went unnoticed.

We had been testing migration loads early on so we had changed the
tombstone lifetime to something smaller so that as we loaded, deleted,
reloaded, etc. the deleted objects would get cleared out sooner but we
had not set this back to a reasonable number of days.

Once we realized we had not set the tombstone value back, we went ahead
and simply set it back to the standard value... the directories then
began replicating again and the errors went away. We decided to let it
run it's course and see if we encountered any problems before opting to
re-install ADAM and so far we have not seen any.

I'm not familiar with replication monitoring. Are you talking about
like using MOM?

Doug

Lee Flight wrote:
Hi

if you are using this configuration in production then I would open an
incident with Microsoft PSS to get help with this.

If this were a test environment I would be inclined to uninstall the ADAM
instance from the server that was stopped. Uninstalling should sort out the
fsmo roles for the configuration set and do the necessary tidying up. You
could then reinstall an ADAM instance on the server and join it to the
configuration set.

Is the server that was stopped simply a replication partner to act as
a backup? If it was in production I am a little surprised that you or
your client applications did not notice that it was down as it must have
been down for greater than the tombstone lifetime (assuming that
the default has not been changed to something much smaller).

When you have fixed the problem it might be a good idea to set up some
replication monitoring to check the health of your configuration set.

Lee Flight


"Doug" <kolpekdb@xxxxxxxxxxxx> wrote in message
news:1137706742.360215.285780@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We have 2 replicated ADAM servers in our environment and we recently
noticed that on one of the servers the ADAM instance had stopped so we
restarted it. We are now seeing replication errors on the server that
was up the entire time (see below). We see the three options but there
is much to know which is the best alternative. When we look at the
repadmin command it does not look like /removelingeringobjects is even
a valid argument.

Are we missing something?

Thanks

Event Type: Error
Event Source: ADAM [UIdP] Replication
Event Category: Replication
Event ID: 2042
Date: 1/12/2006
Time: 8:44:07 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: XXXXX
Description:
It has been too long since this directory server last replicated with
the following source directory server. The time between replications
with this source has exceeded the tombstone lifetime. Replication has
been stopped with this source.
The reason that replication is not allowed to continue is that the two
directory servers' views of deleted objects may now be different. The
source directory server may still have copies of objects that have been
deleted (and garbage collected) on this machine. If they were allowed
to replicate, the source machine might return objects which have
already been deleted.

The replication operation has failed.

User Action:

Determine which of the two directory servers is out of date. You have
three options:

1. Remove or reinstall the directory server(s) that are out of date.
2. Use the "repadmin /removelingeringobjects" tool to remove
inconsistent deleted objects and then resume replication.
3. Resume replication. Inconsistent deleted objects may be introduced.
You can continue replication by using the following registry key. Once
the systems replicate once, it is recommended that you remove the key
to reinstate the protection.
Registry Key:
HKLM\System\CurrentControlSet\Services\ADAM_UIdP\Parameters\Allow
Replication With Divergent and Corrupt Partner


.

Relevant Pages

  • Re: Creating a Computer Object in ADAM
    ... I've never replicated an ADAM ... Win 2003 server down to my instance, but fails from my XP instance ... 'The attempt to establish a replication link for the following writable ... Source directory service address: ...
    (microsoft.public.windows.server.active_directory)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Creating a Computer Object in ADAM
    ... Definitely have replication problems. ... The directory server has failed to update the host name and/or ports ... I can't seem to get connected to my local instance of ADAM running ... Running partition tests on: Schema ...
    (microsoft.public.windows.server.active_directory)