Microsoft KB Archive/813958

= Overview of the Call Trace Logging Feature =

PSS ID Number: 813958

Article Last Modified on 9/12/2003

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server
 * Microsoft Exchange 2000 Enterprise Server

-



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SUMMARY
This article describes an addition to the diagnostic-logging features that are available in Exchange 2000 Server. Call Trace logging records calls to specific external functions, and then writes this information to a log file. You can use Call Trace logging to help you troubleshoot and diagnose Exchange 2000 Server performance issues.

Cumulative Rollup Information
To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824282 September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup



MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. With Call Trace logging, you can gather more data about problem scenarios such as Exchange 2000 Server shutdown issues or situations when the Exchange information store (Store.exe) exhibits a decrease in performance or is unresponsive. For example, in some cases the information store may stop responding when the Store.exe process is blocked inside a call to an external function that requires a long time to complete such as access to Active Directory.

Call Trace logging automatically logs function call data. User intervention or a specific configuration, such as acquiring a user dump of the production server or the use of a debugger, is not required. By default, Call Trace logging is turned off. Turn on this feature in situations where you want to gather more information to help you isolate and identify the root cause of Exchange 2000 Server performance issues.

A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior that is described in this article. Apply it only to systems that specifically need it. This feature may receive additional testing. Therefore, if your system is not severely affected by the lack of this feature, Microsoft recommends that you wait for the next Microsoft Exchange 2000 Server service pack that contains this feature.

To obtain this feature immediately, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

The Global version of this feature has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version     Size       File name --  30-Jan-2003  21:00  6.0.6409.0  3,915,776  Cdoex.dll 30-Jan-2003 20:49  6.0.6409.0    827,392  Davex.dll 30-Jan-2003 21:00  6.0.6409.0  3,571,712  Excdo.dll 30-Jan-2003 20:46  6.0.6409.0    258,048  Exmime.dll 30-Jan-2003 20:50  6.0.6409.0  2,129,920  Exoledb.dll 30-Jan-2003 20:44  6.0.6409.0     81,920  Exosal.dll 30-Jan-2003 20:50  6.0.6409.0    303,104  Exprox.dll 30-Jan-2003 20:15  6.0.6409.0  2,265,088  Mdbmsg.dll 30-Jan-2003 19:44  6.0.6409.0     32,768  Mdbrole.dll 30-Jan-2003 20:45  6.0.6409.0  4,612,096  Store.exe This feature adds the following entries to the Windows registry that you can use to configure Call Trace logging:  To turn on Call Trace logging, set the following registry value to 0:

 

By default, Call Tracing is turned off, and this value is set to 1. To flush the whole contents of the call trace array to the log file, do one of the following:  Set the following registry entry to a value other than 0 (zero):

 

A non-zero value forces a flush of the trace information to the log file. Set the threshold for the number of active Remote Procedure Call (RPC) requests. When this threshold is reached, trace information is flushed to log file. To configure the threshold for active RPC requests, edit the following registry entry:

 

You can use a value between 1 and 100. The default setting is 70.  To configure the maximum log file size (in kilobytes), edit the following registry entry:

You can use a value between 2 and 400. The default setting is 16. After the log file reaches its maximum size, all subsequent flushes override existing flushes. When you modify this setting, you must restart the Exchange Information Store service for these changes to take effect.</li> To specify how frequently call trace information is flushed to the log file, edit the following registry entry:

The minimum interval of time that you can configure is 5 seconds, and the maximum interval of time is 24 hours. The default setting is 5 minutes.</li></ul>

Additional query words: kbExchange2000preSP4septbarFix

Keywords: kbExchange2000preSP4fix kbQFE kbinfo kbfix kbBug KB813958

Technology: kbExchange2000EntServ kbExchange2000Search kbExchange2000Serv kbExchange2000ServSearch kbExchangeSearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.