Cannot add a new DC to domain - error that changes must be made but whether they've been made is undetermined

I'm having trouble adding a new server to an AD domain.  There are four servers on the network, all are Windows 2003 Enterprise.  Two were domain controllers. One DC crashed.  All references to it were removed from AD and a new server was buit.  When trying to add it as a DC using dcpromo wizard we see:

The Wizard is configuring Active Directory
Located comain controller
Examining an existing Active Directory Forest

After a moment we get the error:
The operation failed because:  This Active Directory installation requires domain configuration changes, but whether these changes have been made on the domain controller is undetermined.  The installation process has quite.  "The system cannot find the file specified".

We though it might be because we named the replacement serve the same name as the one we removed.  So we renamed the server and tried again with the same results. This is after a fresh install on a blank drive on this server.  I assume there are some permission problems somewhere in AD, but have no way to verify this or know where to look.  Awhile back we made changes to some impersonation settings, but they should all be back where they belong.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Have you checked that all the fsmo roles are being recognised and held correctly?

Try running this from a command prompt

netdom query fsmo

It should correctly return five roles. If not you may have to seize them if any were held by the exstinct dc.
Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller

You should also check that dns is setup and functioning correctly -

Deb :)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Did the server that crashed hold any of your FSMO roles? You can check and see which server has the roles by following the steps in this article:

If the server that crashed was holding any of those roles you will need to seize them onto another DC. This article covers the steps you will need to go through to do that:;en-us;255504     (Scroll down to the "Seize FSMO roles" portion of the article)

Also, was server 1 the only Global catalog in the forest? If so you will want to make another server the global catalog by following the steps here:

Lastly, if the old DC crashed then it was not able to be gracefully removed from your AD metadata / schema. You can follow the steps in the following article to use ntdsutil to clean up and remove your old DC from the AD metadata:

Hopefully one of these solutions will help you out! Best of luck!

sorry about that Deb, didn't see that you already recomended seizing the FSMO roles, I forgot to refresh before posting :\

Starting with Angular 5

Learn the essential features and functions of the popular JavaScript framework for building mobile, desktop and web applications.

No probs - done it myself many many times ;-)
pcspcsAuthor Commented:
Wahoo!  Thank you Deb. Thank you thank you thank you!
Glad to help :))
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.