Easysoft ODBC-ODBC Bridge

What do I do if I get an Access Violation or Fault popup window?

Last Reviewed:
10th January 2024

If an access violation or other fault occurs when running a program on Windows, a popup window appears. This may occur on the client side when running an application connected to the Easysoft ODBC-ODBC Bridge client or at the server side.

In general:

  1. You should note down any information contained in this popup window.
  2. Write down exactly what you were doing before this occurred.
  3. If you have a Dr Watson log take a copy of the log (see later).
  4. Send all of the above along with the version of the ODBC-ODBC Bridge you were running to .

If you are writing your own ODBC compliant application, 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 the ODBC APIs.

On older versions of Windows, Dr Watson runs 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 directory.

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:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug

This key contains string values "Auto" and "Debugger". If you want to temporarily change the spawned debugger to Dr Watson, 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 restore the original 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 ODBC-ODBC Bridge, the ODBC-ODBC Bridge 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 will also be reported to the Event Log if this is available on the Windows platform. If you have an esoob.exception file, send that to us with a description of what you were doing.

Applies To

Knowledge Base Feedback

* Did this content help you?
* Please select one option based on your first choice:

(* Required Fields)