Solution : https://service.sap.com/sap/support/notes/91980 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the issue of missing ABAP short dumps and additional information during RFC logon failures. To resolve this, the profile parameter "rfc/signon_error_log" should be added to the application server’s profile file. Setting this parameter to "1" triggers the output of the "CALL_FUNCTION_SIGNON_REJECTED" short dump under specific conditions, such as RFC calls from background processes or external programs without GUI links. Setting it to "2" enables logging in the developer trace files for issues leading to the same dump, and should be reset after analysis to prevent file size growth. The Note also references associated Notes for further instruction on logging and error handling.
Key words :
abap short dump analysis transaction, abap runtime errors occur, profile parameter rfc/signon_error_log, profile parameter rfc/signon_error_log = 3, abap short dump, abap short dumps, sap gui link, possessa gui link, log user actions, rfc caller data
Related Notes :
| 506952 | Missing output of the RFC caller data with runtime error |
| 171805 | Determining RFC client when sign-on problems occur |
| 139418 | |
| 116787 | CC-TOPIC: Remote client copy |
| 90323 | Display of RFC logon screen in SM51 |
| 51367 | RFC logon under different user or client |
| 22514 | CC-INFO: Error analysis for client copy |
| 13347 | CALL_FUNCTION_SIGNON_REJECTED |