cancel
Showing results for 
Search instead for 
Did you mean: 

CALL_FUNCTION_SINGLE_LOGIN_REJ- No authorization to log on as a Trusted System (L- RC=1 T-RC=1).

Former Member
0 Kudos

Hi All,

i have created a trusted connection(say system A_100 and B_100,---100 is a client) as per SAP note 128447 - Trusted/trusting systems

I have all required authorisation i.e s_rfcacl,S_rfc ,s_rfc_tt.

i am able to remote logon from system B_100 to system A_100 ,but issue in when i try to logon from system A_100 to system B_100.

error is -

No authorization to log on as a Trusted System (L- RC=1 T-RC=1).

i can see run time error in system B_100 as with user SAPSYS and client 000(why it is showing this user and client )

CALL_FUNCTION_SINGLE_LOGIN_REJ

Details-

Category               Installation Errors
Runtime Errors         CALL_FUNCTION_SINGLE_LOGIN_REJ
Date and Time          08.08.2014 09:07:04

Short text
     No authorization to log on as a Trusted System (L-RC=1 T-RC=1).

What happened?
     The current program had to be terminated because of an
     error when installing the R/3 System.

What can you do?
     Note which actions and input led to the error.

     For further help in handling the problem, contact your SAP administrator
     .

     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.


Error analysis
     An RFC call (Remote Function Call) was send with an invalid user ID
     "XXXX " or the caller system is not registered as a Trusted System in the
     target system.

Information on where terminated
    Termination occurred in the ABAP program "SAPMSSY1" - in
     "REMOTE_FUNCTION_CALL".
    The main program was "SAPMSSY1 ".

    In the source code you have the termination point in line 113
    of the (Include) program "SAPMSSY1".

Source Code Extract

Line  SourceCde

   83   COMMUNICATION SEND ID convid BUFFER header.
   84   IF sy-subrc EQ 0.
   85     PERFORM (sy-xform) IN PROGRAM (sy-xprog).
   86   ELSE.
   87     MESSAGE a800.
   88   ENDIF.
   89 ENDFORM.                    "cpic_call
   90
   91 *&---------------------------------------------------------------------*
   92 *&      Form  remote_function_call
   93 *&---------------------------------------------------------------------*
   94 *       text
   95 *----------------------------------------------------------------------*
   96 *      -->VALUE      text
   97 *      -->(TYPE)     text
   98 *----------------------------------------------------------------------*
   99 FORM remote_function_call USING value(type).
  100   DATA rc             TYPE i VALUE 0.
  101   DATA: l_syxform     TYPE syxform,
  102         l_syxprog     TYPE syxprog,
  103         l_cbe         TYPE i.
  104
  105 * necessary variables for class based exceptions
  106   DATA: l_root        TYPE REF TO cx_root.
  107
  108   DO.

109 *

110 * with ID 'CLException' we determine, whether the caller is

111 * class based excptions or not

112 *

>>>>     CALL 'RfcImport' ID 'Type'        FIELD type

114                      ID 'SYXForm'     FIELD l_syxform

115                      ID 'SYXProg'     FIELD l_syxprog

116                      ID 'CLException' FIELD l_cbe.

117

118     IF l_syxprog = 'JAVA'.

119       SYSTEM-CALL plugin

120                   ID 'JAVA' VALUE 'FORW_JAVA'

121                   ID 'RC'   VALUE RC.

122 *   if there is no rollout on the JAVA side which

123 *   rolls both, JAVA and ABAP, we return to the

124 *   C-Stack and reach this point

125

126 *   in case there was an rollout, the ABAP-C stack is lost

127 *   and we jump direkt to this point

128

129 *   here we trigger the rollout on this Abap side with

130 *   the following statement

131       SYSTEM-CALL plugin

132                   ID 'JAVA' VALUE 'ROLL_OUT'

I have also referred sap note-1627901 - Trusted RFC troubleshooting

No luck.

Do let me know if additional information is needed .

Kind Regards,

Sumit

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

I encountered the same issue and followed the below instructions.

http://wiki.scn.sap.com/wiki/display/ABAPConn/Create+an+RFC+trust+relationship+between+2+SAP+systems...

Former Member
0 Kudos

Hi,

I also had similar kind f dump coming in my ECC system when calling a trusted RFC from Solution manager.

When I checked both system there was a user missing in ECC side and I have created the user in ECC and after that the dump stopped coming.

User and RFC you can find withing the DUMP ins st22.

Regards,

Shanaka.

srinivasan_vinayagam
Active Contributor
0 Kudos

Dear Sumit,

You can check your service file in OS.

and you have to append the following line to the file services: sapms<SID> 3600/tcp on both server.

Regards,

V Srinivasan

Former Member
0 Kudos


HI Srinivasan,

Thanks for the reply

can you please elaborate on it .

Thanks

Sumit

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Sumit,

Check your trusted RFC and try to login with user that has same ID in both system.

Then share the results.

Divyanshu

Former Member
0 Kudos

Hi Divyanshu,

I am using Same User ID in both the system.

But the dump shows different user and client ....dont know why ?

Any idea?

Kind Regards,

Sumit

divyanshu_srivastava3
Active Contributor
0 Kudos

Check RFC, set and mark "current user option" in that.

Sriram2009
Active Contributor
0 Kudos
Former Member
0 Kudos

Hi Divyanshu,

thanks for your reply ..

This is already done settings are correct . as i said i am able to use remote logon from system B_100 to system A_100  but vice versa not possible.

when i go to system system A_100 and click on RFC and do authorisation check it gives error as

No authorization to log on as a Trusted System (L- RC=1 T-RC=1).i haved checked the required notes as mentioned but no luck .

Help

Kind Regards,

Sumit

Sriram2009
Active Contributor
0 Kudos

Hi

In both system have you added the RFC authorization object?

BR

SS

Former Member
0 Kudos

Hi Sriram,

Thanks for ur quick reply.

one question -  why it is working in system B and not in system A.

AS per note..it refers to some program correction as per release.(in my case its sap_bassis is 731)

Can you please tell me how to check if the object (as per note )exits in system B and not in in system A.

Thanks in advance.

Sumit

Sriram2009
Active Contributor
0 Kudos

Hi Sumit

1.  Is this both system Support pack level are same?

2. As you said that you SAP_Basis 7.31 - support package level?

3. Have you check the SAP note 128447 - Trusted/trusting systems they are given ABAP runtime correction  2021691 - CALL_FUNCTION_SINGLE_LOGIN_REJ and trusted RC=1

4.

one question -  why it is working in system B and not in system A.

Its may be software bug for that they give ABAP runtime correction

Regards

Sriram

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Sumit,

Check this note : 128447 - Trusted/trusting systems

and check why you get RC-1.


This will also give you a better idea why such dump comes.


Divyanshu

Former Member
0 Kudos

Hi Sriram,

  • 1.  Is this both system Support pack level are same?                                                        
  • yes

2.


As you said that you SAP_Basis 7.31 - support package level?

Kernal release 721.

support pack level -315

About software---do i need to add the correction as mentioned ?>

Regards,

Sumit

Sriram2009
Active Contributor
0 Kudos

Hi Sumit

Yes, before that you have to check the Basis support pack level. kindly follow the steps

log on to sap system and Go to System>>>Status>> At the SAP System Data box > Click Component

Version. You will see there columns for Software Component, Release,

Level, Highest Support Package, Short Description of Software Component.

Regards

Sriram