Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)

re: Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)

HighQual — Thu, 02 Dec 2010 03:50:05 GMT

mbalsby did you find any solution? We have the same issue on one of our DC

re: Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)

NedPyle [MSFT] — Thu, 07 May 2009 16:53:59 GMT

"Provider load failure" sounds like a WMI failure. Rather than troubleshoot further here, I'd suggest opening a support case with us, it sounds like there are multiple problems going on here.

Provider load failure: Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)

mbalsby — Thu, 07 May 2009 16:34:15 GMT

Here is the error: Provider load failure

C:\Program Files (x86)\Server Performance Advisor>spacmd start "active directory"

The command completed successfully.

C:\Program Files (x86)\Server Performance Advisor>spacmd stop "active directory"

The command completed successfully.

C:\Program Files (x86)\Server Performance Advisor>spacmd compile "active directo

ry"

Compiling: Active Directory

C:\PerfLogs\Data\Active Directory => C:\PerfLogs\Transfer\Active Directory

Provider load failure

C:\Program Files (x86)\Server Performance Advisor>

Windows Server 2003 Performance Advisor (SPA) - no reports generated

mbalsby — Thu, 07 May 2009 13:41:31 GMT

Hi Directory Services Team

We are troubleshooting high CPU load on one of our Domain Controller. In the SCOM 2007 LSASS Processor time monitor view is shows normal load on 3 out of 4 DC’s

One DC peaks With 60-100% CPU load primarily on the LSASS.exe process. This DC is not holding the PDCE role, but has the following roles:

1. Domain naming operation master

2. Schema master

The symptoms:

• Long response time from clients. Citrix Edgesight monitoring reports shows this from both Windows XP and 2003 servers.

• Long response times when accessing DFS resources (through MS DFS / NetApp DFS CIFS)

We have followed the http://blogs.technet.com/askds/archive/2007/08/20/troubleshooting-high-lsass-cpu-utilization-on-a-domain-controller-part-1-of-2.aspx article without success.

Our problem right now is that the Windows Server 2003 Performance Advisor (SPA) report does not show after running the data collector

Conficker causes LSASS to consume CPU Time on Domain Controllers

Ask the Directory Services Team — Thu, 16 Apr 2009 19:55:08 GMT

Hi Gautam here, I wanted to blog about a high-impact problem we have been seeing recently. The problem

Domain Infrastructure Research

Confluence: Campus Active Directory — Wed, 28 Jan 2009 18:25:55 GMT

Microsoft Support Documents 2008 "Lag site" or "hot site" (aka delayed replication) for Active Directory Disaster Recovery support

re: Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)

NedPyle [MSFT] — Wed, 22 Aug 2007 00:01:46 GMT

Hi Brad,

I definitely wrestled with that when creating this post. I find that some of the detail is lacking from the NTDS diagnostic entries for this that I can get from SPA or Tracing, so I ended up writing up all the logging then removing it. The MSDN link I included for inefficient LDAP does point to it at the very end, but it's not as good as your link.

I may revisit this with some other load scenarios caused by RPC/SMB/NP API calls at some point as well, since none of this example or LDAP logging will be helpful there.

I really appreciate the comment!

-Ned

re: Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)

BooRadely — Tue, 21 Aug 2007 01:15:39 GMT

Great post with good details. Surprised you didnt mention Filed Engineering since ti shows these bad queries.

http://www.activedir.org/article.aspx?aid=97

Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)

re: Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)

re: Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)

Provider load failure: Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)

Windows Server 2003 Performance Advisor (SPA) - no reports generated

Conficker causes LSASS to consume CPU Time on Domain Controllers

Domain Infrastructure Research

Top AskDS Blog Posts

re: Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)

re: Troubleshooting High LSASS CPU Utilization on a Domain Controller (Part 1 of 2)