Export (0) Print
Expand All
Expand Minimize

LeakDiag is enabled

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool reads the following registry entry to determine whether LeakDiag.exe is enabled on the computer:

HKEY_LOCAL_MACHINE\Software\Microsoft\LeakDiag\EnableAutoStart

If the Exchange Server Analyzer finds the value for EnableAutoStart set to 1, a warning is displayed. EnableAutoStart is configured using the LeakDiag user interface. The default value is 0. A value of 1 indicates that LeakDiag is enabled and active.

LeakDiag is a set of tools that helps developers, support professionals, and information technology (IT) personnel diagnose memory leaks, fragmentation, and other memory-related issues in applications or services that are on computers running Microsoft Windows NT® Server 4.0, Windows® 2000 Server, Windows XP, and Windows Server™ 2003.

The LeakDiag tools can be used to pinpoint memory leaks down to the line of code. Using Detours technology from Microsoft, LeakDiag intercepts calls to specified memory allocations and tracks the various call stacks. It reports on the memory that has been allocated but not yet freed. This information lets a person who is troubleshooting a memory leak problem see exactly what components made the allocations. With correct debug symbols, even the line of code that requested the allocations can be seen.

It is recommended that you do not run LeakDiag on Exchange servers that are in a production environment. When enabled, LeakDiag will track all memory allocations for all processes every time the Exchange server is started. This will consume a massive amount of processor and memory resources and is not recommended unless you are actively troubleshooting a memory-related problem. If you are not actively troubleshooting a memory-related problem, you should turn off LeakDiag. Running LeakDiag in a production Exchange Server environment could lead to memory fragmentation and depletion, and ultimately Exchange failure.

noteNote:
You should always troubleshoot problems with LeakDiag during off-peak hours. Using LeakDiag during periods of heavy or peak usage can cause a significant decrease in the performance of your Exchange Server computer.

  1. Click Start, and then click LeakDiag.

  2. On the Tools menu, click Options.

  3. On the Options page, clear the Allow AutoStart check box, and then click OK.

For the latest version of LeakDiag, see the Microsoft public FTP site (http://go.microsoft.com/fwlink/?LinkId=41401).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft