Lsass.exe starts maxing CPU after deploying ASP.NET web applications
After deploying a new assembly (mostly modified DLLs) of an ASP.NET web application, the processor on the server now jumps to 100% every few seconds and lsass.exe is the culprit. Do you think that deploying asp.net web app to server and this issue are related? (or is it a coincidence that this happened at the same time?)
Additional Information:
This is the first time I've done a build on a Server 2008 x64 machine. Previous builds were done on a Server 2003 x86 machine. The target is "Any processor", so it should work on any. The deployed server is a 2003 x86 server.
I searched the internet for more information on this and confirmed that the process is lsass.exe (the first character is lowercase L, not uppercase i), so it ruled out the virus version. Found some documents related to Server 2000 bug but not applicable here.
source to share
I ended up isolating the issue for an ASP forum running under this ASP.NET web application. Using the admin page on the forum, I took the forum down and put it back in again and the problem went away. I find it very frustrating because the problem is gone, but I don't know what caused it and as such it could easily come back.
I also installed this Microsoft hotfix and rebooted this server, but it didn't work.
source to share
Updated to use the Active Directory Provider role? I've seen issues where enumerating groups to check for a role binds the processor and really slows down the application. I actually implemented a configured provider that allowed me to specify a specific department and group of groups that I really care to work around this issue for.
source to share
The xperf tools distributed in the Windows Performance Toolkit will tell you what is usin CPU time or disk bandwith. These tools are free and work on any retail build of WS2008 or Vista. Here is a series of xperf tools posts from me.
source to share