Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

June 28, 2004 12:00 AM

Dr. Watson Debugging Symbols

Windows IT Pro
InstantDoc ID #42879
Rating: (0)

To troubleshoot Exchange Server hangs or crashes, Microsoft Product Support Services (PSS) might require that Exchange debugging symbols be installed on your system. Debugging symbols let PSS engineers view global variables and function names in dump files created by Exchange processes, helping the engineers to identify the root cause for a crash. You can install Exchange debugging symbols from the Exchange 2003 or Exchange 2000 installation CD-ROM under the folder \Support\Symbols\i386. The Setup program installs all the necessary symbols in the correct locations on the server. Note that no downtime is required, and you don't need to take Exchange services offline to install the symbol files.

By default, Dr Watson creates a mini crash dump and doesn't generate a symbol table, but Microsoft recommends that you edit these settings. To do so, open a command line and enter

drwtsn32.exe

Set the crash dump type to Full and select the check box to enable Dump Symbol Table, as Web Figure A shows. By default, Dr. Watson stores files in a folder in the profile for the user running Dr Watson. (My default folder path for Dr Watson files is C:\Documents and Settings\morrisseyd\Local Settings\Application Data\Microsoft\Dr Watson.) I suggest that you change the location for crash dumps and log files to F:\diagnosis\drwatson, as Web Figure A shows, so that you can more easily locate debugging files, and so that the files don't take up space on the system drive.

I recommend that you install Exchange debugging symbols on an as-needed basis. If you choose to install them as part of a standard Exchange build, take the following factors into account:

  • Debugging symbols must be loaded into memory with the executable files, which has a small effect on performance. For servers that have more than 1GB of memory and multiple processors, the performance hit will be negligible.
  • For every Exchange service pack and hot-fix installation, you must update symbol files to match the updated executable files. Such updating increases the systems management overhead associated with applying service packs and hot-fixes.
  • Related Content:

    ARTICLE TOOLS

    Comments
      There are no comments to display. Be the first one!
    You must log on before posting a comment.

    Are you a new visitor? Register Here

    advertisement

    advertisement

    White Papers

    Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

    Essential Guides

    Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

    Web Seminars

    What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

    eLearning Series

    We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
    Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

    Subscribe to Windows IT Pro!

    Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.