| Event Id | 412 |
| Source | ESENT |
| Description | services (PID) Unable to read the log header. Error -530. |
| Event Information | This event ID message will be logged every five minutes in the Application event log along with event 1000 from Userenv, 1202 from SceCli,
454 from ESENT. CAUSE: This issue occurs if the local Group Policy database file is corrupt. RESOLUTION: To resolve this issue, use the procedure described in this section to re-create the local Group Policy file. NOTE: When you use this procedure, your computer is returned to the original installation state; the Local Security Policy is not defined. Also, you may have to start your computer in Safe mode to rename or move files. For information about how to do so, see Windows 2000 Help. IMPORTANT: Before performing these steps on a Domain Controller, create a backup of the SYSVOL share. </p> <p>1) Open the %SystemRoot%\Security folder, create a new folder, and then name it "OldSecurity". 2) Move all of the files ending in .log from the %SystemRoot%\Security folder to the OldSecurity folder. 3) Find the Secedit.sdb file in the %SystemRoot%\Security\Database folder, and then rename this file to "Secedit.old". 4) Click Start, click Run, type mmc, and then click OK. 5) Click Console, click Add/Remove Snap-in, and then add the Security and Configuration snap-in. 6) Right-click Security and Configuration and Analysis, and then click Open Database. 7) Browse to the %SystemRoot%\Security\Database folder, type Secedit.sdb in the File name box, and then click Open. 8) When you are prompted to import a template, click Setup Security.inf, and then click Open. |
| Reference Links | ESENT Event IDs 1000, 1202, 412, and 454 are logged repeatedly in the application event log |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.