PDC Broken - 0x00002e2 After Updates. Need it Back

[JRA]

Morning all. Well this sucks. :/

 

Been so busy I've not even been close to fixing this (yes really that bad) but happened a couple of days ago.

 

HyperV guest but any backups restored with Veeam still give the same problem. DC won't boot normally and restarts to recovery options, gives 0x00002e2 error code.

 

Have tried THIS and similar but not gotten anywhere. Restored now to Monday night's unhappy backup for a 'clean' if broken tinker today.

 

Have two other DCs (one hardware one HyperV VM) but this one does all my Google stuff and runs about every useful scheduled task imaginable. Really really want it back.

 

Anyone got any ideas? :/

 

Thanks everyone...

[network41]

This seems a bit more detailed , possibly worth a try

 

https://ithinkvirtual.com/2017/11/12/fixing-a-corrupt-domain-controller-stop-code-0x00002e2/

[Domino]

A couple of things - restoring a DC when you've other working DCs is a monumentally bad idea. Best case scenario the restored DC will be isolated from replication, worst case you do damage to the working DCs. (unless there's a way to do a non-authoritative restore from the backup software. I still would avoid it wherever possible)

 

What state are things currently in now? and can you live without this DC (say if you could get any scripts used in the scheduled tasks from the HD)?

Edited November 21, 2019 by Domino

[JRA]

A couple of things - restoring a DC when you've other working DCs is a monumentally bad idea. Best case scenario the restored DC will be isolated from replication, worst case you do damage to the working DCs. (unless there's a way to do a non-authoritative restore from the backup software. I still would avoid it wherever possible)

 

What state are things currently in now? and can you live without this DC (say if you could get any scripts used in the scheduled tasks from the HD)?

 

Well, I ran the above thing and it looks like I'm now in "best case" - the DC is booted and is up but isn't replicating to the other two DCs, but the other two do seem to be replicating to each other.

 

The broke one (and PDC, Google bits and all on it) is called DC4 btw, DC3 (VM) and DC2 (HW) are the 'good' ones.

 

Anyone think of a good next step?

 

EDIT - I'd rather even demote the other two and re-promote them if this'll solve anything. That too much of a bodge even?

Edited November 21, 2019 by JRA

[Domino]

Are the remaining DCs Global Catalogs?

 

If you run "repadmin /options" on each what are the results?

[HPlum78]

https://www.microsoft.com/en-gb/download/details.aspx?id=30005

 

Download the replication graphical tool and see what it is saying, i am a PowerShell man myself but this is the best tool for the job. Let me know what its saying error wise/ follow what it tells you.

[JRA]

Afternoon everyone. First off, thanks all who chimed in and helped out! Think it's working now, or if not almost there.

 

Moved FSMO roles to another DC yesterday.

 

Demoted it and scrubbed metadata (ntdsutil) then reinstalled AD but that didn't seem to go smoothly - promoted ok (it didn't before metadata removal) but griped about not being successfully advertising as a DC.

 

Got THIS too and managed to fix it from that stage in the hugely technical way described somewhere of clicking the "promote..." thing in server manager a few times and restarting it a few times.

 

It's now back and seems fine! Changes replicate. Touching wood but all looks alright.

 

That sucked. Hold me... :/