on 09-17-2011 8:35 AM
Hi Expert ,
while finished the SM:SELFDIAGNOSIS this job in Solution manager system so in that moment i'm getting a CALL_FUNCTION_SYSCALL_ONLY dump in quality server.
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
Date and Time 25.08.2011 01:43:31
Short text
You are not authorized to logon to the target system (error code 0).
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSYST" 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
RFC calls (Remote Function Calls) were sent with the invalid user
ID "DDIC ". The receiving system regarded the first call as a system
call and therefore accepted it without a valid user ID.
However, the last call was to an external function module and
was thus rejected.
The action was carried out by caller "DDIC " with client 100 from within
system "SOL " and transaction " ".
How to correct the error
In the trusted relation, a logon failure can be caused either by the
fact that the entered security key for system "SOL " is invalid or that the
trusted system data has lost its validity due to a timeout.
The error code of the trusted system was 2.
Meaning:
0 Correct logon as trusted system mode
1 No trusted system entry for the caller system "SOL " or the
security key entry for system "SOL " is invalid
2 User "DDIC " has no RFC authorization (authorization object
S_RFCACL) for caller "DDIC " with client 100.
3 The timestamp of the logon data is invalid
The error code of the SAP logon procedure was 0.
Meaning:
0 Logon was correct
1 Wrong password or invalid user ID
2 User is locked
3 Too many logon attempts
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
5 Error in authorization buffer (internal error)
6 No external user check
7 Invalid user type
8 Validity period of user exceeded
System environment
SAP-Release 701
Application server... "QAserver"
Network address...... "192.168.1.6"
Operating system..... "AIX"
Release.............. "6.1"
Hardware type........ "000A154AD400"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "QAserver"
Database type..... "DB6"
Database name..... "QAS"
Database user ID.. "SAPQAS"
Terminal.......... " "
Char.set.... "C"
SAP kernel....... 701
created (date)... "Sep 23 2010 21:55:35"
create on........ "AIX 2 5 00CB5A5B4C00"
Database version. "DB6_81 "
Patch level. 111
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 701
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6, AIX 1 7"
Memory consumption
Roll.... 16192
EM...... 4189848
Heap.... 0
Page.... 0
MM Used. 1226088
MM Free. 2961160
User and Transaction
Client.............. 000
User................ "SAPSYS"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "858DCEE0F1E5F1B3AAFCE61F137E15A3"
Program............. "SAPLSYST"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
Information on caller of Remote Function Call (RFC):
System.............. "SOL"
Database Release.... 701
Kernel Release...... 701
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.............. 100
User................ "DDIC"
Transaction......... " "
Call Program........."CL_DSMOP_RFC_WATCHER==========CP"
Function Module..... "RFCPING"
Call Destination.... "SM_QASCLNT100_TRUSTED"
Source Server....... "solid_SOL_01"
Source IP Address... "192.168.1.2"
Additional information on RFC logon:
Trusted Relationship "X"
Logon Return Code... 0
Trusted Return Code. 2
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 "SAPLSYST" - in "TABLE_COMPRESS".
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
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
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 2
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 20110825
SY-UZEIT 014330
SY-XPROG SAPLSYST
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
SY-XFORM RFCPING
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
SAPLSYST
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555522222222222222222222222222222222
310C393400000000000000000000000000000000
%_ARCHIVE
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
RC
0
0000
0000
SY-XFORM
RFCPING
000000000000000000000000000000
000000000000000000000000000000
544544422222222222222222222222
26309E700000000000000000000000
%_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 "PrepareSignOnRabax"
of the SAP kernel, in line 5385 of the module
"//bas/701_REL/src/krn/rfc/abrfcfun.c#13".
The internal operation just processed is "CALY".
Internal mode was started at 20110825014330.
The called function module was "RFCPING ".
Caller system......: "SOL "
Caller.............: "DDIC "
Caller client......: 100
RFC user ID........: "DDIC "
RFC client.........: 100
Transaction code...: " "
Logon return code..: 0
Trusted return code: 2
Note: For releases < 4.0, information on the caller may not exist
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = 4294967296
=> Core limit = 1073741312
=> File size limit = unlimited
Runtime Errors CALL_FUNCTION_SYSCALL_ONLY
D ate and Time 25.08.2011 01:43:31
=> Heap address = 0x0x11cd64d20
=> Stack address = 0xfffffffffff4850
=> Stack low = 0xfffffffffff4850
=> Stack high = 0xffffffffffff810
=> Stack Trace:
AixStack() at 0x10007fd28
CTrcStack2() at 0x10007fe20
rabax_CStackSave__Fv() at 0x100068b10
ab_rabax() at 0x1000650a4
PrepareSignOnRabax() at 0x100e3beb0
ab_rfcimport() at 0x100e3a7e4
ab_jcaly__Fv() at 0x10005aeb8
ab_extri__Fv() at 0x10052701c
ab_xevent__FPCUs() at 0x100a31b84
ab_dstep() at 0x100805368
dynpmcal() at 0x100d7f2b4
dynppbo0() at 0x100d7cdf8
dynprctl() at 0x100d84bc4
dynpen00() at 0x100d786a8
Thdynpen00() at 0x10009b01c
TskhLoop() at 0x10009ffa8
ThStart() at 0x1000b7dd0
DpMain() at 0x1015518ec
nlsui_main() at 0x101a4b620
List of ABAP programs affected
Index Typ Program Group Date Time Size Lang.
0 Prg SAPMSSY1 0 11.04.2005 09:27:15 21504 E
1 Prg SAPLSRFC 1 17.12.2008 07:36:53 43008 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 Prg SAPLSYST 4 29.11.2010 01:19:16 35840 E
5 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 QAS
Please assist me asap.
Regards
Shubh
Edited by: Shiv ji Mishra on Sep 17, 2011 9:38 AM
Hello,
It seems some trusted RFC issue. Check the RFCs, somewhere it might be possible that the DDIC user is being used and it doesn't have proper RFC authorization. Try to use some different user.
See the extract from the dump
The action was carried out by caller "DDIC " with client 100 from within system "SOL " and transaction " ". How to correct the error In the trusted relation, a logon failure can be caused either by the fact that the entered security key for system "SOL " is invalid or that the trusted system data has lost its validity due to a timeout. The error code of the trusted system was 2. Meaning: 0 Correct logon as trusted system mode 1 No trusted system entry for the caller system "SOL " or the security key entry for system "SOL " is invalid 2 User "DDIC " has no RFC authorization (authorization object S_RFCACL) for caller "DDIC " with client 100
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The user DDIC which is using the RFC "SM_QASCLNT100_TRUSTED" though job selfdignostic is not either difinened in Satelite system of the password is not correct. check it, your problem should be sorted out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
72 | |
26 | |
10 | |
9 | |
7 | |
6 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.