CALL_FUNCTION_SIGNON_INCOMPL 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.
If, during an RFC (Remote Function Call), an explicit user or an explicit client is requested, you must enter an explicit password for the user (see Transaction SM59).
Refer to notes 684788 and 171805.
Incomplete logon data.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
The logon data for the user <runtime parameter> is incomplete.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
The ABAP program running <runtime parameter> had to be interrupted because the logon could not be completed.
CALL_FUNCTION_SIGNON_INCOMPL - call function signon incompl CALL_FUNCTION_SEND_ERROR - call function send error CALL_FUNCTION_SECSTORE_ERROR - call function secstore error CALL_FUNCTION_RETURN_ERROR - call function return error CALL_FUNCTION_REMOTE_ERROR - call function remote error CALL_FUNCTION_RECEIVE_ERROR - call function receive error