| Event Id | 427 |
| Source | ESENT |
| Description | <process> (<number>) The database engine could not access the file called <full path>\<file name>. |
| Event Information | Following information from a newsgroup post may help you: A: If the event description is " The database engine could not access the file called C:\WINNT\Security\Database\secedit.sdb", following steps may resolve the issue. First you have to rename the file named secedit.sdb (%SystemRoot%\winnt\security\database\secedit.sdb) to some other name such as secedit.old. Then rename the file named secedit.new to secedit.sdb and reboot the system. B: I found a similar case where they followed 278316 and the problem would return after a couple of weeks. This customer had Write-through cache disabled but the IDE controller they were on did not honor it. Do you have Write-back cache disabled on your the controller? If your Drives support write-back cache you may have to turn this off with a jumper on each disk, even if you have turned it off on the controller. 324805 HOW TO: Manually Turn Disk Write Caching On or Off [url]http://support.microsoft.com/?id=324805[/url] 259716 HOW TO: Manually Enable/Disable Disk Write Caching [url]http://support.microsoft.com/?id=259716[/url] In another case the Anti-virus scanning was causing the corruption. If you restore the database by following 278316 and configure the Anti-virus not to scan the database folder where secedit.sdb is located does the problem go away? If it does you should contact the vendor of the Antivirus application for a fix so you can continue to scan the entire machine. Following MS articles will give more information about this event. |
| Reference Links | Jetpack
Fails with Error 1032 How to Use Jetpack.exe to Compact a WINS or DHCP Database |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.