SECRET
ARTICLE
RFC logon screen appears
The RFC logon has failed.
This can also occur when executing functions (such as release notes)
using the 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, see transaction ST22 (ABAP dump
analysis) and the ABAP runtime errors PXA_NO_SHARD_MEMORY or
PXA_NO_FREE_SPACE .
The database ID 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. In
background processing , 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 .
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved