|
Jorge, the problem with throwing a KB at it is that there are hundreds…..probably thousands…..of things that could cause this. With the data provided, it is nearly impossible to effectively diagnose the problem. This KB could be it, and if it is, I suggest you go out and buy a lotto ticket immediately. :)
This is my standard action plan I use for high lsass/dsamain utilization cases: 0)
During the problem state
please collect 3-5 dumps of lsass using adplus as follows: adplus –Hang –p
123 –o c:\dumps 1) During the problem please collect a network trace with a duration of at least 2 minutes in length 2) If on 2k3, collect >=5 minutes worth of SPA data. Set SPA to data only mode, and just zip up the transfer directory. We can compile it after.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jorge de Almeida Pinto
See the following if it applies: http://support.microsoft.com/Default.aspx?kbid=842382 Jorge
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sharif Naser Hello experts,
Lsass.exe hogs my domain controllers cpu (99%), what could be the reason for this, how do I get rid off this problem.
Machine was started twice but the problem still persists. By the way, machines has advanced windows 2000 with sp4.
Regards, DISCLAIMER:
|
- RE: [ActiveDir] lsass.exe hogs my domain controller... Eric Fleischman
- RE: [ActiveDir] lsass.exe hogs my domain contr... Jorge de Almeida Pinto
- RE: [ActiveDir] lsass.exe hogs my domain contr... Sharif Naser
- RE: [ActiveDir] lsass.exe hogs my domain contr... Eric Fleischman
- RE: [ActiveDir] lsass.exe hogs my domain contr... Sharif Naser
- [ActiveDir] Account Name Change Christopher Hummert
