SECRET
ARTICLE
No ABAP Short Dump if an RFC Logon Fails
Further information about the reason for the logon problem is also
missing.
Cause and Prerequisites
ABAP short dumps are only output when an
RFC logon fails if profile parameter
"rfc/signon_error_log" is contained in the profile file of the
corresponding application server :
rfc/signon_error_log = 1
Each time there is a logon error, the short dump
"CALL_FUNCTION_SIGNON_REJECTED" is output. The contents of this
dump can be analyzed with the short dump analysis transaction (
ST22
).
rfc/signon_error_log = 2
In addition to the ABAP short dump "CALL_FUNCTION_SIGNON_REJECTED
", further information about the cause of the problem is logged in
the developer trace files (i.e. in dev_w* files).
Each RFC logon attempt is logged in the developer trace files, whether
or not the logon was successful. Make sure that this profile value is
only used to analyze the RFC logons and then reset. Otherwise the trace
files would become very large.
Solution
Add profile parameter rfc/signon_error_log for the corresponding
application server instances with the corresponding value assignment (1
or 2, see above) to the profile file. Start the server again with this
profile.
To reset the profile parameter, either remove the profile parameter from
the profile file or set the profile value to zero (i.e.
rfc/signon_error_log = 0). Then start the server again with this
profile.
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved