Hi,

I have to W2K3 domain controllers which haven't been used for a
while. When I tried using them today, I got some domain not found
errors on the clients. When I looked at the event logs on DC1, I saw
some 2042 and 1388 errors.

I tried to force replication between both DC1 and DC2 manually and it
failed.

Following http://technet.microsoft.com/en-us/l.../cc780362.aspx, I
went to DC1 and used repadmin /removelingeringobjects to clobber all
the directory partitions which were hosed.

I then went to the other DC and it was giving me target not found
errors when using /removelingeringobjects. Getting this error is a
mystery as I’m using repadmin /showrepl to get the target id in the
first place and then paste it into the command – I would think there’s
zero chance of fat fingering it then!

Afterwards, I rebooted both DCs and I was able to force replication
manually from one of the DCs and not the other.

Apparently, I've got some lingering objects on that second domain
controller even though I'm getting target not found errors. Short of
doing a demote and re-promote, is there anyway I can get both domain
controllers out of the tombstone state?

Suggestions are greatly appreciated.

Thanks!

Hello Adam,

Just to get you correct, 2DC's not running for a long time, but you have
still other DC's running in the domain? Then i would strongly recommend to
demote the 2 DC's and promote them again. This will save you a lot of work
and trouble for getting them back correctly to the domain.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hi,
>
> I have to W2K3 domain controllers which haven't been used for a while.
> When I tried using them today, I got some domain not found errors on
> the clients. When I looked at the event logs on DC1, I saw some 2042
> and 1388 errors.
>
> I tried to force replication between both DC1 and DC2 manually and it
> failed.
>
> Following http://technet.microsoft.com/en-us/l.../cc780362.aspx, I
> went to DC1 and used repadmin /removelingeringobjects to clobber all
> the directory partitions which were hosed.
>
> I then went to the other DC and it was giving me target not found
> errors when using /removelingeringobjects. Getting this error is a
> mystery as I’m using repadmin /showrepl to get the target id in the
> first place and then paste it into the command – I would think there’s
> zero chance of fat fingering it then!
>
> Afterwards, I rebooted both DCs and I was able to force replication
> manually from one of the DCs and not the other.
>
> Apparently, I've got some lingering objects on that second domain
> controller even though I'm getting target not found errors. Short of
> doing a demote and re-promote, is there anyway I can get both domain
> controllers out of the tombstone state?
>
> Suggestions are greatly appreciated.
>
> Thanks!
>

On Aug 11, 1:40*pm, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
> Hello Adam,
>
> Then i would strongly recommend to
> demote the 2 DC's and promote them again. This will save you a lot of work
> and trouble for getting them back correctly to the domain.

Thanks for the reply. That's a matter of perspective. If I could get
the lingering objects deleted off of DC2, like the technet article
says, then I'd be done... and done in a heck of a lot more time that
demote and re-promote.