Re: ebd.log corrupted
- From: Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de>
- Date: Fri, 3 Apr 2009 20:27:38 +0000 (UTC)
Hello http:www.repairpst.info,
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
You can repair your corrupted EDB file. Using Edb Repair Tool
Download the software from here http://www.edbrepair.org/
...
http://www.edbrepair.org/
"Meinolf Weber [MVP-DS]" wrote:
Hello Minimbah,
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
Hi all,
I manage the single SBS 2003 server at a small charity on a pro bono
basis.
We have had a serious problem with Active Directory. When the
system
starts
up the following error message appears:
LSASS.EXE - System Error, security accounts manager initialization
failed
because of the following error: Directory Services cannot start.
Error
status 0xc00002e1
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
.
- References:
- Re: ebd.log corrupted
- From: http://www.repairpst.info
- Re: ebd.log corrupted
- Prev by Date: Re: ebd.log corrupted
- Next by Date: Re: AD Integrated DNS and DHCP on the same server
- Previous by thread: Re: ebd.log corrupted
- Next by thread: Re: Prevent Domain Users From Browsing Around in Active Directory?
- Index(es):
Relevant Pages
|
Loading
