RFC logon screen appears
The RFC logon has failed.
This can also occur with functions (for example, release info) in transaction SM51.
If an RFC logon fails and no logon screen appears, the system writes CALL_FUNCTION_SIGNON_REJECTED or
CALL_FUNCTION_SYSCALL_ONLY to the system log (transaction SM21) and the developer trace files (dev_w*).
Cause and conditions
This situation only arises if an RFC logon fails.
If the RFC connection is in the same client with the same user, you do not need to log on. The RFC logon
screen and the entries CALL_FUNCTION_SIGNON_REJECTED or CALL_FUNCTION_SYSCALL_ONLY only occur in the following cases:
- The RFC destination uses the wrong logon data (in other words, the values entered for client, user, and password do not constitute a valid logon).
- Not all servers within a system have the same kernel release and patch level.
- The server does not have enough shared memory (
PXA memory). For further details, refer to transaction
ST22 (ABAP dump analysis) and the ABAP runtime errors PXA_NO_SHARD_MEMORY or PXA_NO_FREE_SPACE.
- The database key is different on the different servers within the system. This can be the case,
for example, if more than one network card is installed on the database server, so that some servers
identify the database server under a different host name and IP address. You may be able to see this
data in the database data section of the system status display for the relevant server. The RFC logon screen only appears in dialog mode. During the
background processsing, the
RFC communication terminates with a message that the logon data was incorrect (CALL_FUNCTION_SIGNON_REJECTED or CALL_FUNCTION_SYSCALL_ONLY in the developer trace file or the system log).
Solution
- Check the logon data against the destination used. Ensure that the user has not been locked.
- Ensure that all of the servers have the same kernel release and patch level.
- Fix the shared memory (PXA) problem.
- Ensure that all servers access the database server using the same host name and IP address.
Bemerkung:
For further help in analyzing the error, refer to
No ABAP short dump after failed RFC logon