If an access violation or other fault occurs when running a program in Windows a popup dialogue appears. This may occur on the client side when running you application connected to the OOB client or at the server side.
you should note down any information in this popup.
write down exactly what you were doing before this occurred.
if you have a Dr Watson log take a copy of the log (see later)
send all of the above along with the version of the OOB you are running to .
If you are writing your own ODBC compliant application then your first port of call should be to thoroughly investigate your code and satisfy yourself that nothing is wrong with it. Any application can generate an access violation in an ODBC driver by passing invalid pointers to ODBC APIs.
Dr Watson log files are created by drwtsn32.exe. After installing Windows your machine is set up to run drwtsn32.exe when a program fails (note that installing other software e.g. Microsoft Developer Studio can change the spawned debugger). This program writes information about your operating system and the program that failed into a log file. It shows the threads, where each of them were when the program failed and which thread caused the problem. This file can be an invaluable aid in determining the source of the problem. The Dr Watson log file is DRWTSN32.LOG and is created in the your Windows
If you have installed the WIN32 SDK then the debugger is changed to WINDBG. You can change the debugger back to Dr Watson by editing the following key in your registry:
This key contains string values "Auto" and "Debugger". If you want to temporarily change the spawned debugger to Dr Watson to generate a log file then write down the current version of the "Debugger" entry and change it to:
DRWTSN32 -p %ld -e %ld -g
Once you have generated a log file you can reset the debugger entry.
These entries are also available in Windows 95/98 but they are in the win.ini file instead of the registry. The section [aedebug[ has entries that correspond to the registry.
From OOB 126.96.36.199 (for Windows) the OOB Server traps exceptions and reports them in the file LOGDIR\esoob.exception (where LOGDIR is a server configurable parameter defaulting to c:\temp). Any exceptions on NT will also be reported to the Event Log. If you have an esoob.exception file, send that to us with a description of what you were doing.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.