|
Posted by Roger Abell [MVP] on February 9, 2007, 9:49 am
Please log in for more thread options >> Normally one cannot open the security.sdb of the running system
>> as it is opened for exclusive use. Are you sure you are not just
>> confusing this behavior?
>> Otherwise, yes, if you have corrupt sdb files that do not get fixed
>> then there would apparently be little one could do with them save
>> deleting and making new ones.
>>
>>
>>
>> > I'm having trouble with a Windows 2003 server machine. When I go to
>> > the Local Security Policy I get an error saying there is a problem
>> > with secedit.sdb, I've tried to use "esentutl /g" to see if that file
>> > was corrupt, however it came back without any errors. I tried to open
>> > this file and other known good .sdb files from the security analyzer
>> > MMC snap-in, but I always get the same error, that these are not valid
>> > security database files. Does anyone have any suggestions other then
>> > creating a completely new security database? Thank you for your help.
>
> Thanks Roger. I didn't realize I woudln't be able to look at
> secedit.sdb from the MMC, however even when I look at some of the
> other.sdb files they give me the same error. Also from the Local
> Security Policy in Admin tools, I get an error saying secedit.sdb has
> an error and then can't see any of the config parameters. Thanks.
>
Well, as a last resort approach one may use procedure in
http://support.microsoft.com/kb/278316/en-us
to get a new security.sdb
Also, note that your use of esentutl may have caused some tattooing
see within: http://support.microsoft.com/kb/884018/en-us
If I have been hearing you correctly, when you use the MMC
snap-in Security Configuration and Analysis, you are not able
to open any sdb file, which I find troublesome and have not seen.
Does this mean that you also cannot define a new sdb file and
use it successfully?
Roger
| 
XML Sitemap