Active Directory Failure on Startup

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

On a cold boot, after a perfectly normal shutdown, I was unable to start Windows. The cause was a Security Accounts Manager failure to initialize - error 0xc00002e1. There are several Knowledge Base articles relating to this message, and I've checked all of them. The required files are present, in their correct paths, and all have the correct permissions set. There are several drives, and in each case where a NTDS folder exists, the permissions are correct. I've checked file paths in the Registry, and all are correct, excepting one odd entry that starts "C:\=\\?\Volume{bizarre completely unusable GUID} that I don't know how to interpret. Perhaps it's perfectly normal, but it's complete worthless for any diagnostic purpose - there's no way to tell, since there is no published reference that I can find to the ridiculous entries in the Registry

Since nothing available from Microsoft points to a problem that is applicable in this instance, are there other steps I should try before resorting to reinstalling the Server yet again?
 
The error can also be caused by problems with the database. You should use
ntdsutil to run diagnostics against the database.
Try running an integrity check, semantic database analysis and run a repair
if needed. The link below will provide you with information about these
commands.

http://www.microsoft.com/technet/tr...dows2000serv/reskit/distsys/part5/dsgappc.asp


--
Tim Hines, MCSE, MCSA
Windows 2000 Directory Services

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


Roger Wright said:
On a cold boot, after a perfectly normal shutdown, I was unable to start
Click to expand...
Windows. The cause was a Security Accounts Manager failure to initialize -
error 0xc00002e1. There are several Knowledge Base articles relating to
this message, and I've checked all of them. The required files are present,
in their correct paths, and all have the correct permissions set. There are
several drives, and in each case where a NTDS folder exists, the permissions
are correct. I've checked file paths in the Registry, and all are correct,
excepting one odd entry that starts "C:\=\\?\Volume{bizarre completely
unusable GUID} that I don't know how to interpret. Perhaps it's perfectly
normal, but it's complete worthless for any diagnostic purpose - there's no
way to tell, since there is no published reference that I can find to the
ridiculous entries in the Registry.
Since nothing available from Microsoft points to a problem that is
Click to expand...
applicable in this instance, are there other steps I should try before
resorting to reinstalling the Server yet again?
 
Back
Top