Sol Man RFC not connect to Dev System:

[Former Member]

Dear All,

I am going through another error msg. in Sol Man. When I double click on selected option in Configuration Tab in T'code solar02, it gives RFC error saying "RFC Error: No authorization to logon as trusted system (Trusted RC=2)." All the RFC connections are running fine to and from Sol Man - Dev System. But sm59 when I click on UniCode Test button, saying "Target is a unicode system (character size 2)."

Quick help will highly appriciated.

Thanks n Regards

Nash

[Former Member]

Thanks for resolving SolMan RFC to Dev with the following SAP Note: 128447.

Regards

eahsan.

[JPReyes]

2 User "EBAD " does not have RFC authorization (authorization object
(S_RFCACL) for user "EBAD " witl client 100.

Your user should have S_RFCACL authorization in both source and target system.

In anycase when talking about trusted connections between Solman and any of the systems in the Landscape you can check and if required regenerate the RFC's via SMSY.

In above case seems like your user is missing the authorization.

Regards

Juan

Edited by: Juan Reyes on Jan 27, 2011 3:43 PM

[Former Member]

Dear Juan n All,

Sorry! I was on sick leave.

Thanks for prompt reply.

The user "EBAD" with the client 100 is having sap_all profile.

Despite that profile does her needs to have S_RFCAL" role?

Thanks once again.

eahsan.

[Former Member]

Hello,

S_RFC_ACL is outside the scope of SAP_ALL. Please do as advised by Juan and your issue would getr resolved.

With Regards.

Ruchit.

[Former Member]

Dear friends,

The entry in sm59 and smt1 is there, connection test is also done successfully.

Today, When I check at Dev side, there were no authorization to user login.

So, this issue is with my userid or with RFC user id authorizaiton.

Towhom should i give authorization, my userId or RFC user id

Thanks n Regards.

eahsan

[nirmal_konchada]

For RFC User ID.

Regards,

Nirmal.K

[Former Member]

Dear friends,

I tried login with RFC user id many time but unable to logon it gets failed, I reset the password but no logon to RFC user id.

Thanks n Regards

eahsan.

[Former Member]

Dear Nirmal,

Thanks for your responces.

Can you tell me how assign authorization to RFC user. I am unable to logon with RFC user id to find out the miss authorizaiton with su53

Thanks n Regards

eahsan.

[nirmal_konchada]

Hi,

The below note will surely solve your problem :

128447

Regards,

Nirmal.K

[Former Member]

Hi Nirmal,

I have gone through to the note. I checked all the fields, the entries was correct in authorization. In note mention about RC=0, in my case about RC=2.

Please check the below is the error msg from st22:

-

---

Runtime Errors CALL_FUNCTION_SINGLE_LOGIN_REJ

Date and Time 25.01.2011 12:39:51

Short text

No authorization to logon as trusted system (Trusted RC=2).

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPMSSY1" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

An RFC call (Remote Function Call) was sent with the invalid user ID "EBAD "

. Or the calling system is not registered as trusted system in the

target system.

The error code of the trusted system was 2.

Meaning:

0 Correct logon as trusted system mode

1 No trusted system entry for the calling system "SMD " or the

security key entry for the system "SMD " is invalid

2 User "EBAD " does not have RFC authorization (authorization object

(S_RFCACL) for user "EBAD " witl client 100.

3 The timestamp of the logon data is invalid

The error code of the SAP logon procedure was 0.

Meaning:

0 Login was correct

1 Wrong password or invalid user ID

2 Locked user

3 Too many attempted logons

5 Error in the authorization buffer (internal error)

6 No external user check

7 Invalid user type

-

---

Thanks n Regards

eahsan.

[Former Member]

1) SMT1 setting needs to check again or needs to enter again.

2) GO to SMT1-> delete exisyng entry-> create new entry -> enter your trusted RFC name created in SMT1

3) If your target system is refreshed recently then its mendetory to delete existing entry and re-create again in SMT1.

4) ID with which you are creationg SMT1 entry that ID should exist in both system and should have S_RFCACL authorization.

5) Its better if you are using super user to create this entry in SMT1 of both system trusting and trusted system.

6) If issue still persist then do user comparison in SUIM, compare ID of two system with which you created entry in SMT1 of this two diffrent system with solman, You will requre remote comparion option to do this comparision between two satallite system of solman.

Edited by: Ritesh Sathe SAP on Jan 27, 2011 5:03 AM

[ashish_mishra2]

Hi,

Dump CALL_FUNCTION_SINGLE_LOGIN_REJ occurs when your SAP ID would not be existing in target system.

For trusted RFC to work, same SAP ID should be existing in source and target system.

Cheers !!!

Ashish

[Former Member]

Hi,

Try to use wizard in SMSY to create trusted and other RFCs 1st. This will be easy for you. And if it says RFC already exists, thn try to delete them and rereate them through wizard.

Users on both source and target system should have proper authorizations

Regards,

Tajinder

[Former Member]

Hi All,

The solution for RFC is resolved with the following SAP Note no. 128447 provided by Mr. Nirmal

Lots of thanks to all for supporting.

Regards

eahsan.

[Former Member]

If you want to logon to target system, you should maintain logon in SM59 for the RFC user.

Don't check the unicode test, but authorization test.

Regards,

[Former Member]

Hi,

You can either re-maintain the Trusted RFC connection on both side in SMT1 or create new one but delete existing connection.

Thanks,

Salim

[Former Member]

AOA S B,

I maintain using the said T'code and tried to run solar02, the same error still persist. Please provide the solution without recreating with the new one.

Thanks n Regards

M E A.

[nirmal_konchada]

Hi,

Check the RFC in Sm59 and make sure it works for authorization test without asking for password.

Make sure that in SMT1 the entry exists in both the systems.

Regards,

Nirmal.K