Win2000 server has lost its ability to read security databases

[Guest neilbehagg@yahoo.co.uk]

Hi all, I've got a problem on a Windows 2000 server that I really need

some help with. Let me explain the symptoms.

 

The issue was first raised as a problem with SQL2000, we were getting

the dreadded 'cannot generate sspi context' error. Alot of

troubleshooting later lead me to find that the server can't open the

secedit.sdb local policy database. All I get is 'An unknown error

occured when attempting to open the database'. I've verified the

secedit.sdb database, even deleted and recreated it. gave everyone

access to the system drive as its mentioned in a KB somewhere.

 

I finally opened the sdb file from another server, proving that its

not the file thats the issue. It just seems that the server itself

cannot read the secedit database. Going on from this I tried creating

a new databse in the Security Configuration and Analysis snapin but

again it can't create a brand new database from any template, even

from a template from another server. All I get is 'An unknown error

occured when attempting to open the database'. No entries in the

system logs, nothing.

 

I've dropped it out of the domain, added it back in, checked all

policies etc and am now at a complete loss. Anyone ever come across

this before?