CALL_RPERF_SLOGIN_READ_ERROR 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.
Try to perform the call without a trust relationship. Otherwise, a
trust relationship needs to be set up to system <runtime parameter> for user <runtime parameter>.
Caller system........: <runtime parameter>
Caller..............: <runtime parameter>
Caller client...........: <runtime parameter>
RFC user ID...............: <runtime parameter>
RFC client.............: <runtime parameter>
Caller SID..........: <runtime parameter> (only for external trusted systems, such as
domain) Transaction code.: <runtime parameter>
No valid trusted entry for system <runtime parameter>.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
A Remote Function Call (RFC) was submitted from system <runtime parameter> with a trust
relationship. There is no valid trust relationship to this system
however.
User <runtime parameter> in client <runtime parameter> is system <runtime parameter> has attempted to submit a trusted
call using user ID <runtime parameter> and client <runtime parameter>. (Note: In Releases prior to 4.0,
no information is provided about the caller and the caller system).
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
CALL_RPERF_SLOGIN_READ_ERROR - call rperf slogin read error CALL_RPERF_SLOGIN_AUTH_ERROR - call rperf slogin auth error CALL_METHOD_RETURN_ERROR - call method return error CALL_METHOD_PARMS_ILLEGAL - call method parms illegal CALL_METHOD_NOT_IMPLEMENTED - call method not implemented CALL_METHOD_NOT_ACCESSIBLE - call method not accessible