Re: Can't open Local Security Policy database

From: Steven L Umbach (n9rouz_at_nscomcast.net)
Date: 11/27/03 

Date: Thu, 27 Nov 2003 00:51:45 GMT

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" <philts@atm.com> wrote in message
news:050c01c3b47b$e1098360$a401280a@phx.gbl...
> 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.
>
>
> >-----Original Message-----
> >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
> >
> >
> >"philt" <philts@atm.com> wrote in message
> >news:020001c3b45d$a48c1d30$a501280a@phx.gbl...
> >> 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.
> >

Relevant Pages

  • RE: MultiUser Issues with Access2002 - Errors 3343, Invalid SQL,21
    ... that the file may be corrupt. ... docmd.openreport, opening an ADO Recordset, looping through an ADO Recordset ... substitute CurrentDb if not the current database). ... Usually receive one of three Error messages: ...
    (microsoft.public.access.modulesdaovba)
  • Re: Cant open Local Security Policy database
    ... The database was indeed corrupted and esentutl /p fixed it. ... >If the database is corrupt: ... >> Windows cannot open the local policy database. ...
    (microsoft.public.win2000.security)
  • Error 1202 in Eventlog
    ... Security policies were propagated with warning. ... Some JET database is corrupt. ... Run esentutl /g to check the integrity ...
    (microsoft.public.win2000.active_directory)
  • Re: Group Policy Error
    ... Thank you very much Dave. ... problems if the first command reports that the database is corrupt. ...
    (microsoft.public.windows.group_policy)
  • Re: Group Policy Error
    ... problems if the first command reports that the database is corrupt. ... I am receiving the following error when launching Group Policy Editor. ...
    (microsoft.public.windows.group_policy)