Revision as of 19:35, 19 April 2006 by Bobby (talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Tools for debugging Outlook problems

When Outlook hangs or exhibits unexpected behavior (opening pop-up error windows, for example), but you can reproduce the problem, run these tools as described below to generate debugging data to send to us. This process is analogous to enabling the SOAP/XML debug window for the Web Client ($set:debug [1-3]).

There are two components (both free): WinHttpTraceCfg (part of Windows Server 2003 [Resource Kit Tools]), which traces the communication with the server, and [DbgView] (from SysInternals), which captures the trace.

1. In order to enable the trace, and send the data to the debug stream (where DbgView can catch it), run this command in an MS-DOS Command Prompt window:

WinHttpTraceCfg -e 1 -d 1

2. Then run DbgView to catch the data stream. You can run DbgView from the Command Prompt or from the Windows GUI. DbgView runs as a standard Windows application, so once you have generated the trace data (by causing Outlook to have problems), choose the familiar "Save As..." from the File menu and send it to us.

N.B. If Outlook is running when you make changes to the debug settings, it will disregard them until you quit and restart.

Jump to: navigation, search