|
| |||||||||
| Tags: active directory, backup, login screen, security accounts manager, windows 2003 server |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| security accounts manager initialization failed
We have windows 2003 environment, currently organization is running two windows 2003 servers. Few days before one of our administrator deploy another server with exchange 2003 but unfortunately that server become down due to some hardware problem. Now we are facing serious problem. When we try to login to the server it has given an error before the login screen which is “System Error, 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 restore mode, check the event log for more detailed information.” After rebooting the machine in directory services restore mode, I tried to move the database and Log file but when ever I try to wove database I got this error Opening database [Current].*** Error: DBInitializeJetDatabase failed with [ Jet Error -501]. Error While Doing Soft Recovery file maintenance: I have also verified file integrity which was successfully completed. We do not have system state backup of that system. Any one can help me to solve his problem. Thanks Mansoor Siddiqui |
|
#2
| |||
| |||
| Re: security accounts manager initialization failed
Database is currupt. If you can stop replication now. If no other DCs are affected, you can manually remove that affected DC, and add it after metadata cleanup. If not possible: Can you restore it from backup? If not possible the only way is to try a repair on the NTDS.dit. confirm permissions, disk space, registry entries, then attempt a DB repair. http://support.microsoft.com/kb/258062 |
|
#3
| |||
| |||
| Re: security accounts manager initialization failed
Unfortunately I don€™t have backup. I would like to prefer manually remove that server can you guide me how can I remove all information from AD of other servers. I will be really grateful to you |
|
#4
| |||
| |||
|
Assuming that this Dc is an Aditional Dc for an existent domain: - Disconnect (unplug the network cable) the Dc from network and run dcpromo /forceremoval. Restart the server. Delete the NTDS folder. Follow Domain controllers do not demote gracefully when you use the Active Directory Installation Wizard to force demotion in Windows Server 2003 and in Windows 2000 Server http://support.microsoft.com/kb/332199/en-us - Then remove all references to that Dc on AD database (Metadata cleanup). - Remove any Dns references to the Dc. - nltest /dsderegdns:<dns host name> - If necessary seize any left Op Master roles that were hosted by that Dc. *Note: The domain controller that seizes the role must be fully up-to-date with the updates performed on the previous role owner. Because of replication latency, it is possible that the domain controller might not be up-to-date. To check the status of updates for a domain controller, use the Repadmin.exe /Showutdvec switch. *C:\> repadmin/showutdvec server2. mydomain.com dc= mydomain,dc=com *C:\> repadmin/showutdvec server3. mydomain.com dc= mydomain,dc=com - If some discrepancies Use the Repadmin /Syncall switch to make the replication happen immediately. - If the domain controller that you are demoting is a DNS server or global catalog server, you must create a new GC or DNS server to satisfy load balancing, fault tolerance, and configuration settings in the forest, don't forget that you need at least one GC per Forest.. -Dont forget to export the *EFS* certificate. If one of these two dcs is the first dc that was installed in your domain then the EFS certificate resides locally on that dc. When you remove the dc before you export the efs certificate you will loose it. Without this certificate you are not able to recover efs encrypted files. http://support.microsoft.com/?scid=k...41201&x=5&y=13 - When you use the remove selected server command in NTDSUTIL, the NTDSDSA object, the parent object for incoming connections to the domain controller that you forcibly demoted is removed. The command does not remove the parent server objects that appear in the Sites and Services snap-in. Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller http://support.microsoft.com/kb/255504/ How to remove data in Active Directory after an unsuccessful domain controller demotion http://support.microsoft.com/?kbid=216498 Clean up server metadata http://technet2.microsoft.com/Window....mspx?mfr=true |
|
#5
| |||
| |||
|
Our server with windows server 2003 crashed last night and needed a repair install (Told us to repair a file using repair install). We get to the part where active directory services trays to start and then we get the following message: box Isass.exe - System Error Security accounts manager initialization failed because of the following error: Directory Service cannot start: Error Status: 0xc00002e1: Please click ok to shutdown the system. You can use the recovery console to diagnose the system further. What can I do to continue the repair install and get this server to work? Thanks. |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "security accounts manager initialization failed" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Security Account Manager Initialization Failed | lucmook | Windows Server Help | 2 | 20-11-2011 09:03 PM |
| Security Accounts Manager giving fail initialization error | OliverS | Active Directory | 1 | 21-05-2011 04:56 AM |
| security accounts manager initialization failed when repair install | samgi44 | Active Directory | 1 | 21-04-2011 04:59 PM |
| LASS.EXE Security Account Manager initialization failed | Mauri_63 | Active Directory | 4 | 16-09-2009 05:53 PM |
| Disabling Security Accounts Manager | napoleon | Operating Systems | 3 | 13-07-2009 11:33 PM |