Event ID 427 Source ESENT
| Event ID | 427 |
| Source | ESENT |
| Type | Error |
| Description | <process> (<number>) The database engine could not access the file called <full path>\<file name>. |
| English, please! | Request a translation of the event description in plain English. |
| Comments |
Anonymous
(Last update 11/24/2008): - Process: "wuaueng.dll", file: "edb.log" – This error occurred on our Windows 2000 SP4 machine after upgrading our WSUS Server from WSUS 2.0 to WSUS 3.0. Reregistering wups2.dll seems to have solved the problem. Run the following command to register wups2.dll: - regsvr32 %windir%\system32\wups2.dll. Mihai Andrei (Last update 2/9/2006): - Process: "wuaueng.dll", file: "edb.log" - See the link to "Troubleshooting Client Setup". Ionut Marin (Last update 7/8/2004): See the link to "EventID 427 from source ESE" for details on this issue. Anonymous Process: "grovel". File: "database.mdb" - no info Process: "NTDS". File: "ntds.pat" - no info Process: "wins". File: "wins.mdb" - no info Process: "services". File: "edb.chk". - no info Adrian Grigorof Process: jetpack File: j50.chk. This occurs if the WINS or DHCP service is not stopped before you attempt to use the Jetpack utility. See M264515 and M145881 for more details. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! HairyMonster Process: "services". File: "secedit.sdb". Why couldn't the file be accessed? A couple of reasons spring to mind: The backup software had locked the file whilst backing up, or antivirus software had locked it whilst scanning. In my case, it was the backup. This may apply to all types of process/file combination. |
| Links | M145881, M264515, EventID 427 from source ESE, Troubleshooting Client Setup |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Custom search | The custom search information is available to subscribers only. |
| Feedback | Send comments - Notify me when updated |
| Print version |