Automatic creation of dump files for unhandled exceptions in Visual LANSA V13

Date: 25 June 2013
Product/Release: Visual LANSA - V13
Abstract: In V13, a dump file is automatically created in the event of an unhandled exception occurring in Visual LANSA.
Submitted By: LANSA Technical Support

In V13, in the event of an unhandled exception occurring, Visual LANSA automatically creates a dump file in the Windows temporary (%TEMP%) folder. A few points to note about the production of the dump file:

  • Dump files contain critical information that can be used by LANSA to determine the cause of an unhandled exception (also know as an access violation).
  • They are only produced in the event of an unhandled exception.
  • There is only one dump file kept so each time an unhandled exception of the same name occurs, the dump file is overwritten.
  • The error message on the screen will indicate the name of the dump file and where it is located. An example message might be
    Message : (0885) - Access violation (exception code c0000005) at address 00BB5D47 should be reported to your product vendor as soon as possible by supplying the files X_ERR.LOG and X_RUN.DMP in directory C:\Users\userABC\AppData\Local\Temp\2\

If you encounter an unhandled exception, either when executing a Visual LANSA application or while in the Visual LANSA IDE, you should do the following before restarting the Visual LANSA application or restarting the Visual LANSA IDE.

  1. Navigate to the %TEMP% folder in Windows explorer (or use the location specified in the message on the screen) or the Visual LANSA runtime temporary directory (TPTH) if it is set.
  2. Look for a dump file that matches the date and time of the unhandled exception. There may be more than one but they would have different names, for example, LANSA.dmp or x_run.dmp. Checking that the date and time of the dump file matches the date and time of the unhandled exception will help you find the appropriate one.
  3. Dump file can be quite large so we would advise compressing the file.
  4. Contact your local LANSA Support group as they can provide an FTP location to upload the dump file along with the x_err.log (from the %TEMP% folder too) and the About LANSA information.
  5. Note: if you are not in a position to provide the dump file immediately to LANSA support, you should rename it prior to restarting your Visual LANSA application or restarting the Visual LANSA IDE to avoid the valuable information about the unhandled exception being lost or overwritten.

Refer to the Visual LANSA Administrator's Guide 10.2 Gathering Information About LANSA and 10.2.5 Dump Files for more information and instructions.