No Authorization to log on as a trusted system(L-RC=1 T-RC=1)

[Former Member]

Hi,

We are trying to do a POC to retrieve data from SAP ERP to SharePoint using Duet Enterprise.

We have installed Duet bits on SAP and SharePoint. 

Now, we need to establish a trusted relationship between our local SAP(trial version) and ERP . We did that using RFC Destination.

Test connection is working fine but remote logon is not working.

we are getting the error as "No Authorization to log on as a trusted system"

I have inserted a screen shot of it also.

Can anyone help me with this?

Thanks,

Akshitha.

[raphaelbertani]

The way is that:

Destiny enviroment need to have SMT1 that will use an SM59 that conect the 'from' system.

So the system that will allow trusted connection need to have this configuration.

1. Target system need to have sm59 to caller system.

2. Target system need to have SMT1 configuration that will use sm59 to caller system

3. Caller system need to have SM59 with trusted flag + correct Client + current user

4. Authority in User in Target system S_RFCACL in a role in the user ID.

With all this steps, the trusted connection can be done!

[Former Member]

After assigning the new roles to the system/communication user-id recreate the RFC and verify.

That solved my problem.

Thanks.

Gowri Shankar.

[SSSOLMAN]

Hi ,

Create a Trusting RFC's between the system and the connected systems which has the error . This will fix it .

Something like   TRUSTING@XXX_INSTALLATIONID(system)  TYPE 3

this will fix the issue .

Regards

Sweetha S

Message was edited by: sweetha shankaravelu

[Former Member]

Hello,

I have the same problem atm and in German the error says

"Keine Berechtigung zur Anmeldung via Trusted Syste m (L-RC=1 T-RC=1).

Meldungsnr. SR053"

Connection in direction

SAP_BASIS 7.31 -> 7.02  not working

SAP_BASIS 7.02 -> 7.31  working

Solutions are welcome.

Kind regards

Update:

On the target system ( ! ) I used SMT1 where I had to place a new RFC back ( ! ) to the source system. Just a RFC from source to target system is not enough. Afterwards it worked out well.

[Former Member]

Hi Serdel,

The solutions of yours worked for me.

In SMT1 i have deleted the entries and then recreated the RFC's from LMDB.

issue solved. thank you

[Former Member]

Dear Shiva,

I am happy to have helped someone in need.

Thumb up is welcome, too.

Kind regards

me

[linda_peruzzi]

Hi Akshitha,

Whatever user id you are using in your RFC, they need to have the authorization object S_RFCACL assigned to them in the system that is being pointed to.

For instance, if you are logging in with user USER01, then in the backend system in transaction SU01, they need to have a role that contains the authorization object S_RFCACL to verify they are a trusted user.

Hope this helps,

...Linda 

[Former Member]

Hi Linda ,

Thanks for the reply.

But yes. We tried this also. We have assigned the authorization object S_RFCACL to the user in the backend system before only.

But still the same error was coming.

Thanks,

Akshitha