Scecli.dll errors occur when opening Account Policies or Local Policies
Updated: March 2, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Scecli.dll errors may occur when you open Account Policies or Local Policies in Local Computer Policy.
When you attempt to open Account Policies or Local Policies in Local Computer Policy, you may receive the following error messages:
“Windows cannot open the local policy database. An unknown error occurred when attempting to open the database.”
SceCli Event ID 1202: “Security policies are propagated with warning 0x4b8: An extended error has occurred.”
This error message can occur if the Local Group Policy log files are corrupted. This usually indicates that the secedit.sdb file is corrupted.
Determine if secedit.sdb is corrupt by running esentutl /g %windir%\security\database\secedit.sdb.
Try to restore secedit.sdb from a backup before the problem started.
If secedit.sdb is corrupt, attempt a soft recovery first by running esentutl /r edb in the %windir%\security directory.
If soft recovery fails, attempt a repair with esentutl /p %windir%\security\Database\secedit.sdb. Then delete the log files %windir%\security\*edb* and %windir%\security\*log.
Rebuild secedit.sdb. Delete the following files: %windir%\security\*edb*, %windir%\security\*log, and %windir%\security\database\secedit.sdb.
Restart the computer.
|If you perform a repair with esentutl /p on a computer running Windows 2000, the local security policy settings are lost and you must recreate them. If you perform a repair with esentutl /p on a computer running Windows Server 2003, persistent security settings (also referred to as tattoo table) are lost so when Group Policy settings are undefined, the server’s settings do not revert to their original values.|
For more information, see the following articles which describe other known issues that can cause the 0x4b8 error, see the following:
Event ID 1000 and 1202 After Configuring Policies on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=39982).
ESENT Event IDs 1000, 1202, 412, and 454 Are Logged Repeatedly in the Application Event Log on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=39984).