This information is for troubleshooting the short dump CALL_FUNCTION_SECSTORE_ERROR.
The system cannot read the password of the required RFC connection from the secure storage, or the password doesn't exist within the secure storage.
Use transaction SECSTORE to see the status of the secure storage.
If this seems correct, select the application "RFC Destinations" and search for the destination /RFC/.
The destination entry should have a green indicator.
If it doesn't , the message text column displays information about the error.
You can use the question mark within the end column to get an in depth description of the error and notes fix it.
If the destination /RFC/ is not listed in the secure storage, the password is lost.
If this happens, you'll use transaction SM59 "Configuration of RFC Connections" to reenter that password.
Once we save the destination, the status of the password (PW-Status) should be set to "saved" and a corresponding entry should be available in transaction "secstore".
The system cannot read the password of the required RFC connection from the secure storage, or the password doesn't exist within the secure storage.
Use transaction SECSTORE to see the status of the secure storage.
If this seems correct, select the application "RFC Destinations" and search for the destination /RFC/.
The destination entry should have a green indicator.
If it doesn't , the message text column displays information about the error.
You can use the question mark within the end column to get an in depth description of the error and notes fix it.
If the destination /RFC/ is not listed in the secure storage, the password is lost.
If this happens, you'll use transaction SM59 "Configuration of RFC Connections" to reenter that password.
Once we save the destination, the status of the password (PW-Status) should be set to "saved" and a corresponding entry should be available in transaction "secstore".
No comments:
Post a Comment