The x_err.log file in Visual LANSA

Date: August 2007
Product/Release: Visual LANSA All Versions
Abstract: Getting the most from the x_err.log file
Submitted By: LANSA Technical Support

LANSA support will often refer to and ask you to provide a file called x_err.log when you generate an error in Visual LANSA. This file is automatically generated and updated when an error occurs, both in the development environment or when running a LANSA application. 

Some useful information about the x_err.log

  • All versions of Visual LANSA will produce an x_err.log when an error occurs.
  • New entries get appended to the end of the x_err.log file. Over a long period, this can cause the x_err.log file to become quite extensive.
  • In general, all fatal errors will be logged into the x_err.log file.
  • When deploying an application via the Deployment Tool, the x_err.log file will only be found if a LANSA application error occurs during package creation.
  • In a client/server environment, if the application is being run on the client when an error occurs, then this information would appear in a Fatal Error dialog box. If however, the X_RUN is run on a server (via a CONNECT_SERVER) operation, then the server cannot cause the dialog box to pop-up on the client in the same way. It can't even pop-up on the server either (because its a service job and has no desktop) but what would appear in a Fatal Error dialog box is always logged into the x_err.log file.

Location of the x_err.log file

  • For regular VL applications, the x_err.log is created in the users temp directory, which can be accessed quickly by typing %TEMP% in the address bar of Windows Explorer.
  • For Web/WAM applications,and Server systems, the x_err.log is created in the system temp directory (typically C:\WINDOWS\Temp\)
  • However, depending on a users PC configuration, it may reside elsewhere. If it is not found in the locations above, you can search your hard disk to find the file.
  • The next delivery of Visual LANSA will make it easier to find and display the X_Err.log with an all new Error Log Viewer. This will be available from the Tools menu of the Visual LANSA IDE:
    X_Err.log in the Error Log Viewer

Sending the x_err.log file to LANSA Support

When a fatal error occurs when using Visual LANSA, before reporting the error to your local LANSA product vendor, you should do the following:

  • Locate for the x_err.log file. If you cannot find one in your local drives (or Server drives in a Client/Serer application), you should make your local LANSA product vendor aware of the non-existence of the file as this information is also useful.
  • Open the x_err.log file using any text editor and go to the bottom. Review the last message and see if you can determine the cause of the error. Sometimes, the problem is clear-cut e.g. if you are trying to execute a component and the component DLL is unavailable.
  • Before sending to LANSA support, you should locate and delete the existing version of the file. Try to reproduce the error and send the newly created version to LANSA support. This ensures that the x_err.log pertaining to the error is what is reviewed.
  • The x_err.log should be sent to LANSA support in conjunction with other information to assist resolving the LANSA issue e.g. LANSA version and EPC information. Refer to Improving Issue resolution time for other information that should be forwarded to LANSA support with the x_err.log.