Lsass Exe System Error In Windows 2003 Server
Contents |
360 games PC games security accounts manager initialization failed server 2003 Windows games Windows phone games Entertainment All Entertainment
Error Status 0xc00002e1 Server 2003
Movies & TV Music Business & Education Business Students & educators security accounts manager initialization failed windows 7 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Security Accounts Manager Initialization Failed 2003 0xc00002e1
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All stop c00002e2 directory services a device attached to the system is not functioning Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Windows Server 2003 - lsass.exe System Error - Object Name not
Error 0xc00002e1
found Windows Server > Windows Server General Forum Question 0 Sign in to vote
Directory Services Restore Mode Server 2003
I have searched high and low for the last 4 days to find a solution to this problem. I have used error 0xc00002e1 windows 8 my server 2003 discs and done a repair on the install. I have downloaded new SV2003 iso and used them as a repair. I have tried booting into safe mode and the same issue https://support.microsoft.com/en-us/kb/830574 comes up. I have booted into the recovery console and run every single thing I could think of with no luck. I have taken the drive out and slaved it on another PC changed the lsass.exe to lsass.exe.old not luck. Now I know most of you are going to say just reformat and start over. I would if I could... this install is very important and the https://social.technet.microsoft.com/Forums/windowsserver/en-US/d0415322-95bc-47ea-aacf-db1395c4976c/windows-server-2003-lsassexe-system-error-object-name-not-found?forum=winservergen information and setup on it can not be lost. If anyone ANYONE has a solution to this or a fix that would be greatly appreciated. And no it is not a virus as this server is only used to upload documents to which are created in house. The way it all stared was when I was upgrading the RAM in the Server once I popped out a stick and realized the wrong RAM had been sent I put the original stick back in to the motherboard and rebooted to have this error come up everytime. I have gone into the BIOs and set it to default with nothing changing. I am pleading with anyone or even Microsoft please help!Andrew Reed City of Lacombe Monday, May 16, 2011 7:39 PM Reply | Quote Answers 2 Sign in to vote Hi Andrew, i understand your pain.. well have you try using active boot disk? try downloading active boot disk. Execute iton that problematic machine. active boot diskallows you to perform sys restore. and back up all your data.. you can google the iso image for active boot disk. Is freeGuowen Su | CCNA, CCIP, MCP, MCSA, MCSE, MCTS, MCITP, CEH | http://www.microsoft.com/en/sg/default.aspx Our Goal? VE
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us http://serverfault.com/questions/54188/lsass-exe-error-windows-cannot-boot Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and http://www.krishaynes.co.uk/2009/03/lsassexe-system-error-when-booting.html answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up security accounts and rise to the top lsass.exe error, Windows cannot boot up vote 1 down vote favorite This is apocalypse. The server threw me an "lsass.exe" error this morning, saying that it cannot boot, with the following error. LSASS.EXE - System Error, security accounts manager initialization failed because of the following error: Directory Services cannot start. Error status 0xc00002e1. I don't get to boot screen. I can successfully boot security accounts manager in active directory restore mode. I'm beyond horror and panic at the moment. The system told me the user hive was corrupted, but recuperation worked out okay, or so said the messagebox. As far as I know, there is no disaster recovery plan at all. The boss said that there MIGHT be a ghost somewhere. If I don't find any, there isn't. The question is simple. I have to improvise the best plan ever or we're all dead. What should I do, apart from trying not to panic? The system is a Windows 2003 with SiS onboard RAID support, plugged with two scsi drives in RAID 0+1. The drivers and system are up to date. There is seemingly no virus in there, though I wouldn't rule out that possibility. Security is a mess to start with. This is a follow-up to my epic odyssey of tragic death: http://serverfault.com/questions/52312/write-read-errors-raid1-recovery http://serverfault.com/questions/49424/0x00000077-error-on-the-corporate-server http://serverfault.com/questions/53349/windows-server-2003-sisraid-error-device-scsi-sisraid1 windows-server-2003 disaster-recovery scsi share|improve this question asked Aug 14 '09 at 12:34 Olivier Tremblay 232315 I'm either gonna cry or resign. Or both. Both would be good. –Olivier Tremblay Aug 14 '09 at 12:42 Can you summarize here what lead to this condition? –nik Aug 14 '09 at
initialization failed because of the following error: Directory Services cannot start. Error status 0xc00002e1. I know everyone's scenario's when seeing this message are pretty varied but I found a nice way to fix this within an hour providing you have a similar setup. In my particular case I had two servers an SBS 2000 (oh dear I hear you cry) and a Standard Server 2003 running SP1. The 2K3 machine was rebooted and upon reboot we were presented with the above error. So to fix try the following: 1. Reboot the 2K3 server into "Directory Services Restore Mode" then logon to the machine locally, in my case I didnt know the restore password (results of taking on machines from other support companies.) -If this is the case go onto the second server, right click "my computer" and select manage, within the new window, right click the "Computer Management" header and then click connect to another computer, you can then connect to the server you can't log into and reset the local admin password. 2. So first things first now your into the server you need to check the database files, go to start, run, and type "cmd" to open a command shell. The type the following: ntdsutil files info You should see similar the below: Drive Information: C:\ NTFS (Fixed Drive ) free(533.3 Mb) total(4.1 Gb) DS Path Information: Database : C:\WINDOWS\NTDS\ntds.dit - 10.1 Mb Backup dir : C:\WINDOWS\NTDS\dsadata.bak Working dir: C:\WINDOWS\NTDS Log dir : C:\WINDOWS\NTDS - 42.1 Mb total temp.edb - 2.1 Mb res2.log - 10.0 Mb res1.log - 10.0 Mb edb00001.log - 10.0 Mb edb.log - 10.0 Mb You need to make sure that these files exist and the directory is there before you continue. 3. You can now do an integrity check by typing the following: ntdsutil files integrity if you get an error here then continue, otherwise try a reboot and it should fix the issue. 4. Next check is a semantic check, do this using the following command: ntdsutil "sem d a" go If this fails however try the following: ntdsutil "sem d a" "go f" 5. Try a defragment: 5a - Type 'ntdsutil' 5b - Type 'compact to "c:\TMP"' If defragmentation succeeds without errors, follow the Ntdsutil.exe on-screen instructions. Delete all the log files in the log directory by typing the following command: del drive C:\ pathToLogFiles \*.log Copy the new Ntds.dit file over the old Ntds.dit file in the current Active Directory database path that you noted in step 2. Note You do not have delete the Edb.chk file. Restart the computer normally. I personally still had issues at this point, with the server refusing to access these files with JET errors. So from