Re: Unable to edit Security Policies on Win2K Machine

From: Steven L Umbach (sumbach_at_ameritech.net)
Date: 05/29/03 

Date: Thu, 29 May 2003 01:32:06 GMT

       You could try to repair your secedit.sdb file - there are acouple of
ways. --- Steve

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B329887

Or try this from MS website. *************************************

The security database is corrupted.

Cause: A hardware problem if the computer is improperly shut down or a
software error.

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.

"Jim Strenk" <jimstrenk@mindspring.com> wrote in message
news:GJcBa.5202$7J5.106@tornadotest1.news.pas.earthlink.net...
> Having edited security policies in the past, I am now unable to do so on
the
> same Win2K machine. The Security MCC is telling me that the database is
> corrupted. I see messages about the same thing when looking at error logs
> for both applications and system.
>
> Is there a setting(s) within the security settings that might affect the
> transferring of files from one machine to another using a NIC Card? I'm
> limited to very small files that get transferred (less than 70K).
>
> Is there a way that I can restore the required files so that they can be
> edited once again?
>
> Would sending the required files in somewhat generic form be a
possibility?
>
> Could repairing from the Windows 2000 Professional CD be a possibility?
>
> Any suggestions, tips or errata would be greatly appreciated! A copy of
> your reply to my email address would also be helpful.
>
>

Relevant Pages

  • Re: Cannot Open Local Policy
    ... You probable have a corrupt secedt.sdb file. ... The security database is corrupted. ... software error. ... Run esentutl /g to check the integrity of the security database at ...
    (microsoft.public.win2000.security)
  • Re: Failed to save Local Policy Database
    ... Sounds like a corrupt secedit.sdb on the computer in question. ... Try using esentutl utility first. ... The security database is corrupted. ... So I go to 'Local Security Settings/Access this computer from the network' ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Failure to open Auditing in Security Settings
    ... > Your security database may be corrupted. ... >using Security Configuation and Analysis tool. ... >If the database is corrupt: ...
    (microsoft.public.win2000.security)
  • Re: Failure to open Auditing in Security Settings
    ... using Security Configuation and Analysis tool. ... The security database is corrupted. ... If the database is corrupt: ... Attempt to recover it by running esentutl /r on the %windir%\Security folder. ...
    (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)