I have followed the troubleshooting steps in the Knowledge Base article
258062 and the good news appears to be that the NTDSUTIL reports that
directory database is consistent. The bad news is that it seems that the
edb.log file is corrupt.
I tried to perform an offline defragmentation using NTDSUTIL and it failed
with a Jet error -501. The error messages lin the event viewer look similar
to the following:
Event Type: Error
Event Source: NTDS ISAM
Event Category: Logging/Recovery
Event ID: 465
User: N/A
Computer:
Description:
NTDS (532) NTDSA: Corruption was detected during soft recovery in logfile
E:\WINDOWS\NTDS\edb.log. The failing checksum record is located at position
END. Data not matching the log-file fill pattern first appeared in sector
xxxx. This logfile has been damaged and is unusable.
For more information, see Help and Support Center
There is not another domain controller in the domain and there is not a
recent system state backup. (The donated server we were using for backups
across the network fell over a few months ago. These are the challenges of
trying to keep a network running on a near-zero budget).
So my questions are simple -
1) Should I proceed with a lossy recovery of Active Directory as suggested
in KB 258062?
2) Given the error messages above, is a lossy recovery even likely to work?
3) If the lossy recovery option does not work, do I have any other option
apart from a total rebuild ?
Any help or suggestions would be greatly appreciated.
Thanks
I'd try so.
> 2) Given the error messages above, is a lossy recovery even likely to work?
You could try to fix the log file with eseutil as far as I know. Chances
are you get it working.
> 3) If the lossy recovery option does not work, do I have any other option
> apart from a total rebuild ?
As long as the DC doesn't boot correctly, you don't have any.
This is why MSFT recommends having two DCs per domain. Even if the
second DC is a virtual machine on some other server - corruptions and
failures like these can be recovered easier. I don' understand why you
just didn't backup the directory somewhere else. The server has ntbackup
loaded - you could simply have backed up the systemstate to disk and
burn it on CD. Ten minutes of work, a blank DVD (worth $2) and way less
pain.
Cheers,
Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste
The article is in the moment the best/only solution, i can see.
If you do not have a backup from system state and can repair the machine
to start i think you have to rebuild. I do not see another option.
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
--
piyush1414
------------------------------------------------------------------------
piyush1414's Profile: http://forums.techarena.in/members/77193.htm
View this thread: http://forums.techarena.in/active-directory/1117904.htm
Download the software from here http://www.edbrepair.org/
If you followed the posting it states about AD database instead of Exchange.
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
> Repair your edb file using 'edb repair' (http://www.edbrepair.org/)
> tool. download the software from here http://www.edbrepair.org/
>
If you followed the posting it states about AD database instead of Exchange.
Best regards
Meinolf Weber [MVP-DS] wrote:
> If you followed the posting it states about AD database instead of
> Exchange.
Exchange and AD use the same database behind: ESE ;-) In fact, MS
developed ESE for Exchange before the directory services folks took a
build wrapped their code around it.
So if it's good for ESE, you can use it for both Exchange and AD (in
general). Although I would not use a third party tool to mess with a
critical database like that. There's not much info on ESE and MS has a
lot of good tools on their own.
F.
Thanks for the clarification, i thought that are different databases with
the same format name.
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
You need to repair edb file to recover corrupted edb log files. It is
good to choose the option of 'edb repair '
(http://www.edb-repair.com/)other than any one else. Stellar Phoenix
Exchange Server Recovery Software is the powerful and efficient software
for edb repair. This application is the primary need to all the business
as of its promising, fast, versatile and exact recovery options. It
extracts all the mailboxes, repair and converts it in to PST format.
Hence you can further use it with MS Outlook.
--
JNPT
------------------------------------------------------------------------
JNPT's Profile: http://forums.techarena.in/members/126684.htm