Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

One DC cannot boot up due to Directory Services failures

132 views
Skip to first unread message

Derek

unread,
May 2, 2008, 4:47:03 PM5/2/08
to
We have 3 DC's in our domain. For one of them, we get the following error
upon startup:
Directory Services could not start because of the following error: The
system cannot find the file specified. Error status: 0xc000000f. Please click
Ok to shutdown this system and reboot into Directory Services Restore Mode,
check the event log for more detail information.

We've booted into DS Restore mode, and tried to recover the AD db manually,
but also get errors with that:
esentutl /r C:\Windows\NTDS\ntds.dit
--> Operation terminated with error -1003 (JET_errInvalidParameter,
Invalid API parameter) after 0.15 seconds.

What can we do to resolve this problem on that DC?
If not, can we demote that DC from one of the other DC's? Is it as simple as
deleting the server from "Domain Controllers" in ADUC?

Thanks in advance,
Derek.

meinolfweber

unread,
May 2, 2008, 5:07:58 PM5/2/08
to
Hello Derek,

see inline

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

> We have 3 DC's in our domain. For one of them, we get the following
> error
> upon startup:
> Directory Services could not start because of the following error: The
> system cannot find the file specified. Error status: 0xc000000f.
> Please click
> Ok to shutdown this system and reboot into Directory Services Restore
> Mode,
> check the event log for more detail information.

Did you check the event log? What errors are dsiplayed? What happend before
this error message, updates or system crash of DC?

> We've booted into DS Restore mode, and tried to recover the AD db
> manually,
> but also get errors with that:
> esentutl /r C:\Windows\NTDS\ntds.dit
> --> Operation terminated with error -1003 (JET_errInvalidParameter,
> Invalid API parameter) after 0.15 seconds.

You have to know the error before starting a recovery from DSRM, so that
you know what to recover.

> What can we do to resolve this problem on that DC?

Again what was going on before the error?

> If not, can we demote that DC from one of the other DC's?

NO, you can only demote the DC itself, you can cleanup AD from another DC
from old entries.

> Is it as
> simple as
> deleting the server from "Domain Controllers" in ADUC?

NO, demoting a DC is more complex, then just deleting from ADUC contianer.

> Thanks in advance,
> Derek.


Derek

unread,
May 2, 2008, 6:55:10 PM5/2/08
to
Thank you for the feedback.
The errors in Event Log were:

Source: NTDS General
Category: Internal Processing
Event ID: 1003
Description: Active Directory could not be initialized. The operating system
cannot recover from this error

Source: NTDS General
Category: Internal Processing
Event ID: 1168
Description: Internal Error: An Active Directory error has occurred.
Additional Data
Error value (decimal): -501
Error value (hex): fffffe0b
Internal ID: 40749

Source: NTDS General
Category: Performance
Event ID: 1229
Description: System Monitor was unable to open Active Directory performance
counters. An attempt to open shared memory failed.
Additional Data
Error value: 2 The system cannot find the file
specified


We've tried deleting the log files under c:\windows\ntds. A reboot
regenerated these files, but still fail to boot under normal mode.

We can't really tell when this DC started failing. I do see one event under
System Events that may or may not be related:

Source: NETLOGON
Category: None
Event ID: 5783
Description: The session setup to the Windows NT or Windows 2000 Domain
Controller \\dc1.mycompany.com for the domain
MYCOMPANY is
not responsive. The current RPC call from Netlogon on
\\DC2 to
\\dc1.mycompany.com has been cancelled.

(where "dc1" is our main DC, "dc2" is this faulty DC)
This message appears very often in the days leading up to us discovering the
problem. Maybe it's just a generic message, but it's curious why the
Description didn't mention "Windows 2003 DC", which is what all the DC's are
running.

Your help is much appreciated.

Thanks.

Meinolf Weber

unread,
May 2, 2008, 7:33:44 PM5/2/08
to
0 new messages