akyuen
asked on
Security Accounts Manager cannot be initialized.
I'm getting an error when I boot up my Windows 2000 server:
"security accounts manager initialization failed because of the following error: Directory Services cannot start. Error status 0xc00002e1. Please click OK to shutdown this system and reboot into directory services mode."
I rebooted the server and tried following MS KB258062. When I did a ntdsutil files integrity, I got an output that said that there is a page error, I proceeded to perform a ntdsutil "sem d a" go.
the result of that command gives me: Getting records count...0 recordssemantic checker:
Any ideas on what to do after this? Unfortunately, I don't have a backup of the system state.
"security accounts manager initialization failed because of the following error: Directory Services cannot start. Error status 0xc00002e1. Please click OK to shutdown this system and reboot into directory services mode."
I rebooted the server and tried following MS KB258062. When I did a ntdsutil files integrity, I got an output that said that there is a page error, I proceeded to perform a ntdsutil "sem d a" go.
the result of that command gives me: Getting records count...0 recordssemantic checker:
Any ideas on what to do after this? Unfortunately, I don't have a backup of the system state.
Do you have another domain controller?
ASKER
No. This is a stand alone unity server.
If semantic database analysis show errror you need to fix the same by executing ntdsutil "sem d a" "go f"
If error is not found in sysmantec analysis you need to defrag the AD database:http://support.microsoft.com/kb/232122
Even after defraging the database if issue persist you need to repair the AD database.You need to first try soft repair eseutil /R "AD datbase path" and then try hard repair if it does not work eseutil /d "AD datbase path"
http://technet.microsoft.com/en-us/library/cc961819.aspx
Note:Also exclude ntds folder from AV scan
If error is not found in sysmantec analysis you need to defrag the AD database:http://support.microsoft.com/kb/232122
Even after defraging the database if issue persist you need to repair the AD database.You need to first try soft repair eseutil /R "AD datbase path" and then try hard repair if it does not work eseutil /d "AD datbase path"
http://technet.microsoft.com/en-us/library/cc961819.aspx
Note:Also exclude ntds folder from AV scan
I might open a ticket up with Microsoft before the eseutil since it is your only DC.
When you get this fixed get a second DC up if you can. If you would have had a second DC this would have been a much easier problem to fix.
Thanks
Mike
When you get this fixed get a second DC up if you can. If you would have had a second DC this would have been a much easier problem to fix.
Thanks
Mike
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.