Microsoft KB Archive/811173

From BetaArchive Wiki
Knowledge Base


Lsass.exe on a Global Catalog Uses 100 Percent of CPU Resources

PSS ID Number: 811173

Article Last Modified on 12/2/2003



The information in this article applies to:

  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Server



SYMPTOMS

After you create about 1000 additional views to the Microsoft Exchange Global Address Book, the Lsass.exe program may exhaust the CPU on all the global catalogs during logon hours. During the rest of the day, Lsass.exe may use an average of 80 percent of CPU resources.

The ratio between Global Address Book views and CPU usage of the Lsass.exe program on the global catalog varies depending on the number of clients per global catalog, the CPU speed, and the memory that is available to the global catalogs.

You may receive the following event message on the Exchange Server:EventID: 9176 / Source: MSExchangeSA / Description:
NSPI Proxy can contact Global Catalog (Global Catalog Name) but it does not support the NSPI service. After a domain controller is promoted to a Global Catalog, the Global Catalog must be rebooted to support MAPI clients. Reboot (Global Catalog Name) as soon as possible.However, when you restart the global catalog, the behavior recurs.

CAUSE

This behavior occurs because MAPI detects everything as a table (container). Because everything is located in a tree, and there are a number of different ways to structure this tree, the Active Directory directory service does not support tables in the way that MAPI requires them. Therefore, Active Directory must do more work to provide MAPI clients with the table view that they typically use.

The NspiGetHierarchyInfo function is called when you start Microsoft Outlook or open the Address Book to request this table. This function processes all the Global Address Book views, and it sorts the results. The global catalog requires a lot of CPU resources to process and to sort the large number of Global Address Book views and the large number of clients.

WORKAROUND

To work around this behavior, use fewer Global Address Book views or add more (and more powerful) global catalogs.

STATUS

This behavior is by design.


Additional query words: NSPI NspiGetHierarchyInfo MAPI Global Address Book View Exchange Outlook GC

Keywords: kbprb KB811173
Technology: kbwin2000AdvServ kbwin2000AdvServSearch kbwin2000Search kbwin2000Serv kbwin2000ServSearch kbWinAdvServSearch