Topic Last Modified: 2006-07-20

The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine the value of the serialNumber attribute for all objects that have an object class of msExchExchangeServer. If the string value includes Version 5.5, the computer is running Microsoft Exchange Server version 5.5. If the string value includes Version 6.0, the computer is running Exchange 2000 Server. If the string value includes Version 6.5, the computer is running Exchange Server 2003.

The Exchange Server Analyzer also queries for the presence of the Disable Call Tracing subkey from following registry entry to determine whether the Microsoft Exchange Function Call Logging (FCL) feature is enabled for the Exchange server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem

Exchange Server can trace the performance of internal calls that the Microsoft Exchange Information Store service (Store.exe) makes. You can use FCL to isolate the component and the function call that may be the root cause of the performance issue.

The FCL functionality in the Microsoft Exchange Information Store service keeps track of the relevant calls to the following components:

• Local Security Authentication Server (Lsass.exe)
  
  
• DSAccess
  
  
• Extensible Storage Engine (ESE)
  
  
• IMAIL
  
  
• Virusscan
  
  

FCL is low-overhead logging that gathers data about problem scenarios such as shutdown issues in Exchange Server or situations when the Exchange Information Store service (Store.exe) exhibits a decrease in performance or is unresponsive.

As soon as it is enabled, FCL automatically logs the function call data. User intervention or a specific configuration, such as acquiring a user dump file of the production server or the use of a debugger, is not required.

By default, FCL is enabled on Exchange Server 2003 but must be specifically enabled on Exchange 2000 Server.

The Exchange Server Analyzer displays a best practices message if the following conditions are true:

• The server is running Exchange 2000 Server and the Disable Call Tracing subkey is not present or, the Disable Call Tracing subkey is present, but contains a value other than 0.
  
  
• The server is running Exchange Server 2003 and the Disable Call Tracing subkey is present and contains a value other than 0
  
  

This best practices message indicates that FCL is disabled.

It is a recommended best practice to enable FCL on all Exchange servers.

To enable Function Call Logging on an Exchange 2000 Server

1. Open a registry editor, such as Regedit.exe or Regedt32.exe.

2. Navigate to: HKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\ Disable Call Tracing

3. In the right pane, double-click Disable Call Tracing. If the Disable Call Tracing subkey is not present, create it as a new DWORD value.

4. Configure the Disable Call Tracing subkey with a value of 0.

1. Close Registry Editor.
   
   
2. Restart the Exchange Information Store service for these changes to take effect.
   
   

To enable Function Call Logging on an Exchange Server 2003

1. Open a registry editor, such as Regedit.exe or Regedt32.exe.

2. Navigate to: HKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\ Disable Call Tracing.

3. In the right pane, double-click Disable Call Tracing.

4. Configure the Disable Call Tracing subkey with a value of 0.

1. Close Registry Editor.
   
   
2. Restart the Exchange Information Store service for these changes to take effect.
   
   

Before you edit the registry, and for information about how to edit the registry, see the Microsoft Knowledge Base article 256986, "Description of the Microsoft Windows Registry" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).

© 2009 Microsoft Corporation. All rights reserved.