03-12-2013 10:03 PM
I am working on a copy of the productive system. The secure store was cleaned up according to SAP note 816861, transaction SECSTORE shows only one entry (BC_INIT), which is green. However when I try to save credentials to any RFC connection I get an error message:
"Access to entry SAPOSS in the secure storage denied"
There are no additional hints in SM21, ST22 or SLG1 about this issue. Could this problem be related to SAP note 1180143 where just an authorization is missing? I am already working with SAP_ALL however.
Regards,
Mark
03-12-2013 10:51 PM
That is because you have deleted SAPOSS from SECSTORE. Just delete the RFC entry and re-create it. If you still can't store anything in the SECSTORE, try to use report RS_TT_CLEANUP_SECSTORE.
Instead of deleting everything in SECSTORE I myself prefer to migrate the entries after a system copy.
03-12-2013 10:51 PM
That is because you have deleted SAPOSS from SECSTORE. Just delete the RFC entry and re-create it. If you still can't store anything in the SECSTORE, try to use report RS_TT_CLEANUP_SECSTORE.
Instead of deleting everything in SECSTORE I myself prefer to migrate the entries after a system copy.
03-13-2013 4:47 AM
hi Mark,
Please check this SAP note.
Note 1532825 - Deleting SECSTORE entries during system export/system copy
Regards,
03-13-2013 8:57 AM
Thanks for your replies, I really appreciate your suggestions. Adjusting SECSTORE wasn't possible because SECSTORE told me that it cannot modify the entries.
So far I already tried:
1. report RS_TT_CLEANUP_SECSTORE
2. deleting the RFC connection and creating it again
3. a kernel patch from 7.00 243 -> 7.20 402
Unfortunately the error message remains unaffected, but I keep up fighting.
Regards,
Mark
03-13-2013 9:12 AM
hi Mark,
Please also check this Note
1016348 - Secure storage after changing the installation number
Regards,
03-13-2013 9:49 AM
I traced my actions in SM50, this provided helpful information. The problem is fixed now. During the system copy someone must have truncated table RSECACHK. This caused the permission problem -> "access denied". Now I can continue my work.
11-20-2015 10:15 AM