OLT troubleshooting
General issues for troubleshooting Object Level Trace are provided on this page.
- Norton Antivirus needs to be disabled in order to run OLT on Windows 95/98.
- On Windows 2000, in order to use the context-sensitive help of the accompanying product,
you must define a system environment variable called windir and set it to the
system root. For example, if the user's system root is c:\winnt, then windir=c:\winnt.
- When OLT is in step-by-step debug mode, the OLT Viewer
displays a dialog box at each debuggable method prompting you to step into the next
debuggable method. If you are running Windows 2000, you may not see this dialog box if the
Distributed Debugger user interface is covering the OLT Viewer. If you are waiting to be
prompted to step into the next debuggable method by the OLT Viewer, bring the OLT Viewer
in focus so that you will see the dialog box.
- Some trace lines have Server as the Object name. This problem occurs when the
application is debug-enabled and is run before launching OLT. Suppose some objects are
already initialized. When OLT is launched and these objects are called, they do not call
their respective initializers. Therefore, OLT can not determine what the objects are. You
should always start OLT before running a debuggable application.
- If you are using any WebSphere 4.0 Applications with a different code page than the OLT
Tool workstation, you must set the following environment variable on the WebSphere 4.0
Applications workstations to the following:
OLT_TRC_SRV_CODEPAGE=codepage of the OLT Tool host.
In addition, troubleshooting information is included for the following OLT problems:
- Installation
- OLT startup
- Distributed debugging
- Browsers

Debugging a Java client

OLT troubleshooting - OLT environment file