AD and DNS not working on 2003 R2 sp2 x86 server after power failure


Yesterday someone rebooted a windows 2003 R2 sp2 x86 DC by powering it off with the power button instead of restarting it gracefully.  Many of the services don't start on boot and even when they are started manually, AD and DNS are not working.  I am not really sure where to start.  Working on DNS or AD.  I had them reboot it again earlier today to see if that would help and during login a message was displayed "Active Directory is rebuilding indices.  Please Wait.... " I am guessing it was not completely successful.  There are no backups.  This system is old but still used for one application accessed via RDP for a small business.  

The DNS event log error is 4013 - The DNS server was unable to open the Active Directory.  The DNS server is configured to use active directory service information and cannot operate without access to the directory...

The Directory Services have a few errors:

Event ID: 1168 - Internal error an active directory error has occurred
Event ID 1824 - The intersite messaging service requested to perform an ldap bind operation.  The operation was unsuccessful

When I try to open ADUC I get the error "Naming information could not be located because the specified domain either does not exist or could not be contacted  Contact your system administrator to verify that your domain is properly configured and currently online.

It has been a while since I have had to troubleshoot these types of errors - and I am feeling a bit overwhelmed.  It may be I tell these folks to find someone else.  I have been the only tech they have used though for the past 18 years...boy, I am getting old!

If you have any advice, I would appreciate it.  I will continue to google these errors and try a few things.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

JohnBusiness Consultant (Owner)Commented:
You might consider doing the following:  Do a proper (graceful) shut down. Wait a minute. Then start it. Does it repair itself.

DO plan on replacing this server. It is dangerously unsafe if connected to the Internet.
oh, boy. that's a pickle.

Is this THE ONLY DC?

Do as suggested and let the server boot normally, shut down gracefully and start it up again. Do not do anything else for about an hour after it boots, then log in and see what's going on.

Do you have a virtual environment?

If anything, just spin up a new vm running Windows 2008 or higher and install the application that is used. You may be able to copy the information from the old server if you can reach via network share.
Hi, thanks for your responses yesterday, I ended up going through this article:

which may have helped but I ended up having to take an additional step listed in the article below:

All of the integrity checks, rebuilds, compactions passed with flying colors.  This is the bit that did the trick:

1. Open the registry editor by typing “regedit” in command prompt. Locate the path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcSs

2. Add a “Reg_Multi_Sz” with the name as “DependOnService” then add “Eventlog” to the data list “DependOnService”, close the registry and reboot the server in normal mode.

So, if I just added that tiny registry key would it have taken me 5 minutes to fix instead of 6 hours? MAYBE!  But, it was the needle in the haystack :)


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
BonnieKAuthor Commented:
Well, I didn't realize that I have 2 EE logins... so I am going to mark my solution as the one that fixed the others in case it can help anyone else - not trying to cheat and get points...

Hopefully there are not too many others still running 2003 R2 out there!
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 OS

From novice to tech pro — start learning today.