Re: Problems with NTDS.DIT and lsass.exe errors
From: Eric Fleischman [MSFT] (efleis_at_online.microsoft.com)
Date: 02/12/04
- Next message: Marco: "Re: Runing a program using runas in a batch file"
- Previous message: Savut: "Execute Update on multiple network computers"
- In reply to: MJC: "Re: Problems with NTDS.DIT and lsass.exe errors"
- Next in thread: Jack Wang [MSFT]: "Re: Problems with NTDS.DIT and lsass.exe errors"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 12 Feb 2004 10:14:45 -0600
It's a matter of understanding what the tool does I'm afraid. Because of the
type of action that it performs I do not recommend it, although strictly
speaking sure you can. It just isn't a hot idea.
-- Eric Fleischman [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "MJC" <mjcartier@optonline.net> wrote in message news:uyfucWL8DHA.1548@tk2msftngp13.phx.gbl... > Though I've never had to run this utility, I remembered reading about it on > Microsoft KB. Here is MS' version: > http://support.microsoft.com/default.aspx?scid=kb;en-us;816120&Product=winsv > r2003#11 > > It didn't mention not to perform this procedure if you had an additional DC > that was operational. Just if the NTDSUTIL was unsecessful. > > > >>> Eric Fleischman [MSFT]<efleis@online.microsoft.com> 2/11/2004 10:18:17 > AM >>> > I would absolutely, positively not follow this procedure if you have > another > working DC in the domain. > Further, it was stated earlier (if my read is correct) that the dit is not > able to be located. That tells me that we don't have anything to run > esentutl against. > > To see if I'm clear, you do have another dc in the domain correct? And your > goal is to demote and promote this box up again? > > ~Eric > > -- > Eric Fleischman [MSFT] > This posting is provided "AS IS" with no warranties, and confers no rights > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm > > > <mjcartier@optonline.net> wrote in message > news:OaVcziK8DHA.1640@TK2MSFTNGP11.phx.gbl... > > Brent: > > > > Did you try this? > > > > http://www.jsiinc.com/SUBI/tip4200/rh4205.htm > > 4205 » Ntdsutil won't repair the Active Directory database? > > > > When you try to repair the Active Directory database > > (%SystemRoot%\Ntds\Ntds.dit) using the Ntdsutil tool, you receive errors > > similar to: > > > > Operation failed because the database was inconsistent. > > Initialize jet database failed; cannot access file. > > Error while performing soft recovery.If this happens, use the Esentutl > > tool: > > 1. Boot to Active Directory Restore mode. > > 2. Open a CMD prompt and perform an integrity check by typing: > > > > esentutl /g "<path>\ntds.dit"/!10240 /8 /v /x /o > > > > 3. Repair the database by typing: > > > > esentutl /p "<path>\ntds.dit" /!10240 /8 /v /x /o > > > > 4. Delete the database log files from the Ntds folder. > > > > 5. Restart your Server. > > > > > > > >
- Next message: Marco: "Re: Runing a program using runas in a batch file"
- Previous message: Savut: "Execute Update on multiple network computers"
- In reply to: MJC: "Re: Problems with NTDS.DIT and lsass.exe errors"
- Next in thread: Jack Wang [MSFT]: "Re: Problems with NTDS.DIT and lsass.exe errors"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading