- Iguana Crash Reporting
- 32 vs 64 bit ODBC issues
- Using Dr. Watson
- Using Problem Reports and Solutions
Under windows Iguana has a very good built-in crash reporting system that provides detailed information on what caused a crash to occur. It took us a lot of effort to implement but is very useful.
If you look in the Iguana install directory, you will find the following files:
- Files with the extension *.dmp and *.mdmp
Please send them to us, since they have information that is required by our development team to diagnose and resolve issues of this nature.
These files can be quite large. What we recommend doing is:
- Zip them up into single zip archive
- Add to same zip archive any additional file(s) you may find necessary to report to us
- Name this archive with distinguishable name, we recommend this format:
- Upload zip file directly to our ftp site, see FTP uploads to Support
Thank you, we really appreciate you doing this.
If you have an Iguana server which is crashing then this is the recommended troubleshooting procedure.
32 vs 64 bit ODBC issues [top]
Windows users often run into a few issues with ODBC: Using the 32 vs 64 bit version of ODBC administrator tool (not always obvious), always use DSN datasources, and you cannot use the SQL Server “native client” driver, etc
See Using 64 ODBC for details of these problems and their solutions.
Using Dr. Watson [top]
Dr. Watson is the built-in debugger that is included with Windows XP, Windows 2000 and Windows Server 2003. This debugger is named drwtsn32.exe.To configure Dr. Watson on your system:
- On your Windows system, click Start.
- From the menu that appears, select Run.
- In the Run window, type drwtsn32.
- Click OK.
The Dr. Watson window appears:
The following table describes the fields and check boxes that you can modify in this window:
|Log File Path||The path of the log file created when a program crashes. This log file, and the map file generated while building the program, can be used to find the cause of the problem.The user that is running the program must have write access to this folder, or a File Open dialog box will open when when the program crashes.|
|Crash Dump||The location of the dump file created when a program crashes. You can use WinDbg to examine this file, along with the PDB file generated when building the program, to find the cause of the problem.Because WinDbg provides a visual environment that is similar to Visual Studio to inspect the crash, it is often easier to use the crash dump file to find the cause of the problem than to use the log file.The user that is running the program must have write access to this folder, or a File Open dialog box will open when when the program crashes.The Create Crash Dump File check box must be selected for a crash dump to be generated.|
|Number of Instructions||This specifies the number of assembly instructions to be recorded for each thread when an application error occurs. Setting this value to 10 is usually sufficient.|
|Number of Errors To Save||This is the maximum number of errors saved to the log file. Setting this value to 10 is usually sufficient.|
|Dump Symbol Table||Specifies that the symbol table is to be dumped. You do not normally need to select this check box, as a symbol table is provided in the map and PDB files. If this check box is selected, the log file can become very large.|
|Dump All Thread Contexts||Provide data for all threads. This check box should be selected, as it can provide useful information about what else was happening when the program crashed.|
|Append To Existing Log File||Append log data to an existing log file. If this check box is selected, the log file can become very large.|
|Visual Notification||If this check box is selected, a dialog box appears when a crash occurs. For Iguana, this check box can be kept unselected, as displaying this dialog box keeps Iguana from restarting if service recovery settings are being used.If you do not dismiss this dialog box (by pressing OK), it automatically disappears after 5 minutes.|
|Sound Notification||Provide audio notification when a crash occurs. This check box can normally be kept unselected.|
|Create Crash Dump File||Specifies that a crash dump file is to be created when a crash occurs.|
Click the Help button for more information on these settings and the log file.
After you have configured Dr. Watson, you must install it. To install Dr. Watson, open a Command Prompt window and type drwtsn32 -i. Then, restart the program that you want to debug.
When Dr. Watson is installed, a log file named drwtsn32.log is created when the program crashes. If Create Crash Dump File has been selected, a crash dump file is also created.
For more information on Dr. Watson, see the following resources:
- The Wikipedia entry for Dr. Watson
- Microsoft’s page on Dr. Watson for Windows for Windows XP
- Using Dr. Watson to Create a Dump File
Using Problem Reports and Solutions [top]
Problem Reports and Solutions is a tool provided with Windows Vista and Windows Server 2008 that collects information about crashes as they occur.To access Problem Reports and Solutions:
- From the Control Panel, select Problem Reports and Solutions and View problem history.
- Locate the crashed application that you are interested in.
- Select View a temporary copy of these files.
You can use WinDbg to debug the minidump.mdmp file.
For more information on Problem Reports and Solutions, see Microsoft’s help pages:
- For Windows Vista, see Windows Error Reporting and the Problem Reports and Solutions Feature in Windows Vista.
- For Windows Server 2008, see Windows Error Reporting and the Problem Reports and Solutions Feature in Windows Server 2008.
- Windows Error Reporting and the Problem Reports and Solutions Feature in Windows 7 and Windows Server 2008 R2
If you are using Windows Vista, and Problem Reports and Solutions does not generate a crash dump, you can generate a full user-mode dump file. See How to create a user-mode process dump file in Windows Vista and in Windows 7 for more details.