Corrupted Active Directory Database On Windows Server 2003 Member Server
Posted on 2007-11-24
I have a client with an SBS 2003 server. It is running fine.
They also have another server running under the SBS domain server as a member server. It is running Windows Server 2003 Standard Edition. It is also running Windows Terminal Services in Application Mode, SQL Server 2005 Express, IIS and Canon Imageware document management. The member server has Active Directory installed and the AD database became corrupted this past week.
We have it booted in Safe Mode at this time. I tried to run NTDSUTIL integrity checks and tried to repair the corrupted database but I keep getting Jet Error -1018 (Verification Failures) - same problems with ESENTUTL.
Is there some way to copy the AD database from the PDC (SBS 2003 Premium) to the member server to restore the corrupted AD database?
If not, is AD necessary on the member server? Exchange is running on the PDC (as a matter of fact it is the only thing running on the PDC right now).
This is a critical problem - the client's entire business is down as a result since all of their apps run on the member server.
(By the way, I am in New York and the server is in Florida. I have remote access to the member server via RDP and to the PDC via RWW. I am a Microsoft MCP with a Network Infrastructure competency. There is a local consultant handling the problem but he has been unsuccessful in solving it as yet. My client requested my assistance in expediting a solution. I have a strong vested interest since I am the application developer/maintainer of the apps running on TS and IIS on the failed member server.)