Skip to end of metadata
Go to start of metadata

Purpose

If you experience a dump, this page helps you how to find a solution.

 


Overview

What is short dump?

If an unhandled exception or program error occurs while an ABAP program is executed, the ABAP runtime environment triggers an ABAP runtime error. The execution of the program is terminated and a detailed error log (short dump) is created and saved in the affected ABAP system. You can find these saved documents in transaction ST22.

How can I determine that a short dump occured?

If you execute a Web Dynpro application in the browser you will get one of the following screens, which verifies that a short dump has been triggered in the backend:

You can see a title 500 Internal Server Error with termination RABAX_STATE on the browser screen. It can have 2 layouts:

  1. New style
  2. Old style

How to find a solution?

In the Analyzing the dump section of this document you can see many hints about the effective way how to find yourself a solution to solve the dump finally.

 

 


 

Analyzing the dump

Search for possible solutions

After you have found the corresponding dump in ST22, please open it up with the Long Text version. This case you will see every detailed information why and where is dump occured.

1. Header

First of all, check the header information of the dump. This will tell you the application component, program name, error type and category.

How to find a SAP note for this?

In SAP note search please enter the application component and search for the ABAP program name and/or the runtime error.

Example search terms based on the above header:
  • BC-WD-ABA | ASSERTION_FAILED
  • BC-WD-ABA | CL_NW7_VIEW_ELEMENT_ADAPTER

If you do not find any relevant note, go ahead with the other sections.

2. Additional information

In the Error analysis and How to correct the error section of the dump there are some hints about the reason and possible solutions. You can also search for these hints in SAP note search.

  

Example search terms based on the above screenshot:
  • may contain fatal script
  • UNCAUGHT_EXCEPTION
  • CX_WD_GENERAL

If you do not find any relevant note, go ahead with the other sections.

3. Source code snippet

This is the most informative section of the dump. You can find the concrete code line (marked with >>>>> symbol), where the program experienced something wrong during runtime and had to throw this dump. Here you can search for SAP notes

Example search terms based on the above screenshot:
  • assert 1 = 0
  • We got an event for a non-existing UI-control
  • l_event_handler
  • ListAccess

If you do not find any relevant note, go ahead with the other sections.

4. Active calls/events

This section shows the program call stack.

Example search terms based on the above screenshot:
  • DISPATCH_NW7_EVENT
  • CL_WDR_CLIENT_SSR_LS
  • GET_CLIENT_UPDATES
  • CL_NW7_VIEW_ELEMENT_ADAPTER

 

 


 

Related Content

Related SAP Notes/KBAs

SAP Note 2102812: Search for correction notes in transaction ST22

SAP Note 1234433: Search for correction notes in transaction ST22