Can't open Local Security Policy database

[philt]

We have a W2k Advaced server running an intranet web
server. When trying to open Local Security Policy database
via Admin tools, it say can't open Local policy database.
I check the MS knowledgebase and there is article talking
about Everyone account should have full rights to the
%SystemRoot% dir; which is the case on our server.

Is there any other way that we can get this problem fixed?

Thanks much in advance.

 

[Steven L Umbach]

What KB article says that the everyone group needs full control to systemroot
folder?? What is the error message you get when trying to open it? Are there in error
messages in Event Viewer? --- Steve

http://support.microsoft.com/?kbid=278316

 

[Phil]

Thanks for the reply, Steve.

The article is Q300267
(http://support.microsoft.com/default.aspx?scid=kb;en-
us;300267&Product=win2000)

When trying to open the Local Policies (Audit Policy, User
Rights Assignment, Secutiry Options)
The messages are:

Windows cannot open the local policy database.

An unknown error occured when attempting to open the
database.


Not error messages related to this are logged in evet log.

 

[Steven L Umbach]

Thanks for posting that KB. I have never seen that one and looks like it was an
issues with earlier service packs. My guess is that your secedit.sdb may be corrupt
and attempting the repair in KB278316 may be worth a try. Also using esentutl may
help as described below.

The security database is corrupted.
Run esentutl /g to check the integrity of the security database at
%windir%\Security\Database\Secedit.sdb.

If the database is corrupt:

1.. Attempt to recover it by running esentutl /r on the %windir%\Security folder.
If this fails, attempt to repair it by running with esentutl /p on
%windir%\Security\Database\Secedit.sdb.
2.. After that, delete the log files in %windir%\Security.

 

[Phil]

The database was indeed corrupted and esentutl /p fixed it.
Thank you very much, Steve.

-Phil

 

[vizoere]

Corrupt secedit.sdb

The same fix worked for me. Thanks Steve!