Event 2095 USN Rollback caused broken replication

  • Thread starter Alexander V. Alexeev
  • Start date
A

Alexander V. Alexeev

Hi all,

On our network has two DCs - Win 2000 Server SP4 + the rollup. One of them
carries all FSMO roles and is a PDC emulator. The other one is just a DC and
has also got a DNS. So there're two DNSs, both AD integrated.

Since promotion of the second DC, it replicated okay but after a few mins it
failed to do so. Logged the 2095 event and NTDS log msgs appeared saying
that inbound and outbound replications have been disabled. DCDIAG suggested
I ran the repadmin /ooption servername -disable_outbound_repl thing - I did
so on the PDC. Went ok. But when I try to manually replicate, it reverts to
disabled state.

I have tried replmon, repadmin, AD Site and Services - to initiate the
replication - and all I got is an error saying that the server denied
replication request.

The problem described in the following KB article is what I seem to be
having:
http://support.microsoft.com/default.aspx?scid=kb;en-us;885875

However, I am unable to follow their suggestion, as without the replication
functioning DCPROMO refuses to run on the offending DC.

I realise that my course of action now would be to demote that DC, get its
metadata cleaned from AD, if any left...
http://support.microsoft.com/kb/216498/en-us - hopes for this article. Then
attempt to promote it back.

Any suggestions on how to attempt to get the replication going?
Thank you!

Regards
Alex Alexeev
 
J

Jorge_de_Almeida_Pinto

Hi all,

On our network has two DCs - Win 2000 Server SP4 + the rollup.
One of them
carries all FSMO roles and is a PDC emulator. The other one is
just a DC and
has also got a DNS. So there're two DNSs, both AD integrated.

Since promotion of the second DC, it replicated okay but after
a few mins it
failed to do so. Logged the 2095 event and NTDS log msgs
appeared saying
that inbound and outbound replications have been disabled.
DCDIAG suggested
I ran the repadmin /ooption servername -disable_outbound_repl
thing - I did
so on the PDC. Went ok. But when I try to manually replicate,
it reverts to
disabled state.

I have tried replmon, repadmin, AD Site and Services - to
initiate the
replication - and all I got is an error saying that the server
denied
replication request.

The problem described in the following KB article is what I
seem to be
having:
http://support.microsoft.com/default.aspx?scid=kb;en-us;885875

However, I am unable to follow their suggestion, as without
the replication
functioning DCPROMO refuses to run on the offending DC.

I realise that my course of action now would be to demote that
DC, get its
metadata cleaned from AD, if any left...
http://support.microsoft.com/kb/216498/en-us - hopes for this
article. Then
attempt to promote it back.

Any suggestions on how to attempt to get the replication
going?
Thank you!

Regards
Alex Alexeev

If it is like you say you need to demote the offending DC. You can
also use DCPROMO /FORCEREMOVAL to force the demotion and then cleanup
its metadata.

These things can happen when imaging DCs and restoring the images or
restoring snapshots from DCs in a virtual environment like Virtual
PC/server and Vmware
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top