Users getting runtime error CALL_FUNCTION_SIGNON_INCOMPL in user landscape.
Along with following short message:
Incomplete logon data
Mostly these errors can be solved with a kernel update or if they happen after a system copy/upgrade/export by deleting the secstore entries. If neither of these work then user need to identify the calling client(s) involved and correct the logon information being passed to the server.
Solution
- First please check whether you performed the system copy? If yes then implement SAP document 1532825.
- Other option is to update the latest kernel patch (this solves the problem most of the time).
Having reviewed and where applicable applied the above suggestions if the problem still not solved then please try to gather more information regarding calling client so that you can correct the logon information being passed to the backend server (the underlying reason for the runtime error).
Please try following steps in order to gather more information on the calling client:
- On the corresponding backend application server set the parameter rfc/signon_error_log = 2. With this setting, in addition to the runtime error being triggered, trace output relating to this problem is also written to the developer trace files (dev_w*) on the SAP server side.
- Then please go through SAP Document 171805 & 495911.
- Once you have all these settings in place when the error next occurs you should then have more detailed information about the cause of the problem in the relevant RFC, gateway and work process traces using transaction ST11 (in addition to the runtime error itself in transaction ST22)
- Use this info for gathering the required information on the calling client. You then need to ensure that all necessary logon information is being passed by this client to the server (user, password etc.)
Note: Please ensure to deactivate both the trace and Security Audit Log and then reset the parameter rfc/signon_error_log back to its previous setting once you have completed troubleshooting this error.