nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

lsass.exe w2k process

frattafr

The lsass process is taking a lot of cpu time on your w2k server.

We use w2k server with servicepack 2.

Do other users have the same problem?

Find more posts tagged with

Accepted answers

All comments

The LSASS problem is caused when the Administrative GUI is killed from the task manager instead of being closed normally. Apparently some cleanup deep within Windows is not taking place. Michael is right about it taking a fix from Microsoft to prevent this from happening, but for now, I would try to avoid killing the System Administrator and just close it normally.

BK

Questionario

which system administrator are you talking about?

I also noticed the lsass.exe process taking a ton of cpu-time on my orion server sometimes...

ecklerwr1

There are also some trojans that can cause this to happen... also if it's a DC:

support.microsoft.com/.../842382

Alex975

Here is a list of malwares that uses lsass.exe http://www.file.net/process/lsass.exe.html So, malware is also a possibility.

Questionario

i doubt its a virus/trojan and its not a DC.

Virus scanner is installed and nothing but Solarwinds products have ever been installed on the server, internet security is on high and nobody surfs on that computer.

chris.lapoint

Have you upgraded to APM 3.5 RC? It should be in your portal now.

Questionario

We just upgraded to ALX on APM, I have added several monitors and now the server is almost constantly at 100%, most of it coming from this lsass.exe process.

Any solution to this?

EDIT:

I opened a ticket with #159443

Questionario

I was told the solution is to either wait for NPM v10 and upgrade to Win2008 R2 or wait for APM 3.5 to release.

*vents*

Until then... I guess we just have to delay go-live of solarwinds again.

Its only been 7months anyhow... not quite the ~1hour until its ready... and a lot of wasted money for support, if I knew I would have waited a year for the purchase.

*/vents*

ecklerwr1

The NPMv10 RC3 is about as production ready as it's going to get. I understand companies being afraid of Release Candidates after some of the things that have happened with Microsoft. I'd look at the NPMv10RC3 and W2k8R2 if you require it.

Questionario

nope, no RCs for us. We will have to wait for v10 to be released

chris.lapoint

NPM 10.0 and APM 3.5 will GA together very very soon. In fact, I can safely say it doesn't make any sense to wait any more since the last RC build (RC3 for both) IS the GA build. The RC period is over and we're NOT making any more changes before GA.

Questionario

ok, good...

would you still recommend upgrading (because of the bugs/incompatibilty with APM) from win2008 to win2008 R2 while updating APM and NPM?