Could Not Initialize Jet Engine Error 501
Contents |
may get get this error. The most common being a corrupt Active Directory database (NTDS.DIT). I know this sounds detrimental, opening dit database jet error 501 but it's actually easy to fix this blue screen. *** This
Esentutl Operation Terminated With Error
is the Active Directory Database we're talking about here, so make sure you have a good backup stop c00002e2 directory services a device attached to the system is not functioning of the server, in case this doesn't work*** This Stop code is only seen on a system with Active Directory on it. You notice it when the server is failed to open dit for ad ds/lds instance ntds. error -2147418113 booting. You'll get a blue screen and an error code, like the following: STOP: c00002e2 Directory Services could not start because of the following error: A device attached to the system is not functioning. Error Status: 0xc0000001. Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information. To
Operation Not Allowed Because Ad Ds/lds Files Are In The Restored State
begin, do as the message says, and boot into Directory Services Restore Mode. When the server powers on, press F8 before the OS begins to load. You should see a selection screen like this. Choose Directory Services Restore Mode: Once in Directory Services Restore Mode, you can check if there is a problem with the database by running the following commands: ntdsutil.exe activate instance ntds files If there is a problem with it, you'll see something like this returned: Could not initialize the Jet engine: Jet Error -501. Failed to open DIT for AD DS/LDS instance NTDS. Error -2147418113 To fix, just rename all of the .log files located in C:\windows\ntds\ to .log.old, or anything else, so they can be recreated. Now reboot the server. For most people, this fixed the database, and the server booted up. For others, it still blue screened after this. If you continue to get a blue screen, run the following command in Directory Services Restore Mode, and then reboot: esentutl /p "c:\windows\ntds\ntds.dit" Bookmark/Sear
somehow managed to corrupt one of my domain controllers in lab. LAB was based on Windows Server 2008 Datacenter. While rebooting server, server booted fine until the stage where I had to login error status: 0xc0000001 into Windows. Instead of getting login screen I got blue screen for fraction stop c00002e2 directory services could not start sbs 2008 of a second, and then everything rebooted again. In order to see what is the error, after rebooting when “Repair your
Could Not Initialize The Jet Engine Jet Warning 1
Computer” appeared I choose: (You can invoke recovery menu in Windows Server 2008 with F8) Disable automatic restart on system failure After that, instead of automatically rebooting on login screen I finally got to http://itswapshop.com/tutorial/how-fix-c00002e2-directory-services-could-not-start-blue-screen see the error Error was: c00002e2 Directory Services could not start because of the following error: A device attached to the system is not functioning. Error status: 0xc0000001 After that I rebooted machine again and from Recovery Menu I choose Directory Services Repair Mode If everything is ok with your DSRM after some time you`ll get login screen on which you have to login to your local administrator account https://www.informaticar.net/?p=1888 (domain services are not working, remember). At this stage you`ll need password which you setup for AD restore mode (password that you have to enter while setting first DC in domain) Next step is to open command prompt (with Administrative permissions) and enter Ntdsutil.exe After that Activate instance ntds And at last files If there is a problem, you`ll see following error Could not initialize the Jet engine: Jet Error -501. Failed to open DIT for AD DS/LDS instance NTDS. Error -2147418113 If you get this error, you should navigate to C:\Windows\NTDS directory. There you should rename all log files to log.old or whatever you like. We are renaming files so that they could be recreated. Reboot after renaming log files. After reboot my server booted normally and AD services were available. If your server still doesn`t work try this (repeat procedure and go to DSRM): esentutl /p "c:\windows\ntds\ntds.dit" Disclaimer Posted in Microsoft Related Tagged Active Directory Services could not start, c00002e2, c00002e2 Directory Services could not start, Zeljko Medic, Zeljko Medic IT Blog Post navigation Previous ArticleMicrosoft Outlook: Invisible attachments Next ArticleHow To: Use Telnet to test SMTP communication Search © Copyright 2016 IT Blog. Powered By WordPress. w
lab environment my Windows 2008 R2 Domain Controller VM did not start. When booting the VM I got a BSOD with a STOP error: STOP: c00002e2 Directory Services could not start because of the http://martijnwestera.blogspot.com/2013/01/stop-c00002e2-directory-services-could.html following error: a device attached to the system is not functioning. Error status: 0xc0000001. Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information. http://www.tech-archive.net/Archive/Windows/microsoft.public.windows.server.active_directory/2007-05/msg00321.html This was my only Domain Controller and no backup so I had to solve this problem. Troubleshooting steps: 1. Boot into Directory Services Restore Mode (F8) 2. NTDSUTIL: activate instance NTDS files could not Error: Could not initialize the Jet engine: Jet Error -501. Failed to open DIT for AD DS/LDS instance NTDS. Error -2147418113 quit 3. ESENTUTL /g C:\Windows\NTDS\ntds.dit ESENTUTL result: successful (no DB corruption) 4. ESENTUTL /p C:\Windows\NTDS\ntds.dit ESENTUTL result: successful (no DB corruption) 5. Event log: Error 1003: Active Directory Domain Services could not be initialized. The directory service cannot recover from this error. could not initialize Restore the local directory service from backup media. Error value: -501 JET_errLogFileCorrupt, Log file is corrupt Error 465: NTDS (2156) Corruption was detected during soft recovery in logfile C:\Windows\NTDS\edb.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 6697 (0x00001A29). This logfile has been damaged and is unusable. Error 454: NTDS (2256) Database recovery/restore failed with unexpected error -501. 6. Rename edb.log to edb.log.old and restart system Result: same STOP error Solution to this problem: rename all *.log files in C:\Windows\NTDS folder and restart system. Posted by Martijn Westera at 2:41 AM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest 64 comments: bjormeFebruary 4, 2013 at 1:38 PMYou are amazing! Messed with this for like 3 hours and your post is short and to the point. Thank you!!ReplyDeleteAnonymousFebruary 11, 2013 at 2:17 PMBrilliant! I did a v2v (form ESXi to MS) of a 2008 DC using imaging software and ended up with this exact issue, after trying just about every recommendation around, this is what resolved it for me, It turns out i had the same issue with DFSR and WSUS DB's, renaming the logs sorted the
ISAM Event Category: Logging/Recovery Event ID: 465 Date: 5/5/2007 Time: 5:31:09 AM User: N/A Computer: RC-SERVER-4 Description: NTDS (532) NTDSA: Corruption was detected during soft recovery in logfile E:\WINDOWS\NTDS\edb.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 695 (0x000002B7). This logfile has been damaged and is unusable. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ===================================================== These are the results from KB258062 (filled with 501 errors on the edb.log file) ===================================================== C:\>ntdsutil files integrity ntdsutil: files file maintenance: integrity Opening database [Current].*** Error: DBInitializeJetDatabase failed with [ Jet Error -501]. Error While Doing Soft Recovery Executing Command: C:\WINDOWS\system32\esentutl.exe /g"K:\WINDOWS\NTDS\ntds.dit" /o Initiating INTEGRITY mode... Database: K:\WINDOWS\NTDS\ntds.dit Temp. Database: TEMPINTEG792.EDB Checking database integrity. Scanning Status (% complete) 0 10 20 30 40 50 60 70 80 90 100 |----|----|----|----|----|----|----|----|----|----| ................................................... Integrity check successful. Operation completed successfully in 7.766 seconds. Spawned Process Exit code 0x0(0) If integrity was successful, it is recommended you run semantic database analysis to ensure semantic database consistency as well. file maintenance: q ntdsutil: q C:\>ntdsutil "sem d a" "go" ntdsutil: sem d a semantic checker: go Fixup mode is turned off Opening database [Current].*** Error: DBInitializeJetDatabase failed with [ Jet Error -501]. semantic checker: q ntdsutil: q C:\>ntdsutil "sem d a" "go f" ntdsutil: sem d a semantic checker: go f Fixup mode is turned on Opening DIT database... Could not initialize the Jet engine: Jet Error -501. Failed. Opening database [Current].*** Error: DBInitializeJetDatabase failed with [ Jet Error -501]. semantic checker: C:\>ntdsutil files info ntdsutil: files file maintenance: info Drive Information: C:\ NTFS (Fixed Drive ) free(24.6 Gb) total(39.6 Gb) D:\ NTFS (Fixed Drive ) free(8.6 Gb) total(9.7 Gb) E:\ NTFS (Fixed Drive ) free(66.5 Gb) total(100.4 Gb) H:\ NTFS (Fixed Drive ) free(3.8 Gb) total(5.8 Gb) I:\ NTFS (Fixed Drive ) free(37.5 Gb) total(39.6 Gb) J:\ NTFS (Fixed Drive ) free(5.1 Gb) total(9.7 G