services.exe error; secedit.sdb

[Guest]

has anyone found any documentation/admittance of an issue regarding
services.exe errors from Microsoft on XP Pro? we have found in numerous
instances, services.exe crashes on a machine, offering the usual "Send Error
Report", "Don't Send" options, and also "Debug". debug locks up the box.
either send or don't send commences a shutdown.exe /reboot sequence. we have
found a workaround, but are not satisfied, and want an endorsed solution.
the box begins as a member of a domain, but will be used exclusively offline,
and so is removed/disjoined form domain membership back to a workgroup. if
we move the SECEDIT.SDB from its default location, this has so far resolved
the problem. but, management wants an "endorsed" resolution to the problem.

has anyone found any details as such on microsoft's site?
thanks.

 

[Wesley Vogel]

SECEDIT.SDB may be corrupt.

ESENT event IDs 1000, 1202, 412, and 454 are logged repeatedly in the
Application log
http://support.microsoft.com/kb/278316

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

I suppose it could be, but I'm wondering how it is that other boxes we build
from the same sms image are not affected. it seems as long as they remain
members of the AD domain rather than removed from the domain, the domain
members do not exhibit the problem. is it possible that somehow the
secedit.sdb could get corrupted by disjoining from the domain? I don't
understand how that could be.
thanks for the tip, and the reference to the KB article.

 

[Wesley Vogel]

Who knows how any file could get messed up.

Check the integrity of secedit.sdb.

Open a command prompt, type or paste the following line and hit Enter...

esentutl /g %windir%\security\database\secedit.sdb

If you get "Integrity check successful." you can rule that out.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In