CALL_FUNCTION_ACCEPT_FAILED, SAPMSSY1, REMOTE_FUNCTION_CALL
Hi,
I am getting ST22 dump CALL_FUNCTION_ACCEPT_FAILED. Dump details are as under:
~
Runtime Errors CALL_FUNCTION_ACCEPT_FAILED
Date and Time 28.08.2007 17:50:38
ShrtText
Error when starting a Remote Function Call (ACCEPT).
What happened?
"CPIC-CALL: 'ThCMACCP'#Statistics not active "
An error occurred when executing a Remote Function Call.
Error analysis
An error occurred when executing a Remote Function Call.
"CPIC-CALL: 'ThCMACCP'#Statistics not active "
Status of connection.... "CODE=CM_DEALLOCATED_NORMAL CM_NO_STATUS_RECEIVED
CM_NO_DATA_RECEIVED SAPCODE=0 CONV=36058497"
Internal error code.... "RFC_IO5"
There is an error in the communication system. To clarify
and resolve the error, contact your system administrator.
Trigger Location of Runtime Error
Program SAPMSSY1
Include SAPMSSY1
Row 68
Module type (FORM)
Module Name REMOTE_FUNCTION_CALL
~
Line 68 is -> call 'RfcImport' id 'Type' field type.
~
DIA Work Process trace file have the following Entry:
A Tue Aug 28 17:50:38 2007
A
A ABAP Program SAPMSSY1 .
A Source SAPMSSY1 Line 68.
A Error Code CALL_FUNCTION_ACCEPT_FAILED.
A Module $Id: //bas/640_REL/src/krn/rfc/abrfcfun.c#21 $ SAP.
A Function ab_rfcimport Line 2687.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
A ** RABAX: end no http/smtp
A ** RABAX: end RX_GOTO_SAPDEXT
A Error when starting a Remote Function Call (ACCEPT)..
A
~
I have checked pinging targert server from SAP system and it is pinging fine.
I have checked the RFC Connection between my R/3 system and target system and it is working fine and test connection is ok.
~
I am not able to figure out where the issue is. Is any one know what could be the issue ?
Please reply urgently as this is an Emergency and business has been stopped due to this.
Any help will be Highly appreciated.
Thanks
Best Regards,
Basis.
Also see the intenal notes from ST22 dump:
~
Internal notes
The termination occurred in the function "ab_rfcimport" of the SAP
Basis System, specifically in line 2687 of the module
"//bas/640_REL/src/krn/rfc/abrfcfun.c#21".
The internal operation just processed is "CALY".
The internal session was started at 20070828180442.
Status of connection:
"IO HANDLE=1 DRV=INT LINE=2816 CODE=5 "
RFCIO_ERROR_SYSERROR.
Error elimination according to error code in communication system
(CPI-C return code, etc.).
Similar Messages
-
Category ABAP Programming Error
Runtime Errors TIME_OUT
ABAP Program SAPMSSY1
Application Component BC-MID-RFC
Date and Time 03.05.2014 09:04:14
|Short text |
| Time limit exceeded. |
|What happened? |
| The program "SAPMSSY1" has exceeded the maximum permitted runtime without |
| interruption and has therefore been terminated. |
| |
|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 |
| After a specific time, the program is terminated to make the work area |
| available to other users who may be waiting. |
| This is to prevent a work area being blocked unnecessarily long by, for |
| example: |
| - Endless loops (DO, WHILE, ...), |
| - Database accesses with a large result set |
| - Database accesses without a suitable index (full table scan) |
| |
| The maximum runtime of a program is limited by the system profile |
| parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this |
| time limit is |
| exceeded, the system attempts to cancel any running SQL statement or |
| signals the ABAP processor to stop the running program. Then the system |
| waits another 60 seconds maximum. If the program is then still active, |
| the work process is restarted. |
|How to correct the error |
| Programs with long runtime should generally be started as background |
| jobs. If this is not possible, you can increase the system profile |
| parameter "rdisp/max_wprun_time". |
| |
| Depending on the cause of the error, you may have to take one of the |
| following measures: |
| - Endless loop: Correct program; |
| - Dataset resulting from database access is too large: |
| Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table |
| (for example); |
| - Database has unsuitable index: Check index generation. |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "TIME_OUT" " " |
| "SAPMSSY1" or "SAPMSSY1" |
| "REMOTE_FUNCTION_CALL" |
| |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information: |
| |
| 1. The description of the current problem (short dump) |
| |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 2. Corresponding system log |
| |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |
| |Hi Bacon
Can you please check the user / transaction details which caused this error ? You will get that information in the dump itself.
Secondly is the dump occurring repeatedly.
From the dump details you have provided , it looks like there has been a RFC call in dialog mode which has exceeded runtime.
To resolve as a one time issue - also you have the possibility to increase the maximum run time parameter temporarily in the system
Thanks
Rishi -
CALL_FUNCTION_NOT_FOUND
Since January, some data missing in EWA report (e.g. performance data), and I found some short dump in ST22 with CALL_FUNCTION_NOT_FOUND. I found in source systems and those data capture successfully. How can I let the SolMan read those information back and generate EWA reports in normal?
Runtime Errors CALL_FUNCTION_NOT_FOUND
Occurred on 14.04.2008 at 02:22:43
Function module "SMY_GET_SDCC_INPUT" not found.
What happened?
The function module "SMY_GET_SDCC_INPUT" was called, but cannot be
found in the Function Library.
Error in ABAP application program.
The current ABAP program "SAPMSSY1 " had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
The program "SAPMSSY1 " contains a CALL FUNCTION statement. The name
of the function module to be called is "SMY_GET_SDCC_INPUT".
No function module exists with the name "SMY_GET_SDCC_INPUT".
All function modules are stored in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
to upper/lower case and underscores ("_")
b) Transport error
c) If an enqueue/dequeue module has been used, the lock object
may not have been activated (ABAP Dictionary)
may not have been activated (ABAP Dictionary).
How to correct the error
Check the last transports to the R/3 System.
Is the program "SAPMSSY1 " currently being changed?
If an enqueue/dequeue module is involved, is the activation
of the lock object missing in the ABAP/4 Dictionary?
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CALL_FUNCTION_NOT_FOUND" C
"SAPMSSY1 " or "SAPMSSY1 "
"REMOTE_FUNCTION_CALL"
Function modules with names similar to "SMY_GET_SDCC_INPUT":
SNC_GET_MY_INFO
SDU_SPECCAT_GET
SMSY_GET_SYSTEM_INFO
SMSY_GET_HOST
SCAN_INPUT
SDU_SPECCAT_PUT
SMAP_SC_INT_GET_CURSOR
SMSY_GET_CVERS_INFO
SWA_G_CONVERT_INPUT
SMSY_BPR_GET_SYSTEM_INFO
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "itcovssm"
Network address.......... "165.108.188.24"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "2x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "ITCOVSSM"
Database type............ "MSSQL"
Database name............ "SOL"
Database owner........... "dbo"
Character set............ "English_United State"
SAP kernel............... "620"
Created on............... "Feb 9 2004 21:59:19"
Created in............... "NT 5.0 2195 Service Pack 2 x86 MS VC++ 12.00"
Database version......... "SQL_Server_7.00 "
Patch level.............. "1340"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "620"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 000
User................ "SAPSYS"
Language key........ "E"
Transaction......... " "
Program............. "SAPMSSY1 "
Screen.............. "SAPMSSY1 3004"
Row of screen....... 2
Information about program making the Remote Function Call (RFC):
System.............. "BQ0"
Database Release.... 620
Kernel Release...... 640
Connection type: 3 (2 = R/2, 3 = R/3, E = External, R = Reg.external)
Call type: "S-" (S = Synchronous, a/A = Asynchronous, T = Transaction)
Client.............. 110
User................ "IA9901"
Transaction......... " (Program: /SDF/SAPLCCMS_DL)"
Function module..... "SMY_GET_SDCC_INPUT"
Call destination.... "SOL"
Source server....... "itcovsbq0_BQ0_00"
Source IP address... "165.108.188.37"
Additional RFC logon information:
Trusted Relation....." "
Logon return code...." "
Trusted return code.." "
Note: Prior to Release 4.0, there was less information available on RFC
calling programs.
Information on where termination occurred
The termination occurred in the ABAP program "SAPMSSY1 " in
"REMOTE_FUNCTION_CALL".
The main program was "SAPMSSY1 ".
The termination occurred in line 68 of the source code of the (Include)
program "SAPMSSY1 "
of the source code of program "SAPMSSY1 " (when calling the editor 680).
Source code extract
000380
000390 module %_rfcdia_call output.
000400 "Do not display screen !
000410 call 'DY_INVISIBLE_SCREEN'.
000420 perform remote_function_diacall.
000430 endmodule.
000440
000450 module %_cpic_start.
000460 if sy-xprog(4) = '%RFC'.
000470 perform remote_function_call using rfctype_external_cpic.
000480 else.
000490 call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
000500 perform cpic_call using convid.
000510 endif.
000520 endmodule.
000530
000540
000550 form cpic_call using convid type c.
000560 communication send id convid buffer header.
000570 if sy-subrc eq 0.
000580 perform (sy-xform) in program (sy-xprog).
000590 else.
000600 message a800.
000610 endif.
000620 endform.
000630
000640 form remote_function_call using value(type).
000650 do.
000660 * test if sy-xprog and sy-xform are set
000670 * sy-xform = 'quatsch'. sy-xprog = 'quatsch'.
> call 'RfcImport' id 'Type' field type.
000690 perform (sy-xform) in program (sy-xprog).
000700 rsyn >scont sysc 00011111 0.
000710 enddo.
000720 endform.
000730
000740 form remote_function_diastart.
000750 do.
000760 call 'RfcImport' id 'Type' field rfctype_rfcdia.
000770 perform (sy-xform) in program (sy-xprog).
000780 "Parking position for next request
000790 rsyn >scont sysc 00011111 10.
000800 "ALternativ : Free mode
000810 "COMMIT WORK.
000820 "SYSTEM-CALL FREE MODE 0.
000830 enddo.
000840 endform.
000850
000860 form remote_function_diacall.
000870 sy-xcode = '%_@no@'.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 1
SY-TABIX 0 SY-DBCNT 0
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
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
2 FORM REMOTE_FUNCTION_CALL
SAPMSSY1
SAPMSSY1 68
1 MODULE (PBO) %_RFC_START
SAPMSSY1
SAPMSSY1 30
Chosen variables
2 FORM REMOTE_FUNCTION_CALL
SAPMSSY1
SAPMSSY1 68
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
SY-REPID SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
SY-MSGID
22222222222222222222
00000000000000000000
CONVID
22222222
00000000
SPACE
2
0
SY-MSGNO 000
333
000
COUNT 0
0000
0000
SY-MSGV1
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV3
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV4
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
%_DUMMY$$
2222
0000
SYST-REPID SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
TYPE 3
0000
3000
SY-XPROG
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
SY-XFORM SMY_GET_SDCC_INPUT
545544555444544555222222222222
3D9F754F3433F9E054000000000000
%_SPACE
2
0
1 MODULE (PBO) %_RFC_START
SAPMSSY1
SAPMSSY1 30
TYPE 3
0000
3000
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "link_rfdir" of the SAP
Basis System, specifically in line 165 of the module
"//bas/620/src/krn/runt/ablink.c#5".
The internal operation just processed is "CALY".
The internal session was started at 20080414022243.
Active calls in SAP kernel
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=2432)
When : 4/14/2008 2:22:43.597
Threads : 2
Computer Name : ITCOVSSM
User Name : SAPServiceSOL
Number of Processors: 2
Processor Type: x86 Family 15 Model 2 Stepping 9
Windows Version : 5.0 Current Build: 2195
State Dump for Thread Id 97c
eax=7803a770 ebx=03245744 ecx=00000010 edx=00000000 esi=03245744 edi=03245718
eip=77f8850f esp=02ec74dc ebp=02ec7924 iopl=0 nv up ei pl nz ac pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000212
function : <nosymbols>
77f884ef c21000 ret 0x10
77f884f2 8bff mov edi,edi
77f884f4 b848000000 mov eax,0x48
77f884f9 8d542404 lea edx,[esp+0x4] ss:05d8df1b=00000000
77f884fd cd2e int 2e
77f884ff c22800 ret 0x28
77f88502 8bff mov edi,edi
77f88504 b849000000 mov eax,0x49
77f88509 8d542404 lea edx,[esp+0x4] ss:05d8df1b=00000000
77f8850d cd2e int 2e
77f8850f c20800 ret 0x8
77f88512 8bff mov edi,edi
77f88514 b84a000000 mov eax,0x4a
77f88519 8d542404 lea edx,[esp+0x4] ss:05d8df1b=00000000
77f8851d cd2e int 2e
77f8851f c20800 ret 0x8
77f88522 8bff mov edi,edi
77f88524 b84b000000 mov eax,0x4b
77f88529 8d542404 lea edx,[esp+0x4] ss:05d8df1b=00000000
77f8852d cd2e int 2e
77f8852f c21000 ret 0x10
77f88532 8bff mov edi,edi
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
02ec7924 00d9f2e5 03245718 02ec7954 03245718 02ec7948 ntdll!<nosymbols>
02ec79c4 004edcc9 004edc45 7803a770 7803a770 7803a770 disp+work!NTDebugProcess >
> [ntstcdbg.c (388)]
02ec79c8 004edc45 7803a770 7803a770 7803a770 0132f7c4 disp+work!NTStack >
> [dptstack.c (1453)]
02ec79e4 004edc0c 7803a770 00000000 00739ec5 7803a770 disp+work!CTrcStack2 >
> [dptstack.c (327)]
02ec79f0 00739ec5 7803a770 013b527c 30305f59 36313030 disp+work!CTrcStack >
> [dptstack.c (165)]
02ec7a0c 0073388d 00000000 00000001 00000012 01eed480 disp+work!ab_rt100 >
> [abrabax.c (6708)]
02ec7abc 00656e48 013b5294 013b527c 000000a5 013b5210 disp+work!ab_rabax >
> [abrabax.c (952)]
02ec7af4 00656d7b 01a1b44c 00000012 02ec7b18 00000000 disp+work!ab_link >
> [ablink.c (165)]
02ec7b84 007b2c9d 00000001 01a1b44c 00000192 0000185f disp+work!ab_link >
> [ablink.c (358)]
02ec802c 0072993a 02ece67c 02ece688 000000cd 00000000 disp+work!ab_rfcimport >
> [abrfcfun.c (2802)]
02ec8044 0064a967 00000003 50a56c28 00000000 07d97760 disp+work!ab_jcaly >
> [abcall.c (99)]
02ece680 0064a246 00000000 006b3012 00000000 50a56c28 disp+work!ab_extri >
> [abextri.c (389)]
00000000 00000000 00000000 00000000 00000000 00000000 disp+work!ab_extri >
> [abextri.c (201)]
State Dump for Thread Id a94
eax=78008532 ebx=00000103 ecx=7c57b740 edx=00000000 esi=00000000 edi=00000000
eip=77f884ff esp=0531fe70 ebp=0531feb0 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function : <nosymbols>
77f884df c20c00 ret 0xc
77f884e2 8bff mov edi,edi
77f884e4 b847000000 mov eax,0x47
77f884e9 8d542404 lea edx,[esp+0x4] ss:081e68af=????????
77f884ed cd2e int 2e
77f884ef c21000 ret 0x10
77f884f2 8bff mov edi,edi
77f884f4 b848000000 mov eax,0x48
77f884f9 8d542404 lea edx,[esp+0x4] ss:081e68af=????????
77f884fd cd2e int 2e
77f884ff c22800 ret 0x28
77f88502 8bff mov edi,edi
77f88504 b849000000 mov eax,0x49
77f88509 8d542404 lea edx,[esp+0x4] ss:081e68af=????????
77f8850d cd2e int 2e
77f8850f c20800 ret 0x8
77f88512 8bff mov edi,edi
77f88514 b84a000000 mov eax,0x4a
77f88519 8d542404 lea edx,[esp+0x4] ss:081e68af=????????
77f8851d cd2e int 2e
77f8851f c20800 ret 0x8
77f88522 8bff mov edi,edi
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0531feb0 00e457a7 0000025c 00000000 00000028 04a3fdc8 ntdll!<nosymbols>
0531ff7c 780085bc 00000000 00000028 00000000 04a3fdc8 disp+work!SigILastSig >
> [signt.c (540)]
0531ffb4 7c57b3bc 04a3fdc8 00000028 00000000 04a3fdc8 MSVCRT!<nosymbols>
0531ffec 00000000 00000000 00000000 00000000 00000000 KERNEL32!<nosymbols>
List of ABAP programs affected
| Type| Program | Gen. Date Time | Load Size |
| Prg | SAPMSSY1 | 31.01.2002 17:21:09 | 18432 |
| Typ | SYST | 01.02.2001 17:25:48 | 24576 |
List of internal tables
No dump information available
Directory of Application Tables
Program
Name................ Contents....1........2........3........4........5....+....
SAPMSSY1
SYST |\x01\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
Directory of Application Tables (Administrative Information)
Program
Name.......................... Time.......... Length...
SAPMSSY1
SYST 00002404
ABAP control blocks CONT
Include Line source code
Index Name F1 Co Par01 Par2. Par3. Par4. Tabl
SAPMSSY1 60 message a800.
210 CLEA 00 54
211 CLEA 00 55
212 MESS 00 28
SAPMSSY1 62 endform.
213 ENDF 00
214 -
218 -
SAPMSSY1 64 form remote_function_call usin
222 PERP 00 1
223 PERP 02
SAPMSSY1 65 do.
224 WHIL 00 2
228 WHIL 00 3
232 BRAN 05 Branch to 246
SAPMSSY1 68 call 'RfcImport' id 'Type' fie
233 CALY 00 3 56 42 5 5
>>>>> CALY 02 57 P0
SAPMSSY1 69 perform (sy-xform) in program
241 xper 02 16 17
243 PERP 80
SAPMSSY1 70 rsyn >scont sysc 00011111 0.
244 SYSC 1F
SAPMSSY1 71 enddo.
245 BRAX 00 Branch to 228
246 WHIL 00 4
SAPMSSY1 72 endform.
250 ENDF 00
251 -
End of runtime analysisRefer to Note 98458 - SAPMSSY1, CALL_FUNCTION_NOT_FOUND
-
Finding caller program in a RFC call
Hi experts,
We are having lots of CALL_FUNCTION_NOT_FOUND short dumps in one of our systems. The errors are caused because other systems call a function that does not exist, so the dumps are created.
What we would like to know is what program is doing these calls, since all we can see in the short dump is the caller system and the function it is trying to access, but not the exact program where the call is performed so we can fix the code.
Thanks in advance for your support.Sorry if this is too much of a wall of text, I can't find an "attach file" type feature.
ABAP runtime errors CALL_FUNCTION_NOT_FOUND
Occurred on 11.12.2006 at 10:04:34
Function module "Y_EF_DETERMINE_PICTURE" not found.
What happened?
The function module "Y_EF_DETERMINE_PICTURE" was called, but cannot be
found in the Function Library.
The current ABAP/4 program "SAPMSSY1 " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
The program "SAPMSSY1 " contains a CALL FUNCTION statement. The name
of the function module to be called is "Y_EF_DETERMINE_PICTURE".
No function module exists with the name "Y_EF_DETERMINE_PICTURE".
All function modules are stored in the Function Builder (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
to upper/lower case and underscores ("_").
or
b) Transport error
c) In the case of an enqueue/dequeue module, the lock object
may not have been activated (ABAP Dictionary).
How to correct the error
Check the last transports to the R/3 System.
Is the program "SAPMSSY1 " currently being changed?
If an enqueue/dequeue module is involved, is the activation
of the lock object missing in the ABAP/4 Dictionary?
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"CALL_FUNCTION_NOT_FOUND"
"SAPMSSY1 " or "SAPMSSY1 "
"REMOTE_FUNCTION_CALL"
Function modules with names similar to "Y_EF_DETERMINE_PICTURE":
Y_EF_USEX_DETERMINE_TAX
Y_GF1_DETERMINE_RECTYPE
Y_GK_DETERMINE_PRCTR
Y_EF_USEX_PICTURE_SUBMIT
Y_EF_USEX_SHOW_PICTURE
Y_EF_RFC_PICTURE_POST
Y_GF1_DETERMINE_SBU
Y_GF_DETERMINE_VERSION
Y_GF_DETERMINE_DATE_PREVMON
Y_GF1_DETERMINE_CURRENT_PERIOD
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "46C"
Application server....... "sapgp1s"
Network address.......... "52.99.71.21"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C4449E4C00"
Database server.......... "sapgp1s"
Database type............ "DB6"
Database name............ "GP1"
Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "46D"
Created on............... "Aug 26 2005 22:40:31"
Created in............... "AIX 1 5 0056AA8A4C00"
Database version......... "DB6_71 "
Patch level.............. "2113"
Patch text............... " "
Supported environment....
Database................. "DB6 06., DB6 07., DB6 08.*"
SAP database version..... "46D"
Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3
5, , System build information:, -
, LCHN :
User, transaction...
Client.............. 000
User................ "SAPSYS"
Language............ "E"
Transaction......... " "
Program. ........... "SAPMSSY1 "
Screen. ............ "SAPMSSY1 3004"
Line of screen...... 2
Information about Remote Function Call (RFC) Caller:
System.............. "WP1 "
Database release.... "46C "
Kernel release. .... "46D "
Connection type. ... "3 " (2 = R/2, 3 = R/3, E = Extern, R = Reg.
Call type........... "S-" (S = synch., a/A = asynch., T = transactional
Client.............. 510
User................ "PC1706 "
Transaction......... "/COCKPIT/1 "
Function module..... "Y_EF_DETERMINE_PICTURE"
Call destination.... "GP1590"
Source server....... "wsdux44_WP1_10"
Source IP address... "52.99.71.124"
Additional information about RFC logon:
Trusted relationship " "
Logon return code... " "
Trusted return code. " "
Note: In Releases earlier than 4.0, some of the above information about
RFC calls may not be available.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPMSSY1 " in
"REMOTE_FUNCTION_CALL".
The main program was "SAPMSSY1 ".
The termination occurred in line 67
of the source code of program "SAPMSSY1 " (when calling the editor 670).
Source code extract
000370 ENDMODULE.
000380
000390 MODULE %_RFCDIA_CALL OUTPUT.
000400 "Do not display screen !
000410 CALL 'DY_INVISIBLE_SCREEN'.
000420 PERFORM REMOTE_FUNCTION_DIACALL.
000430 ENDMODULE.
000440
000450 MODULE %_CPIC_START.
000460 IF SY-XPROG(4) = '%RFC'.
000470 PERFORM REMOTE_FUNCTION_CALL USING RFCTYPE_EXTERNAL_CPIC.
000480 ELSE.
000490 CALL 'APPC_HD' ID 'HEADER' FIELD HEADER ID 'CONVID' FIELD CONVID.
000500 PERFORM CPIC_CALL USING CONVID.
000510 ENDIF.
000520 ENDMODULE.
000530
000540
000550 FORM CPIC_CALL USING CONVID.
000560 COMMUNICATION SEND ID CONVID BUFFER HEADER.
000570 IF SY-SUBRC EQ 0.
000580 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000590 ELSE.
000600 MESSAGE A800.
000610 ENDIF.
000620 ENDFORM.
000630
000640
000650 FORM REMOTE_FUNCTION_CALL USING VALUE(TYPE).
000660 DO.
CALL 'RfcImport' ID 'Type' FIELD TYPE.
000680 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000690 RSYN >SCONT SYSC 00011111 0.
000700 ENDDO.
000710 ENDFORM.
000720
000730 FORM REMOTE_FUNCTION_DIASTART.
000740 DO.
000750 CALL 'RfcImport' ID 'Type' FIELD RFCTYPE_RFCDIA.
000760 PERFORM (SY-XFORM) IN PROGRAM (SY-XPROG).
000770 "Parking position for next request
000780 RSYN >SCONT SYSC 00011111 10.
000790 "ALternativ : Free mode
000800 "COMMIT WORK.
000810 "SYSTEM-CALL FREE MODE 0.
000820 ENDDO.
000830 ENDFORM.
000840
000850 FORM REMOTE_FUNCTION_DIACALL.
000860 SY-XCODE = '%_@no@'.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 1
SY-TABIX 0 SY-DBCNT 0
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+....4
SY-XPROG
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
SY-XFORM Y_EF_DETERMINE_PICTURE
554454454544445544555422222222
9F56F45452D9E5F093452500000000
%_SPACE
0
0
SY-MSGID
22222222222222222222
00000000000000000000
EBC_TO_ASC-X05 P&QéRêSëTèUíVîWïXìY~ZÜ[$*])^;_^
525E5E5E5E5E5E5E5E575D5252525355
06192A3B485D6E7F8C9EACB4CAD9EBFE
RFCTYPE_QUEUE 6
0000
0006
%_PRINT 000
2222333222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 0 ########
2222222222320000000022222222222222222222
0000000000000000000000000000000000000000
... + 120
22222222
0000000
SY-MSGNO 000
333
000
EBC_TO_ASC-X04 @ A BâC{DàEáFãGåHçIñJÄK.L<M(N+O!
424A4E474E4E4E4E4E4F4C4243424242
0010223B405163758791A4BECCD8EBF1
SY-MSGV1
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV3
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV4
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
%_?NOT_ASSIGNED?
2222
0000
SPACE
2
0
SY-REPID SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
TYPE 3
0000
0003
SYST ########################################
0000000000000000000000000000000000000000
0001000000000000000000000000000000000000
... + 40 ########################################
0000000000000000000000000000000000000000
0000000000010000000100000000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 120 #######################################T
00000000
0000000
Active calls / events
No.... Type........ Name..........................
Programm
Include Line
1 FORM REMOTE_FUNCTION_CALL
SAPMSSY1
SAPMSSY1 67
2 MODULE (PBO) %_RFC_START
SAPMSSY1
SAPMSSY1 31
Internal notes
The termination occurred in the function "link_rfdir" of the SAP
Basis System, specifically in line 165 of the module
"//bas/46D/src/krn/runt/ablink.c#3".
The internal operation just processed is "CALY".
The internal session was started at 20061211100434.
Active calls in SAP kernel
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = unlimited
=> Core limit = 51200000
=> File size limit = unlimited
=> Heap address = 0x118dba360
=> Stack address = 0xfffffffffff5d50
=> Stack low = 0xfffffffffff5d50
=> Stack high = 0xffffffffffff600
=> Stack Trace:
AixStack() at 0x100059364
CTrcStack2() at 0x10005945c
rabax_CStackSave() at 0x10003959c
ab_rabax() at 0x1000425b4
link_rfdir() at 0x100540418
ab_link() at 0x100540a18
ab_rfcimport() at 0x1005f49f0
ab_jcaly() at 0x100024560
ab_extri() at 0x100487474
ab_xevent() at 0x10059c804
ab_dstep() at 0x10043bd98
dynpmcal() at 0x100942f94
dynppbo0() at 0x100941320
dynprctl() at 0x100948f40
dynpen00() at 0x1008f7818
Thdynpen00() at 0x1001429f4
TskhLoop() at 0x100146368
tskhstart() at 0x1001576ac
DpMain() at 0x100e06e38
main() at 0x100de72f4
List of ABAP programs affected
Type
Program
Gen. date time
LoadSize
Prg
SAPMSSY1
04.01.2000 19:06:59
20480
List of internal tables
No dump information available
Directory of application tables (contents)
Program
Name.......... Contents.1........2........3....+....
Directory of data areas (administration information)
Program
No.. Name.......... Lgth Ofsg Type Next Gen date Gen time
SYST
L not assigned -15 0 IN
M /%_LISTTABLE -14 1 CO 0
T global stack -13 1 2 GL 0
SAPMSSY1
A global data 0 3 DA
L constant dat 1 4 LI .0 .0216
L constant dat 2 5 LI SSY .0 .018B
L not assigned 3 6 IN
L SYST 4 7 TA 0
L SY 5 8 TA
L RSJOBINFO 6 9 TA
M /%_SYS%% 7 0 CO
M field symbol 8 1 FS
L TCPIC 9 2 TA
M field symbol 10 3 FS
L text pool 11 4 TP
Directory of data areas (contents)
Program
No.. Name.......... Contents..1........2........3....+....
SYST
L not assigned 0
L text pool 102 |SAPMSSY1
ABAP control blocks CONT
Include Line source code
Index Name F1 Co Par01 Par2. Par3. Par4. Tabl
SAPMSSY1 60 MESSAGE A800.
215 CLEA 00 84
216 CLEA 00 85
217 MESS 00 27
SAPMSSY1 62 ENDFORM.
218 ENDF 00
219 -
223 -
SAPMSSY1 65 FORM REMOTE_FUNCTION_CALL USIN
227 PERP 00 1
228 PERP 02
SAPMSSY1 66 DO.
229 WHIL 00 2
233 WHIL 00 3
237 BRAN 05 Branch to 251
SAPMSSY1 67 CALL 'RfcImport' ID 'Type' FIE
238 CALY 00 3 86 70 71 71
>>>>> CALY 02 87 P0
SAPMSSY1 68 PERFORM (SY-XFORM) IN PROGRAM
246 xper 02 12 13
248 PERP 80
SAPMSSY1 69 RSYN >SCONT SYSC 00011111 0.
249 SYSC 1F
SAPMSSY1 70 ENDDO.
250 BRAX 00 Branch to 233
251 WHIL 00 4
SAPMSSY1 71 ENDFORM.
255 ENDF 00
256 -
End of runtime analysis -
Process Chain Stopped in BI PRD
Data Loading Error :
Hi All,
In BI PRoduction, all the process Chains are stopped and while Checking the errors, it is giving the error message as
Errors while sending packages from OLTP to BI
Diagnosis
No IDocs could be sent to BI using RFC.
System Response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further analysis:
Check the TRFC log.
You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Error handling:
If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.
Morning, I have logged into BW Production, and saying BW Production is down. This is happening frequently.By the help of basis, the system is up.
Please help on this issue.
Thanks,
Jelina.Thanks for the reply.
I have Checked in ST22 and found, Time Out error is there.
These are the error messages in ST22.
The program "SAPMSSY1" has exceeded the maximum permitted runtime without interruption and has therefore been terminated.
Error Analysis :
After a specific time, the program is terminated to make the work area available to other users who may be waiting.
This is to prevent a work area being blocked unnecessarily long by, for
example:
- Endless loops (DO, WHILE, ...),
- Database accesses with a large result set
- Database accesses without a suitable index (full table scan)
The maximum runtime of a program is limited by the system profile
parameter "rdisp/max_wprun_time". The current setting is 3600 seconds. If this time limit is exceeded, the system attempts to cancel any running SQL statement or signals the ABAP processor to stop the running program. Then the system waits another 60 seconds maximum. If the program is then still active,the work process is restarted.
How to correct the Error :
Programs with long runtime should generally be started as background jobs. If this is not possible, you can increase the system profile parameter "rdisp/max_wprun_time".
Depending on the cause of the error, you may have to take one of the following measures:
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
(for example);
- Database has unsuitable index: Check index generation.
If the error occures in a non-modified SAP program, you may be able to find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following keywords:
"TIME_OUT" " "
"SAPMSSY1" or "SAPMSSY1"
"REMOTE_FUNCTION_CALL"
If you cannot solve the problem yourself and want to send an error notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP program: The source code of the program
In the editor, choose "Utilities->More Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Thanks,
Ram
Edited by: Ram Siva on Jul 28, 2009 6:59 AM -
Abap Error CALL_FUNCTION_WAIT_ERROR in program SAPMSSY1
I am getting abap error " CALL_FUNCTION_WAIT_ERROR ".
The termination occurred in the ABAP/4 program "SAPMSSY1 " in
"REMOTE_FUNCTION_CALL".
The main program was "SAPMSSY1 ".
The termination occurred in line 69
of the source code of program "SAPMSSY1 " (when calling the editor 690).
Regards,
ArundhatiHello,
If CALL_FUNCTION_WAIT_ERROR occurs only at the server side for
Remote Function Call (RFC) communication when the server gets
the message that the client side is not reachable any more.
This can happen if there exists an communication interruption (CPIC /
TCP/IP network problems) or a client is not any more active.
Therefore please check the gateway, workprocess and rfc traces
(dev_rd, dev_w* and dev_rfc*) and SM21 for possible problems. Could
you find the origin of the rfc connection? Is it an external RFC
program? Then you may need to install the most recent rfc library
on external side according to SAP notes:
413708 RFC library current at present
27517 Installation RFCSDK
Regards,
David -
Hi Friends ,
I am getting following dump .
CALL_FUNCTION_NOT_FOUND
"Check the last transports to the SAP System.
Is the program "SAPMSSY1" currently being changed?
If an enqueue/dequeue module is involved, is the activation
of the lock object missing in the ABAP/4 Dictionary?"
call 'RfcImport' id 'Type' field type.
if sy-xprog = 'JAVA'.
system-call plugin
id 'JAVA' value 'FORW_JAVA'
id 'RC' value rc.
i m working on this.But didnot get any clue.
please let me know if you can help on this.
regards,
kaniI would try to set a break-point to find more information
form remote_function_call using value(type).
data rc type i value 0.
do.
call 'RfcImport' id 'Type' field type.
if sy-xprog = 'JAVA'.
system-call plugin
id 'JAVA' value 'FORW_JAVA'
id 'RC' value rc.
* if there is no rollout on the JAVA side which
* rolls both, JAVA and ABAP, we return to the
* C-Stack and reach this point
* in case there was an rollout, the ABAP-C stack is lost
* and we jump direkt to this point
* here we trigger the rollout on this Abap side with
* the following statement
system-call plugin
id 'JAVA' value 'ROLL_OUT'
id 'RC' value rc.
else.
perform (sy-xform) in program (sy-xprog).
rsyn >scont sysc 00011111 0.
endif.
enddo.
endform. -
Error while executing query on portal-SAPMSSY1 method : UNCAUGHT_EXCEPTION
Hello all,
I have created a quey and executed it on portal and everything just works fine. The query has few input varaibles at the start like fiscal year and some other inputs. I saved the query in my Portal favorites and then when I try to excute it from there it gives me a runtime BI error.
Termination message sent ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION MSGV1: SAPMSSY1 MSGV3: UNCAUGHT_EXCEPTION
I guess it errors out because of the variable input part at the start of query.
We already have note "950992" in the system so wonder what next now.
Any inputs appreciated.
Thanks,
KiranWe are having the same issue too - we are SP13. Our query is built on a Infoset, and the problem comes with 0FISCPER variable, when we try to do a input help (F4) in Bex. this happens only when I use fiscper on queries bulit on INFOSETS, and it works perfectly alright with all other cubes.
<i>System error in program CL_RSMD_RS_SPECIAL and form
IF_RSMD_RS~READ_META_DATA-02 (see long text)
Message no. BRAIN299
Diagnosis
This internal error is an intended termination resulting from a program
state that is not permitted.
Procedure
Analyze the situation and inform SAP.
If the termination occurred when you executed a query or Web template,
or during interaction in the planning modeler, and if you can reproduce
this termination, record a trace (transaction RSTT).</i>
For more information about recording a trace, see the documentation for
the trace tool environment as well as SAP Note 899572.
and in portal, it gets to the point of variable screen and then throws a error msg.
<i>ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION</i>
Message was edited by:
voodi
Message was edited by:
voodi -
Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION in Report
Hi All,
This is the frequent problem we are facing in BW production.
While executing the BW reports
We are getting the below error.
No Space left in Shared memory.
Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION in Report.
An exception with the type CX_SY_EXPORT_NO_SHARED_MEMORY occurred, but was neither handled locally, nor declared in a RAISING
Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
System error in program SAPLRRK0 and form INITIALIZE_DATA_ACCESS-01
The problem solved when we restarted the server.
but this is coming very frequent.
Is there any permanent soln for this one.
Pls advice.
Thanks!
SanjayHi,
Check the below notes,
Note 656060 - OLAP: Cache main memory displacement not functioning
Note 1114164 - Termination in the cache due to insufficient shared memory
Apply note 1114164 and check if issue resolves or not.
Regards,
Niraj -
Program error in class sapmssy1 method : uncaught_exception
Hi Friends,
I am executing Balance sheet report in portal while displaying the out put I am getting the below error message
u201CError Brain (068): Characteristic value 18 of characteristic 0GL_ACCOUNT is not ALPHA-converted
Program error in class sapmssy1 method : uncaught_exception u201C
Can you please provide the solution on this?
Thanks
srini Rthis sounds like an R/3 data quality issue...if the alpha conversion routine is not put in the infoobject maintenance you need to put the alpha conversion hardcoded in the start routine. then reload everything...
M. -
Program error in class SAPMSSY1 Method When Filtering on Source System ID
Whenever I try to filter my Source System ID in the BEx Query Designer (BI 7.0), I get the error:
Reading Characteristic Values
Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION.
And I cannot filter my Source System ID.
Does anybody know how to resolve this?Hi,
Check the below notes,
Note 656060 - OLAP: Cache main memory displacement not functioning
Note 1114164 - Termination in the cache due to insufficient shared memory
Apply note 1114164 and check if issue resolves or not.
Regards,
Niraj -
ABEND RSBOLAP (000): error in class SAPMSSY1 method - after report move Pro
Hi Guys,
We recently moved a report to production and got the following error (500 Internal Error) when executing from Query designer
ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION
I saw in one of the threads to run the Program RSPOR_SETUP and see if all the 12 steps are ok and they are not but they are not ok in Dev and Qua as well where its running fine. Appreciate if somebody can advise.Hi,
Check your Query in RSRT properties tab and make necessary settings.
Do OLAP check in RSCRM_BAPI t-code. It will show the inconsistencies in your query.......
Regards,
Suman -
Hello,
A BI Report contains a field "X" & a field "Y".
Y is a sub part of X. Means on clicking upon X, Y opens.
This report runs on date basis. For each date Y contains Zero value, but in the result Y contains some value greater than zero.
Now when i execute this report in Portal, clicking on X for the dates opens up Y.
But in the result column, Clicking on X giveg the following error:
Root Cause
The initial exception that caused the request to fail was:
Termination message sent
ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
MSGV1: SAPMSSY1
MSGV3: UNCAUGHT_EXCEPTION
Pl. note that this report is running fine in BEx analyer & not giving any such error.
Thanks & RegardsIn SE 38 run RSPOR_SETUP and see if all the 12 steps are ok, as I see this is a an issue with java server not able to commute with BI., you need to exchange java certificates to BI and vise versa.,(basis can do this step)
Hope this helps., -
Program error in class SAPMSSY1 method
We are on 2004s SP10. I can create queries fine, but can not save them. I created a bex default transport. When I check the query it says it is fine. The error I am getting is "Error in Class SAPMSSY1 Method". I also get an error referencing a 26 or so bit program saying it does not exist. I have not found any threads which from out SP level that match these errors. Any idea? Thanks Steve
This is an issue with Fiscal Year Variant Variable in the query. (Or at least that was our team's issue). To solve this, you have to rebuild the qurey from scratch. Attempting to edit the existing query will NOT fix the issue. Trying to fix it, creates a loop were it again looks for fiscal year variant variable then produces the error.
I solved this be rebuilding the query and adding 0FISCVAR last. Then in the filter, I chose K4 instead of a variable or SAP exit. (sorry if you requirement needs a variable, i would suggest creating a new one of those too). Then save and you should have a working query.
Yes when you check it appears fine, but in the background it is not. When you save the "correct" query, the system looks for the old 0FISCVAR variable and fails to save. -
SAP Installation RFC LOGON FAILED- SQl ERROR ON PROGRAM SPAM (SAPMSSY1)
Dear Gurus,
during the SAP installation, i got the RFC logon failed error: SQL Error on program SPAM (SAPMSSY1)
I am pasting the disp_w0 file.....................
http://www.4shared.com/file/89058633/ac7a0547/_2__dev_w0.html
pls let me know the how to lovve this.
the basic error is like....
Generating ABAP/4 Program SAPMS380 .
A Source SAPMS380 Line 8.
A Error Code GEN_SOURCE_FORMAT.
A Module $Id: //bas/620/src/krn/gen/screads.c#7 $ SAP.
A Function sc_getstring Line 624.
A Error when reading program SAPMS380
Its showing this kinda error for a max of program like SAPMSSY1, SAPMSSY2, SAPMS380 and lots more which are clearly depicted in disp_w0 file.
what is the error??? is there any error in program SAPMSSY1??
if this is true pls let me know hot to solve this? where i can access this SAPMSSY1 ?? remember i can not use any T-code like SE36 as my installation is not finished.
Kindly have a detail look on the disp_w0 file.
AbhishekHI
can u tell me how 2 acces the ABAP program like SAPMSSY1 etc. without entering into SAP by T-code.
as i can not login right now. i want to do certain changes in these programs.
Abhishek
Maybe you are looking for
-
Creating a Purchase Order for the Asset
Hi, Please see the following steps: 1.Create a purchase order for the asset. 2. Post a goods receipt from this PO. 3. Quantity of asset will be transfered from goods receipt. But I find quantity of asset(AS02) was not be transfered and still was equa
-
ITunes Match weird glitches on my iPhone 5
Hello Community. I'm having a weird problem with iTunes Match, pmart playlists, and songs downloaded to my iPhone. I have used smart playlist on both my Mac and iPhone for as long as I can remember and havent incountered any significant issues until
-
2 months and still no broadband
So on March 31st I rang to do a homemove, as I had infinity and my new home doesn't (even though it's nearer to the exchange and there's a fibre cab a 100 yards down the road but ours isn't in the rollout plan for some daft reason) They said they had
-
Does the number of photos stored on the Ipod touch affect the quality of photos
My IPod touch had started out taking great photos, but over time I ended up storing well over 500 photos on it. Recently I noticed that my new photos are of very poor quality (fuzzy) could this be due to the volume of photos stored. I can easily dele
-
Regular expression in oracle for hypen
Hi, I want to match a word "{color:#993300}83-ASG{color}" using regexp_like and i used '{color:#993300}^83-*{color}' pattern to match this word but this also matches words like "{color:#993300}8307-YUF{color}". could anyone please tell me what patter