CALL_FUNCTION_SYSCALL_ONLY SAP ABAP Runtime Error call function syscall only

CALL_FUNCTION_SYSCALL_ONLY is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: F - Installation Errors

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

CALL_FUNCTION_SYSCALL_ONLY ABAP Runtime Error

If an error occurs in the evaluation of the trusted-trusting relationship, an error code from the trusted system is set. If an error then occurs during the logon, an error code from the logon procedure is set. Both sets of return codes are listed below.

The failed logon in the trusted relationship is the result of an invalid trusted key entry for system <runtime parameter> or for example that the trusted system data is no longer valid due to a timeout.

The error code from the trusted system was <runtime parameter>.

Meaning:
0 Correct logon as trusted system session.
1 No trusted system entry for caller system <runtime parameter>, or the security key entry for system <runtime parameter> is invalid.
2 User <runtime parameter> does not have RFC authorization (authorization object (S_RFCACL) for caller <runtime parameter> with client <runtime parameter>.
3 The time stamp of the logon data is invalid

The error code of the SAP logon procedure was <runtime parameter>.

Meaning:
0 USER_OK Login was correct
1 USER_NOT_ALLOWED User or password incorrect
2 USER_LOCKED User locked
3 STOP_SESSION Too many logon attempts
5 BAD_BUFFER Error in the authorization buffer
6 CUA_MASTER_RECORD No external user check
7 BAD_USER_TYPE Invalid user type
8 USER_NOT_VALID Validity of the user exceeded 9 SNC_MAPPING_MISMATCH User does not match SNC name
10 SNC_REQUIRED Secure connection required
11 SNC_NAME_NOT_IN_ACL User not found in USRACL(EXT) 12 SNC_SYST_NOT_IN_ACL System not found in USRACL(EXT)
13 SNC_MAPPING_NO_MATCH No matching user found
14 SNC_MAPPING_AMBIGUOUS Multiple matching user found
20 TICKET_LOGON_DISABLED Logon process deactivated
21 TICKET_INVALID Data received is not a SSO ticket
22 TICKET_ISSUER_NOT_VERIFIED Digital signature not verified 23 TICKET_ISSUER_NOT_TRUSTED Ticket issuer nicht trusted
24 TICKET_EXPIRED Ticket expired
25 TICKET_WRONG_RECIPIENT Wrong recipient
26 TICKET_WITH_EMPTY_USERID Ticket contains an empty User ID
30 X509_LOGON_DISABLED Snc/extid_login_diag = 0
31 X509_BASE64_INVALID Cert not base64-encoded
32 X509_INVALID_SERVER X.509 not provided by ITS
33 X509_HTTPS_REQUIRED Cert not sent via SSL
34 X509_MAPPING_NO_MATCH No matching account
35 X509_MAPPING_AMBIGUOUS Multiple matching accounts
40 EXTID_LOGON_DISABLED snc/extid_login_diag = 0
41 EXTID_MAPPING_NO_MATCH No matching account
42 EXTID_MAPPING_AMBIGUOUS Multiple matching accounts
50 PASSWORD_LOGON_DISABLED login/disable_password_logon
51 PASSWORD_IDLE_INIT login/password_max_idle_init
52 USER_HAS_NO_PASSWORD USR02.CODVN = 'X' (flag)
53 PASSWORD_ATTEMPTS_LIMITED Lock counter exceeded
54 PASSWORD_IDLE_PROD login/password_max_idle_prod.
100 CLIENT_NOT_EXIST Client does not exist
101 CLIENT_LOCKED Client locked
200 MULTIPLE_RFC_LOGON login/disable_multi_rfc_login The function module called was <runtime parameter>. Caller system........: <runtime parameter>
Caller..............: <runtime parameter>
Client of calling program..: <runtime parameter>
RFC user ID...............: <runtime parameter>
RFC client.............: <runtime parameter>
Transaction code....: <runtime parameter>
Logon return code..: <runtime parameter>
Trusted return code: <runtime parameter>
Note: In Releases < 4.0, not all information about the caller is provided. You are not authorized to logon to the target system (error code <runtime parameter>). Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.

RFC calls (Remote Function Calls) were sent with invalid user ID <runtime parameter>. The receiving system treated the first call as a system call and therefore accepted it without a valid user ID. The last call was sent to a non-system function module however and was therefore rejected.

The system function modules include RFC_PING and RFC_SYSTEM_INFO.

The action was executed by caller <runtime parameter> with client <runtime parameter> from system <runtime parameter> using transaction <runtime parameter>. Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.