How to set up Regtrace for Exchange 2000

The transport and routing components in Microsoft Exchange Server 5.5 have been significantly modified in Exchange 2000 Server, and as a result, many transport and routing problems have become quite difficult to solve. To assist Microsoft Product Support Services (PSS) in troubleshooting and resolving Exchange 2000 Server transport and routing problems, Microsoft has provided a utility called "Regtrace" with the Exchange 2000 Server CD.

This article describes how to configure Regtrace to capture detailed information about the transport and routing components in Exchange 2000 Server. This article also explains what to do with that information.

Enabling Regtrace

Regtrace.exe can be found on the Exchange 2000 Server CD in the Support\Utils\I386 folder. Copy Regtrace.exe to a folder on the server, and then run the program.

To activate the Tracing feature on the server where Exchange 2000 is installed:

1. At a command prompt, type regtrace. The Trace Settings window opens.
2. On the Trace tab, ensure that all check boxes are checked.
3. On the Output tab, ensure that the File option is selected, and provide a path to a location that is large enough to store the very large file that is possible as output.
4. On the Threading tab, ensure that the Write traces on a background thread option is not selected.
5. Edit the registry: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.
   
   1. Start Registry Editor (Regedt32.exe).
   2. Locate the following key in the registry:
      HKEY_LOCAL_MACHINE\Software\Microsoft\MosTrace\CurrentVersion\DebugAsyncTrace
      By default, the only registry entries for Regtrace are:
      AsyncThreadPriority: REG_DWORD : 0
      AsyncTraceFlag: REG_DWORD : 0x1
      OutputTraceType: REG_DWORD : 0x1
      TraceFile: REG_SZ : c:\trace.atf
   3. On the Edit menu, click Add Value, and then add the following registry values:

         Value Name: Modules
         Data Type:  REG_MULTI_SZ
         Value:      AQ
                     CAT
                     DS2MB
                     dsevntwrap
                     EXSINK
                     IMAP4SVC
                     REAPI
                     RESVC
                     Routing
                     SMTP
                     StoreDrv
                     TranMsg
                     DSACCESS
                     MTA

      Each module entry should be separated by carriage return/line feed (CR/LF) in the REG_MULTI_SZ edit dialog box.
      
      The new entry appears in the registry as:
      Modules:REG_MULTI_SZ:AQ CAT DS2MB dsevntwrap EXSINK IMAP4SVC REAPI RESVC Routing SMTP StoreDrv TranMsg DSACCESS

      Value Name: MaxTraceFileSize
      Data Type: REG_DWORD
      Value: 0x1400000
      The new entry sets the maximum trace file size to 20 megabytes (MB) and appears in the registry as:
      MaxTraceFileSize:REG_DWORD: 0x1400000
   4. Quit Registry Editor.
6. It is not necessary to restart any services. Regtrace will begin tracing as soon as you configure an output filename and click Apply or OK in Regtrace.
7. Reproduce the problem that you are troubleshooting. For example, if you are reproducing a problem where mail is being returned undeliverable, send some e-mail to an address that will cause Exchange 2000 Server to return the message undelivered.
8. When you have reproduced the problem several times, stop tracing by clicking No Tracing from the Output menu in Regtrace. Also, on the Trace tab, make sure that the All tracing type option is not selected.

Important Do not leave Regtrace enabled. Without the MaxTraceFileSize registry entry, the trace file that will be created can fill up the hard disk. PSS has observed that on "busy" bridgehead servers, Regtrace can write 10 MB of data or more every minute.

What to Do with the Logs

The trace file will be available at the location that you specified on the Output tab of Trace Settings window in step 3. The default location for the file is C:\Trace.atf.

The trace file is a binary encoded file that needs to be "fixed" before it can be viewed. The trace file contains an enormous amount of debug-level information about all of the transport and routing components that are being traced. For this reason, PSS requires customers to send in the trace files for internal analysis. The files may need to be zipped and delivered to PSS by means of an FTP server, Microsoft File Exchange (MSFE), or Premier Service Desk. For details on any of these delivery methods, consult your PSS representative.