What should be considered when troubleshooting


Errors in control processing usually only occur when the automation queue is synchronized. The synchronization takes place either explicitly by calling the method CL_GUI_CFW => FLUSH or implicitly after running through the last PBO module.

If the error occurs during explicit synchronization, the exception of the method is thrown. If the error occurs during implicit synchronization, a short dump usually occurs. You can avoid the short dump by processing special events of the control framework.

Initially, the triggering of the exception only indicates that any method call on a control at the front end could not be successfully issued. Therefore, it must now be narrowed down which control on the front end led to this exception and why the control triggered this exception. To do this, use the debugger:

  1. Run the program again in the debugger.

  2. Go to the debugger settings and select the Automation Controller: Always process jobs synchronously checkbox. This setting means that the automation queue is synchronized after each method call.

  3. Debug across each method call. Note that the is set after the incorrect method call, provided you have queried the exception handling of the method in your application program. Otherwise you will receive a short dump again at this point.

  4. Check why the method call failed.


In the event of an error, you should first run the sample programs for the respective control casing. If an error occurs here too, there is an installation problem with the local SAP GUI.


After the occurrence of a control, i.a. can no longer be worked on. Above all, it should be noted that entries in the automation queue after the error were no longer made.

If the error occurred the first time the automation queue was synchronized, the automation controller may no longer be active. This means that all subsequent control calls abort with a.