I suggest extra troubleshooting:
- does this happen for all users, or only one? Who are the users for which it works? what is different about them?
- note that SAP_ALL is famous for not including "all" authorizations, especially some RFC related auths such as S_RFCACL (unless you specifically switch that on) and these RFC failures rarely appear in traces (but they do appear in SM21 sometimes). also, unless you are consistent with regenerating SAP_ALL after installing support packs it will get out of date and not contain everything.
- have you checked TMS logs on operating system as advised by the error message? Those logs usually have extra details. you can probably read them yourself with AL11.
- have the generated RFC destinations used by TMS been altered? You first need to identify the RFCs within STMS then go into SM59 and look at them. They should not be using "current user" authentication, because tp should be run by the sidadm or sapservice users on the OS. Maybe basis has altered those RFC.
let us know what you find.
UPDATE:
thinking about this further.
I bet you are hitting S_RFCACL errors. Give the user SAP_ALL plus a dummy role having S_RFCACL and try. Activate a trace. If I'm right, you will see the S_RFCACL proper value needed in a role. compare that to a user for whom it works. Bet it's something like that. Might as well add several S_RFC* authorizations to the dummy role too.
Message was edited by: Kesayamol Siriporn