Show TOC

CRASH.01 What Exactly does Crash Mean? Locate this document in the navigation structure

 

Symptom

Often a problem ticket is opened stating only that NWBC crashed. However, it is not possible to know whether the shell of NWBC had a problem, whether the crash happened because of the SAP GUI used as canvas, whether it is a JavaScript error or whether the ABAP runtime itself caused a rabax.

Solution

To continue with the investigation, we need screenshots of the complete desktop (or at least NWBC shell) showing exactly what “crashed”. If possible, include text that describes the exact type of crash.

  • A SAP GUI crash can be recognized by the mouse cursor that changes to include the word “crash”. In this case, it is highly recommended to first install the latest SAP GUI and retest the application. If it still crashes, see if the application can be executed directly within SAP GUI without crashing. If it crashes also in standalone case, route problem tickets to BC-FES-GUI.

  • If it is an ABAP rabax, it is important to also attach the text of the rabax (using transaction ST22). In this case, the error is usually caused by the running application, and the problem ticket needs to be routed to that specific component. The approach is to see what component triggered the rabax (class, report, etc.), to then navigate to the containing package and there to determine the assigned application component (which is the queue to be used for the problem ticket).

  • For a JavaScript error, the error is usually caused by the canvas application itself and not NBWC. The approach would be to reproduce the error without NWBC and then investigate why the web application is triggering a JavaScript error.