OLT troubleshooting - Installation and Startup

"ERROR_GET_KEY_VALUE - entry not found in the string table"
If you receive this message when installing the IBM Distributed Debugger and OLT, check the registry and locate the following registry keys:
 \HKEY_LOCAL_MACINE\SOFTWARE\IBM\IBM Distributed Debugger \HKEY_LOCAL_MACINE\SOFTWARE\IBM\IBM Distributed Debugger\CurrentVersion
The OLT installation program cannot be installed if a partial key already exists. Rename or remove these keys and try installing the IBM Distributed Debugger and OLT again.

"Cannot copy ivbtr30i.dll"
If you receive this message on a new install of the IBM Distributed Debugger, and you have Component Broker already installed, stop all servers, orb daemons, and bgmain, then retry the installation.

OLT server or viewer fails to start
If OLT appears to start, then closes prematurely, try starting from the command line by typing olt. This should provide you with an error message. Ensure that the directory defined by the %DER_DRIVER_PATH%\temp exists, and that you have "write" permission for this directory. If the problem persists, enter the following command to pipe your error message to a file, then send this file to your IBM representative:

olt >olt.log 2>&1

OLT viewer throws java.lang.OutOf Memory error during startup
If, when starting OLT from a command line, you see a java.lang.OutOfMemory error, you will need to edit the file that starts OLT and increase the -mx value in the file. On Windows, the file is %DER_DRIVER_PATH%\bin\olt.bat. On AIX, the file is /usr/idebug/bin/olt.

Client application fails to run
Try running the application from a command shell. If the application fails to start, a detailed error message should appear. (For help interpreting the message, Component Broker users should see the Problem Determination Guide).

Client application runs, but OLT appears to stop the application server
Check the transaction timeout values in your application code. These values must be set to zero, or a value not easily reached while using the debugger, such as 300 seconds.

Events do not appear in the viewer
If your application runs cleanly, but events do not appear in the OLT viewer, ensure that you have completed the necessary startup steps:

  1. Compile your code to include OLT flags.
  2. Enable OLT in System Manager.
  3. Start OLT (on NT, do not close the OLT command prompt window).
  4. Run your client application.

For detailed instructions, see the topic "Preparing for an OLT session".

Unusual program behavior
Check your temporary directory (as set by the %DER_DRIVER_PATH%/TEMP environment variable on Windows NT, or the /tmp directory on AIX). If you have a .chk file in your temporary directory, delete it and try running your application again. During normal operation, Object Level Trace creates files in the temporary directory and, if the program terminates unexpectedly, some of these files may not be properly deleted.

ngrelt.gif (466 bytes)
Preparing for an OLT session