How To Fix TPDA350 - No hay ningún modo debug disponible

SAP Error Message - Details

• Message type: E = Error

• Message class: TPDA - Debugger

• Message number: 350

• Message text: No hay ningún modo debug disponible

¿Qué causa este problema?

In "Non-Exclusive Mode", the ABAP Debugger was unable to reserve a
work process exclusively for this debugging session. The reason for this
is that all available work processes were already in use with other
debugging sessions.

El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.

Restrictions in "Non-Exclusive Mode":
For every Debugger interaction, a database commit must be triggered.
As a result:
- You cannot debug between "SELECT ... ENDSELECT" (short dump in
Debugger)
- If the debugging session is cancelled, the database content can become
inconsistent.
Since there can be no database inconsistencies in production systems,
the "Non-Exclusive Mode" is not possible there. Instead of starting the
Debugger in "Non-Exclusive Mode", the system triggers the short dump
"DEBUGGING_IMPOSSIBLE".
The number of work processes exclusively available for debugging in
production systems is defined in the profile parameter for the number of
dialog work processes as follows: "rdisp/wp_no_dia / 2"
In non-production systems, this number is set using the profile
parameter "rdisp/wpdbug_max_no". It is recommended that
"rdisp/wpdbug_max_no" is roughly equal to "rdisp/wp_no_dia / 2".
On the other hand, the default value "rdisp/wpdbug_max_no = 1"
is almost always too low.

Respuesta del sistema

¿Cómo arreglar este error?

In the meantime, a work process may have become free for exclusive use
by the Debugger, so that you could try to switch to "Exclusive Mode" by
choosing "Debugger -> Exclusive Debugging Mode On" from the menu.

Procedimiento para Administradoras de Sistemas

Extracto de mensaje de error del sistema SAP. Copyright SAP SE.