Trusted/ Trusting RFC Questions
Hi,
I noticed some problems with my trusted/ trusting relationships and was hoping some peole could shed light on the situation.
Where is the configuration of trusting connections in SMT2 used? How is it used?
Could someone please define the purpose of configuring SMT2 and SMT1. I have looked all over for an explanation of the trustING portion of the trusted/trusing relationship and have not found nothing to clarify this piece of the puzzle.
Hi kaustubh,
1. Create a RFC-Destination (in SolMan) in SM59 (i.e. name: C00 ), with satellit adress and checked Trusted=No.
No further login data to fill out. This is a separate RFC (so I did).
2. In SMT1 you add a trusted system with the destination above (i.e. C00 ).
3. Doing Points 1 + 2 also in satellit system
4. Create RFC-Destinations (i.e. with wizzard)
5. Check Trusted = yes
Hope it helps you.
Regards,
René
Edited by: Rene Hinsch on Jun 4, 2008 1:46 PM
Similar Messages
-
Trusted RFC and Remote logon not possible due to Nat'd IP addresses
Hi,
We are trying to connect our SolMan 4 to our cusotmers ECC 6 and BI7 systems, the systems are off site and the IP addresses for the customers systems are nat'd when they come in and go out from our Network.
The problem we get is that we cannot set up Trusted systems or Remote Logon to these systems due to issues with the Nating of the IP adresses. We can set up all standard RFC's after adding the the appropriate addresses into the hosts file and they work fine. But the trusted RFC does not set up properly and the BACK rfc from the satelite system does not get set up properly. What appears to happen is that when you try to start a remote session SAP goes to the satelite system and finds the Instance Name and the local IP address rather than the NAT'd IP address and try's to open a session from there. I found this by going into the trusted RFC in SM59 and then going to Extra's, System Information, Target System, this then tells me the Target System information, where it shows the System ID and IP address (which is the incorrect IP address).
Anyone know how we can get the system to try to have the correct IP adress in the target system information so that we can get Remote Logon's to work??
CheersHi Carl,
Based on your explanation about Nating,, how will the RFC determine to connect to Solmans internal IP after it has been directed to the IP for the Router connection.
I feel it is like configuring a jump of RFCs from one IP to another in a single chain.
Can this be done ?? I mean we have to specify an IP in the RFC connection right.. so how will the automatic jumping of IPs be done.
Sorry not answering the question but its very interesting and wanted to know.
Also went trough note # 148832, might help.
Regards,
Kaustubh.
Edited by: Kaustubh Krishna on Aug 13, 2009 12:17 PM -
Trusted RFC User : Current User or Fixed?
Hello All,
We will be implementing Service Desk and Charm.
My question is that while creating the Trusted RFCs initially, which user-id option we should give?
Should it be the Current User? Or a fixed Dialog User-id which exists?
Why I am asking is that I am not quite sure in which all cases this Trusted RFC is used. If it is used in critical operations we should not give a fixed user-id which has plenty of access. It should be Current User.
IF it is a fixed User-Id - what all authorizations it should have in SolMan and in the Satellite Systems?
Thanks!Hi,
THe user you need can be a current user, however this user needs to be setup in both systems; for a better sypnosis on the setup scenario for trusting RFCs please kindly refer to this note
128447 Trusted/trusting systems
more information are also available in
http://help.sap.com/saphelp_nw04/helpdata/en/22/042671488911d189490000e829fbbd/frameset.htm
Also please remember to regenerate the RFC in SMSY, but before that, you have to
DELETE the following in BOTH solman and satellite system
- the relevant RFCs
- the relevant users created by SMSY when generating the RFCs
- the respective SID in both txn SMT1 and SMT2 (In Solman, you have to
delete the satellite's SID. In satellite system, vice versa)
After you have deleted both, please regenerate the RFCs in SMSY and it
should recreate everything for you again that you have deleted. Please
note that the user you use to generate the RFCs have to exist in both
systems, also the authorization object S_RFCACL have to be included in
user for BOTH system (which is not included in SAP_ALL, SAP_NEW).
Hope this helps.
Cheers
SH -
Trusted RFC: "jumping to PRD system from DEV via SOLMAN"
Hallo!
I have the following question regarding the Trusted RFC generally in SOLMAN area and better especially within ChaRM.
We have SOLMAN and 3 satellite systems DEV, QAS and PRD.
When we generate Trusted RFC connections from SOLMAN to these satellite systems, we become scared about the following scenario:
A user accesses to DEV system and goes via Trusted RFC to SOLMAN.
From SOLMAN he chooses the Trusted RFC to PRD system and goes into PRD system.
The question:
How can this identification gap/problem be solved?
Thank you very much indeed!
H. ThomassonHi Thomasson,
You can restrict the access of your solman system from your DEV system.
Disable the trusted relationship in the RFC that points to Solman from Dev system.
Hope this helps.
Regards,
Kiran. -
Trusted RFC: "jumping to PRD system from DEV"
Hallo!
I have the following question regarding the Trusted RFC generally in SOLMAN area and better especially within ChaRM.
We have SOLMAN and 3 satellite systems DEV, QAS and PRD.
When we generate Trusted RFC connections from SOLMAN to these satellite systems, we become scared about the following scenario:
A user accesses to DEV system and goes via Trusted RFC to SOLMAN.
From SOLMAN he chooses the Trusted RFC to PRD system and goes into PRD system.
The question:
How can this identification gap/problem be solved?
Thank you very much indeed!
H. ThomassonHolger,
First of all the user that tries to launch the TRUSTED RFC needs to have an active user in the satellite system he/she tries to reach.
Secondly, this user needs to have the authorization object S_RFCACL assigned to its user.
You can manually change this TRUSTED RFC to 'Logon Screen' if you like.
Roel -
BPMON Alerts Detail Info - how to switch to use TRUSTED RFC ?
Hello Experts,
we have configured BPMON for our customer and it works fine, alerts are flowing in.
Now the users start using it and they complain about having a logon prompt popup every time the hit "Detail info" button to jump into satellite system to see alert details. It's very annoying when they need to check many alerts simultaneously.
So I investigated and found that the function is using LOGIN type RFC for the logon and it seems that SAP designed it to work this way, as SAP's own DEMO shows same thing.
Question: Is there a legitimate way to make BPMON function use TRUSTED RFC to show alert details instead of LOGIN RFC ?
By "legitimate" I mean, I know the LOGIN RFC can be "adjusted" to behave like TRUSTED, but that is not "legal" fix especially in production.
Appreciate any comments.
Thanks
ElenaHi Elena
I assume you are using Login RFC in SolMan setup.
If you switch current RFC to Trusted RFC, if the user has Trusted RFC profile and same user exist in both system, user can use trusted connection.
Please go to transaction SolMan setup, and side bar menu managed system configuration and open managed config screen to target system. In the 3 rd step of the wizard, there is a place to configure RFC.
In case if BPMon, Read RFC is used for data collection(as of SAP TMW is used instead of READ).
And then there are 3 RFC TMW, Trusted and last one(RFC for Solution manager).
When you press the detail info button, last RFC is used. To this RFC type, you can assign RFC Login( this will ask login screen by default) or Trused RFC. I think you assin RFC login right now. That's why you have popup.
If you switch this to Trused one, Trused RFC is used.
Best Regards
Keiji -
ChaRM: Trusted RFC a must?
Hi!
1) Are the Trusted RFC a "must" within ChaRM approach, If Yes in which clients?
2) Which authorizations does the user for the RFC connection between SOLMAN and satellite system need (besides authorization object S_RFCACL)
Thank you very much!
ThomHi.
I guess it's not mandatory but in most cases kind of annoying not to use Trusted RFC.
One example is the action "Logon to System" which is performed from within a Change Document. User may logon to the system where he wants to perform developement in without being prompted for user name and password.
Which basically is the answer to the question "in which clients?": all the ones you want to work in.
As for RFC authorization:
The users SOLTMW<SID><CLIENT> and SOLMAN<SID><CLIENT> for Non-Trusted RFCs are being generated and should get the correct profiles automatically.
SOLTMW<SID><CLIENT>
S_BDLSM_READ
S_CSMREG
S_CUS_CMP
S_TMW_CREATE
S_TMW_IMPORT
SOLMAN<SID><CLIENT>
S_BDLSM_READ
S_CSMREG
S_CUS_CMP
The users who use Trusted RFC should have objects S_RFCACL and S_RFC.
And of course all other authorizations they need for the work in the target system.
Hope this helps.
/cheers -
Hello
I am trying to connect my ERP and BW systems to Solution Manager but I can't make Trusted RFC connections.
When I checked SM59 on three systems I see `You are not authorized to logon to the target system (error code 1)
I did successfully installed Solution Manager, did initial and basic settings. I created SOLMAN_ADMIN user every system assigned it SAP_ALL, SAP_NEW and created a role with S_RFCACL authorization object, (I assigned full authorization on all objects on that role). I did add IP numbers and hostnames to hosts file but still same. When I test connection I get success but authorization check always fails.
I both tried from SOLMAN_SETUP > Managed Systems and also after clearing all RFCs and trusted system entries from SMT1 and SMT2, I added RFCs from SMSY but I get same results.
Side note, all servers are in the same subnet but Solution Manager server belongs to different domain.
My main reason to implement trusted rfc is I need to implement ServiceDesk and I have to test it before going live, so all data on Solution Manager is expendable.
My systems are
ERP: Windows 2003 R2 x64, SQL 2005 SP3, ERP EHP4 SP5
BW: Windows 2003 R2 x64, SQL 2008 SP1, NW 7.0 EHP2 SP6
Solman: Windows 2003 R2, SQL 2008 SP1, EHP1 SP7
What am I doing wrong there?Hello,
Are you letting the wizard create the RFC's for you?
On the Client tab in SMSY?
Also you assigned S_RFCACL what about S_RFC?
I would ask you to check the logon tab and make sure Current user is not checked.
Also, please review this Note 128447 - Trusted/trusting systems
This should help resolve.
Regards,
Paul -
Trusted RFC - TRUSTING_SYSTEM@P11and SM_P11CLNT040_TRUSTED
Dear SAP colleagues,
From SAP Solution Manager, I want to connect a satellite system (P11).
I have currently 2 Trusted RFC :
1. TRUSTING_SYSTEM@P11
2. SM_P11CLNT040_TRUSTED generated from SMSY.
I am currently re-checking all RFC of SOLMAN and I am wondering why 2 TRUSTED RFC which are directed to the same system and client are necessary ?
In other term, what is RFC TRUSTING_SYSTEM@P11 used for ?
Is this RFC only created during system installation ?
Best regards
P. C.Hi PC,
The Trusted system RFC TRUSTING_SYSTEM@P11 is automatically created while establishing a trusted system access using SMT2.
Please refer to the below link:
http://help.sap.com/saphelp_nw04/Helpdata/EN/8b/0010519daef443ab06d38d7ade26f4/content.htm.
Its not always necessary to have two trusted access. Mainly used to jump into the other satellite system without giving userID and password and authorizations pays a key role here.
The usage depends on the scenario. It is normally required for the system monitoing functionality and you do have an option to define the Trusted RFC for monitoring, when you setup system monitoring. It also plays a key role in Central system adminstration.
Hope this helps, Revert for any issue.
Thanks,
Jagan
Edited by: jagadheeshan govindasamy on Oct 7, 2009 7:50 AM -
Dears,
I want to know that in which particular case we should create RFC between systems.I am aware of like how we create trusted RFC and what benefits we get by it but dnt know as per standred in which scnerio we should create it.
Please suggest.
Shivam Mittal
Edited by: Shivam Mittal on Jan 9, 2009 9:29 AMHello Shivam,
trusted RFCs are usually used when data must be accessed in another system with the same user (for checking the authority).
For example:
System A: HR system with the personal data
System B: Document Management System with the document info sets, etc.
Now if a HR user looks in the HR system for a specific personal number and wants to see the documents for this person. The HR data itself is located in system A, but the documents are located on system B in the document info sets. Now you must have a remote connection that allows you to access the documents in system B with the same user as you have logged on the HR. Now you can check authority in system B too, because you have logged in with the same user.
Regards
Stefan -
Creation of trusted RFCs between two systems
Hai,
Can anyone help me to create TRUSTED RFC between two systems ie Solution Manager and the Production. To carry out Service desk facility.Dear Mohan,
You can create RFC's in the Solution manager system using T-Code SMSY. there you find all your installed systems select the system from the left hand side under Landscape Components click on Application Server ABAP on the right hand side you will find a tab client in this screen select the client for which you want to create TRFC. Go to change mode and click on the button Generate RFC with Assistance. Carry out the wizard for creating the RFC's... -
Trusted RFC connection Problem
Hello,
Trusted RFC connection between two systems when the results are negative. The error we get is "You Are Not authorized to logon to the target system (error code 1)." But everything looks smooth (kernel, logfiles, etc.).. S_rfc users and has s_rfcacl objects. Where do you think could be problem?
RFC trace log files;
dev_rfc0
Trace file opened at 20100503 232709 GTB Daylight Time, SAP-REL 700,0,236 R
======> You are not authorized to logon to the target system (error code 1).
ABAP Programm: RSRFCPIN (Transaction: SM59)
Called function module: RFCPING
User: P0326 (Client: 100)
Destination: RFC001 (handle: 2, 21766343, {3CF256DF-FE74-F105-BF85-000C29E0B2F6}
dev_rfc1
Trace file opened at 20100503 233011 GTB Daylight Time, SAP-REL 700,0,236 R
======> No authorization to logon as trusted system (Trusted RC=1).
ABAP Programm: SAPLSYST (Transaction: SM59)
Called function module: ABAP4_LEAVE_TO_TRANSACTION
User: P0326 (Client: 100)
Destination: RFC001 (handle: 2, 21951359, {A7F256DF-F7BE-F119-BF85-000C29E0B2F6}
Trace file opened at 20100503 233115 GTB Daylight Time, SAP-REL 700,0,236 R
======> Name or password is incorrect (repeat logon)
ABAP Programm: RSRFCPIN (Transaction: SM59)
Called function module: RFCPING
User: P0326 (Client: 100)
Destination: RFC001 (handle: 2, 22021687, {D1F256DF-90D2-F15E-BF85-000C29E0B2F6}
Trace file opened at 20100503 233127 GTB Daylight Time, SAP-REL 700,0,236 R
======> You are not authorized to logon to the target system (error code 1).
ABAP Programm: RSRFCPIN (Transaction: SM59)
Called function module: RFCPING
User: P0326 (Client: 100)
Destination: RFC001 (handle: 2, 22034437, {D8F256DF-78D3-F1BE-BF85-000C29E0B2F6}
Regards
ismailHi,
In addition to the auth object, First make the entry in SMT1 with the normal RFC here the rfc should not be enabled as trusted.
Then create an entry in the target system as well, one the entries are made in tcode SMT1 in both the systems, then enable both the RFC's as trusted RFC it will work fine then.
Regards,
Vamshi. -
Minimum Trusted RFC's for productive system
Hi!
We have very strict requirements dealing with set up of Trusted RFC for productive system for ChaRM approach in SOLMAN.
Can some one tell me which Trusted RFC's and users for the productive system do I need?
a) Trusted RFC is not mandatory for the productive system
b) Trusted RFC only in productive system, client: 000, users: 1 communication user and 1Dialog user
c) Trusted RFC in productive system for each client with users...
Thank you very much!
H. ThomassonCreate the function modules in SE37 and set the remote-enabled flag in the attributes section. Then import them into XI.
Create a custom Z table through SE11 on each system to store any data, and the code in each function module would reference it. (Either that or just hard-code everything)
In short yes it can be done through SE37, no you don't need SE38.
I think you're talking about function groups which is a container for the function module. You can do everything through SE37 if you use the Goto->Function Groups-> Create Group option and give it the same name as your Function Module. -
Trusted RFC not working for different user , working for same user
Dear All,
I have two SAP system - One Solman (7.0) and another ECC 6.0 (SR3) on HPUX box with Oracle DB (Unicode).
I want to establish Trust relationship between these system.
I have configured the same, as per the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/8b/0010519daef443ab06d38d7ade26f4/content.htm
and note 128447.
My requirement is one user X in solman client 001,
will execute some test plan (Tcode stwb_2) which will take the control to ECC 6.0 client 200, execute the tcode as user Y and come back in Solman again.
The user X (SAP_ALL) exists in Solman - client 001 and user Y (SAP_ALL) exists in ECC 6.0 - client 200.
In ECC 6.0 client 200, I have created a role ZRFCACL with the following and assigned to the user Y (as per the above help / note):
Role : ZRFCACL
Auth. Obj: S_RFCACL
Value assigned to fields are:
RFC_SYSID : SOL
RFC_CLIENT: 001
RFC_USER : X
RFC_EQUSER: N
RFC_TCODE : *
RFC_INFO : *
ACTVT : 16
Whenever the user X is trying to execute the test from solman, he is getting the error : "No authorization to log on as trusted system (RC = 0)"
Each time the user is trying the above, in ECC 6.0, the following dump is occuring:
CALL_FUNCTION_SINGLE_LOGIN_REJ under username SAPSYS
I have assigned the role ZRFCACL to user X in Solman also.
Next, I have performed the following check:
created one user M in both system
created the role ZRFCACL2 in ECC 6.0 client 200 as follows and assigned the role to user M:
Role : ZRFCACL2
Auth. Obj: S_RFCACL
Value assigned to fields are:
RFC_SYSID : SOL
RFC_CLIENT: 001
RFC_USER : ''
RFC_EQUSER: Y
RFC_TCODE : *
RFC_INFO : *
ACTVT : 16
Assigned SAP_ALL to user M in both system (So the user M in Solman does not have ZRFCACL2).
This time, the trust relationship worked and no dump got generated.
I have also checked the thread Trusted RFC do not work
but unable to resolve the issue.
Any suggestion where the things are going wrong in this / what else I need to check or this is not possible at all?
Thanks in advance for your help.
SudipHi Valdecir,
Thanks for the reply. I am providing the detail of the generated dump below:
Please check in case any clue is there.
Runtime Errors CALL_FUNCTION_SINGLE_LOGIN_REJ
Date and Time 12.08.2008 18:59:32
Short text
No authorization to logon as trusted system (Trusted RC=0).
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 "98819 "
. Or the calling system is not registered as trusted system in the
target system.
How to correct the error
The error code of the trusted system was 0.
Meaning:
0 Correct logon as trusted system mode
1 No trusted system entry for the calling system "SOL " or the
security key entry for the system "SOL " is invalid
2 User "98819 " does not have RFC authorization (authorization object
(S_RFCACL) for user "98819 " witl client 001.
3 The timestamp of the logon data is invalid
The error code of the SAP logon procedure was 1.
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
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 16192
EM...... 4189840
Heap.... 0
Page.... 0
MM Used. 1194640
MM Free. 2992576
User and Transaction
Client.............. 000
User................ "SAPSYS"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "489F2BD6C36D0F12E10000000A0A049E"
Program............. "SAPMSSY1"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "SOL"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and non-transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 001
User................ 98819
Transaction......... "SMSY"
Call Program........."SAPLSRTT"
Function Module..... "SCCR_GET_RELEASE_NR"
Call Destination.... "SM_RD3CLNT200_TRUSTED"
Source Server....... "gcbsolm_SOL_00"
Source IP Address... "10.10.4.206"
Additional information on RFC logon:
Trusted Relationship "X"
Logon Return Code... 1
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
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 67
of the (Include) program "SAPMSSY1".
Source Code Extract
Line
SourceCde
37
endmodule.
38
39
module %_rfcdia_call output.
40
"Do not display screen !
41
call 'DY_INVISIBLE_SCREEN'.
42
perform remote_function_diacall.
43
endmodule.
44
45
module %_cpic_start.
46
if sy-xprog(4) = '%RFC'.
47
perform remote_function_call using rfctype_external_cpic.
48
else.
49
call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
50
perform cpic_call using convid.
51
endif.
52
endmodule.
53
54
55
form cpic_call using convid type c.
56
communication send id convid buffer header.
57
if sy-subrc eq 0.
58
perform (sy-xform) in program (sy-xprog).
59
else.
60
message a800.
61
endif.
62
endform.
63
64
form remote_function_call using value(type).
65
data rc type i value 0.
66
do.
>>>>>
call 'RfcImport' id 'Type' field type.
68
if sy-xprog = 'JAVA'.
69
system-call plugin
70
id 'JAVA' value 'FORW_JAVA'
71
id 'RC' value rc.
72
if there is no rollout on the JAVA side which
73
rolls both, JAVA and ABAP, we return to the
74
C-Stack and reach this point
75
76
in case there was an rollout, the ABAP-C stack is lost
77
and we jump direkt to this point
78
79
here we trigger the rollout on this Abap side with
80
the following statement
81
system-call plugin
82
id 'JAVA' value 'ROLL_OUT'
83
id 'RC' value rc.
84
else.
85
perform (sy-xform) in program (sy-xprog).
86
rsyn >scont sysc 00011111 0.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080812
SY-UZEIT
185932
SY-XPROG
SAPRFCSL
SY-XFORM
READ_SINGLE_LOGIN_DATA
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM SAPMSSY1 SAPMSSY1 67
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30
%_RFC_START
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name REMOTE_FUNCTION_CALL
%_DUMMY$$
0000
0000
2222
0000
SY-REPID
SAPMSSY1
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
SYST-REPID
SAPMSSY1
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
HEADER
000000000000
000000000000
TYPE
3
0000
0003
SY-XPROG
SAPRFCSL
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5455445422222222222222222222222222222222
3102633C00000000000000000000000000000000
%_ARCHIVE
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RC
0
0000
0000
SY-XFORM
READ_SINGLE_LOGIN_DATA
000000000000000000000000000000
000000000000000000000000000000
544455444445444445445422222222
2514F39E7C5FCF79EF414100000000
%_SPACE
0
0
2
0
No. 1 Ty. MODULE (PBO)
Name %_RFC_START
%_PRINT
000 0###
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RFCTYPE_INTERNAL
3
0000
0003
Internal notes
The termination was triggered in function "ab_xsignon"
of the SAP kernel, in line 2491 of the module
"//bas/700_REL/src/krn/rfc/absignon.c#9".
The internal operation just processed is "CALY".
Internal mode was started at 20080812185932.
Calling system.....: "SOL "
Caller.............: "98819 "
Calling client.....: 001
RFC user ID........: "98819 "
RFC client.........: 200
Trusted return code: 0
Logon return code..: 1
Transaction code...: "SMSY "
Active state.......: "-782823270"
Note: At releases < 4.0, the information for the caller is not
available.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x4000000002b43cb0 SignOnDumpInfo + 0x280 at absignon.c:2491 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000002b3f2f0 ab_xsignon + 0xb30 at absignon.c:876 [dw.sapRD3_DVEBMGS00]
(5) 0x4000000002aa4cb0 ab_rfcimport + 0x1ad0 at abrfcfun.c:3599 [dw.sapRD3_DVEBMGS00]
(6) 0x40000000040f4a80 Z8abjcalyv + 0x500 [dw.sapRD3_DVEBMGS00]
(7) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003f538b0 Z9abxeventPKt + 0xb0 at abrunt1.c:281 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003f360a0 ab_dstep + 0x280 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001cb4600 dynpmcal + 0x900 at dymainstp.c:2399 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cab0e0 dynppbo0 + 0x280 at dymainstp.c:540 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fb4de0 TskhLoop + 0x4e20 at thxxhead.c:4518 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(20) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
SAPMSSY1
0
11.04.2005
09:27:15
22528
E
1
Prg
SAPLSCCA
1
05.07.2005
13:10:18
52224
E
2
Prg
SAPRFCSL
0
13.02.2005
17:31:45
17408
E
3
Typ
RFCSYSACL
0
13.02.2005
17:31:45
7168
4
Typ
SYST
0
09.09.2004
14:18:12
31744
Directory of Application Tables
Name Date Time Lngth
Val.
Program SAPMSSY1
SYST . . : : 00004612
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0\0
Program SAPRFCSL
RFCSYSACL . . : : 00001760
SOL RD3
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
116
CLEA
00
0035
SAPMSSY1
60
117
CLEA
00
0036
SAPMSSY1
60
118
CLEA
00
0037
SAPMSSY1
60
119
MESS
00
001C
SAPMSSY1
60
120
ENDF
00
0000
SAPMSSY1
62
121
00
0000
SAPMSSY1
62
122
PERP
00
0001
SAPMSSY1
64
123
PERP
02
0000
SAPMSSY1
64
124
WHIL
00
0002
0000
0000
0000
0000
0000
0000
SAPMSSY1
66
128
WHIL
00
0003
0000
0000
0000
0000
0000
0000
SAPMSSY1
66
132
BRAN
05
001E
SAPMSSY1
66
133
CALY
00
0003
0038
002A
0005
002B
0000
0000
SAPMSSY1
67
>>>>>
CALY
02
0000
0039
8000
0000
0000
0000
0000
SAPMSSY1
67
141
COMP
00
0002
0010
003A
SAPMSSY1
68
143
BRAF
02
000E
SAPMSSY1
68
144
SRFC
01
0000
003A
003B
SAPMSSY1
69
146
SRFC
01
0000
003C
C000
SAPMSSY1
69
148
SRFC
02
0000
0000
0000
SAPMSSY1
69
150
SRFC
01
0000
003A
003D
SAPMSSY1
81
152
SRFC
01
0000
003C
C000
SAPMSSY1
81
Thanks & Regards
Sudip -
Hi,
I am trying to set-up the Trusted RFC from my solman to the production server.
Both are on i400 series and same box.
I keep getting error RC=1, No authorizations to connect as trusted system.
I have checked under dev_rfc.trc
RFC I/O error- sys-error.
T 1286.
Checked all the notes regarding to these errors , kernel level is more than what is mentioned in the notes,ABAP and BASIS component are also fine.
The authorizations for the users on both the servers is given ,, both S_RFC and S_RFCACL.
There is a mention in help.sap.com to clean out the user buffer in SU56 if the problem persists(RC=1).
Is this recommended?? as its a production system.Hi Rene,
I am working on I400 series.
I have seen the entries in the table the message server is mentioned with the correct TCP port.
The authorizations are correct in both the systems.
The Service under STMS is not activated in the satellite system.
and let me know what was the addition to the services file..
I already have the message server mentioned.
wht else is needed??
the error in DEV_RFC is
error RFCIO_error_syserror in abrfcio_mt.c
And one doubt, do we need to have the entries in the services file just like the host file,, i mean ,, solman with entries of satellite and in satellite entries of solman ??
saw it in ur thread somewhere..
also SMT1 creation goes fine in both the systems, in SMT2 in the satellite system it says service "sapms??" unknown connection closed.. saw it in your thread also. the solution is the same include into services file, but i have done it already still not working..
And , the authority_check_trusted_system
How did you solve this ??
any help
Regards,
Kaustubh.
Edited by: kaustubh on Jun 10, 2008 9:28 PM
Edited by: kaustubh on Jun 10, 2008 9:36 PM
Maybe you are looking for
-
Hello, If I change the Wage types of It0014, directly in the mid of the month, the system does not pro-rate the part2 calculation based on the changed amount for that month. But in the next month onwards it takes the changed valule. At the same tim
-
Upgrading tables from OWB...
I am trying to upgrade a table in OWB using the deployment action of Upgrade. The old table exists in the target schema. When I try to upgrade it I get this error: RPE-01008: Recovery of this request is in progress. RTC-5351: A serious error occured
-
Joy of Print Servers; USB success
I administer a Netware 4.11+sp9 network, small by most standards. We also have Internet capability, using a commodity-quality Linksys router as a DHCP server, for most IP addresses. Our Netware server, however, runs IPX exclusively. I have read some
-
Can we use setInsets into JPanel?
can we use setInsets into JPanel? Advance wishes
-
Access to DLLs using Flash possible?
I have been researching the possiblity of passing parameters to a DLL from within a Flash project but have not had much luck. Does anyone know if this is beyond the capabilities of Flash or if it is in face doable? any help or suggestions would be gr