Re: Unable to read any security database file

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.

<lleventh@xxxxxxxxx> wrote in message
news:1170876689.266901.178030@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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.



.