Microsoft KB Archive/255140

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 12:53, 21 July 2020 by X010 (talk | contribs) (Text replacement - """ to """)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base

Reset Lotus Notes JIT debugger after client is installed on Exchange 2000

Article ID: 255140

Article Last Modified on 5/22/2007


  • Microsoft Exchange 2000 Server Standard Edition

This article was previously published under Q255140

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry


It is recommended that you reset the Lotus Notes Just In Time (JIT) debugger setting after you set up a Lotus Notes client on an Exchange 2000 server. Doing so allows the Connectivity Controller to restart a Connector for Lotus Notes process if it failed to handle an exception and, therefore, to continue its normal operation. Lotus Notes Setup enables its utility "Quincy" to handle failed processes (crashes) that require operator intervention (to click OK) to end the failed process.


Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

You can disable the JIT Debugger with the following procedure:

  1. Start Registry Editor.
  2. Locate the following registry key:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug

  3. Select the Debugger value.
  4. On the Edit menu, click String.
  5. To use Dr. Watson, type drwtsn32.exe -p %ld -e %ld.

    Note An easier way to make Dr. Watson the default debugger by running this command:

    drwtsn32.exe -i

For more information about how to choose a debugger other than Dr. Watson, click the following article number to view the article in the Microsoft Knowledge Base:

121434 Specifying the debugger for unhandled user mode exceptions

Additional query words: XFOR

Keywords: kbinfo KB255140