Siebel Interactive Selling Transact Server Interface Reference > Installing Transact Server > Troubleshoot Transact Server >

Identify the Problem

If you run into problems after the installation, use the log file to identify the source of the problem. Once identified, if you are unable to correct the problem, then you can contact Siebel Technical Support.

To identify a problem

  1. Set the Transact Log Debug property to on in the property editor.
  2. Transact then records in the log details about all activities.

  3. Perform the same actions you did when the problem occurred.
  4. Open the log file.
  5. The location of the log files is specified in the property editor.

The error message contains a time stamp, an error number, a message that states the attempted action and consequences, the actual Java exception message, and a stack trace of where it occurred in the code. In the following example, the Configuration List could not be generated because the socket connection was closed (the user navigated elsewhere before it had a chance to return). This error is given by the Java exception.

Example Error:

8/16/00 2:55 PM[OLM_MAR_E_05000] ERROR: Couldn't complete action!

(action=ConfigList.jsp) Connection reset by peer: socket write error

From looking at the log file, you may be able to determine the problem yourself. If not, record the log activity that occurred while you were reproducing the problem and contact technical support. Providing your technical support representative with this information is the easiest way to resolve the problem.

 Siebel Interactive Selling Transact Server Interface Reference 
 Published: 18 April 2003