CALL_FUNCTION_SECSTORE_ERROR SAP ABAP Runtime Error call function secstore error

CALL_FUNCTION_SECSTORE_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: I - Internal Kernel Error

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.

CALL_FUNCTION_SECSTORE_ERROR ABAP Runtime Error

More information about this runtime error can be found in SAP Note 1026091. Please see rfc internal error for more details about the possible cause of this runtime error and how it could be avoided.

Please see rfc internal error for more details about the possible cause of this runtime error and how it could be avoided.

P1: <runtime parameter>
P2: <runtime parameter>
P3: <runtime parameter> Error during the retrieval of logon data stored in secure storage Check the error by calling transaction sm59 and running an authorization check for destination <runtime parameter>. This should result in the same error as in the application program.

You can use transaction SECSTORE to check the secure storage. To start with, investigate the general errors that are listed when the transaction starts. If no general errors are found, choose the application /RFC/Destination -> F8 from the initial screen and check the entry '<runtime parameter>'.
(see SAP Note #1026091)

Detailed error descriptions and solutions are normally provided in transaction SECSTORE. If the problem cannot be solved using this method, proceed as follows: Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.

Please see rfc internal error for more details about the possible cause of this runtime error and how it could be avoided.

An attempt was made to make a Remote Function Call (RFC) with destination '<runtime parameter>'. An error (ID:'<runtime parameter>') occurred while logon data for this RFC connection was loading from secure storage. Please see rfc internal error for more details about the possible cause of this runtime error and how it could be avoided.

An attempt was made to make a Remote Function Call (RFC) with destination '<runtime parameter>'. An error (ID:'<runtime parameter>') occurred while logon data for this RFC connection was loading from secure storage. Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.