cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime Errors MESSAGE_TYPE_X

Former Member
0 Kudos

I have the following error when i try to create a table-join in SQVI. Could you help how i can overcome this problem

Short text

The current application triggered a termination with a short dump.

What happened?


The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).

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


Short text of error message:
Control Framework : Error processing control
Long text of error message:
Technical information about the message:
Message class....... "CNDP"
Number.............. 006
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
to correct the error
Probably the only way to eliminate the error is to correct the program.
-
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:
"MESSAGE_TYPE_X" " "
"SAPLOLEA" or "LOLEAU02"
"AC_SYSTEM_FLUSH"
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.

System environment

SAP-Release 700

Application server... "temsaapp"

Network address...... "10.180.1.53"

Operating system..... "AIX"

Release.............. "5.3"

Hardware type........ "000A97A0D600"

Character length.... 8 Bits

Pointer length....... 64 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "temsapdb"

Database type..... "ORACLE"

Database name..... "TEP"

Database user ID.. "SAPR3"

Char.set.... "tr_TR.ISO8859-9"

SAP kernel....... 700

created (date)... "Aug 31 2006 20:36:57"

create on........ "AIX 2 5 005DD9CD4C00"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 75

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"

Memory consumption

Roll.... 16128

EM...... 8353536

Heap.... 0

Page.... 40960

MM Used. 2983992

MM Free. 1189648

User and Transaction


Client.............. ???
User................ "????????"
Language key........ "T"
Transaction......... "SQVI "
Program............. "SAPLOLEA"
Screen.............. "SAPLAQJD_CNTRL 0200"
Screen line......... 0

Information on where terminated

Termination occurred in the ABAP program "SAPLOLEA" - in "AC_SYSTEM_FLUSH".

The main program was "SAPMS38R ".

In the source code you have the termination point in line 29

of the (Include) program "LOLEAU02".

Source Code Extract

Line SourceCde

1 FUNCTION AC_SYSTEM_FLUSH .

2 *"----

-


3 ""Lokale Schnittstelle:

4 *" IMPORTING

5 *" VALUE(CALLED_BY_SYSTEM) TYPE C OPTIONAL

6 *" EXCEPTIONS

7 *" CNTL_SYSTEM_ERROR

8 *" CNTL_ERROR

9 *"----

-


10 data: sysubrc like sy-subrc.

11

12 CALL FUNCTION 'AC_FLUSH_CALL'

13 EXPORTING

14 SYSTEM_FLUSH = 'X'

15 CALLED_BY_SYSTEM = CALLED_BY_SYSTEM

16 IMPORTING

17 MESSAGE_NR = sysubrc

18 MESSAGE_TEXT = SY-MSGLI.

19

20 sy-subrc = sysubrc.

21

22 CASE SY-SUBRC.

23 WHEN 0.

24 WHEN 1.

25 * system_error

26 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 007 RAISING CNTL_SYSTEM_ERROR.

27 WHEN 2.

28 * method_call_error

>>>> MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.

30 WHEN 3.

31 * property_set_error

32 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.

33 WHEN 4.

34 * property_get_error

35 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.

36 WHEN OTHERS.

37 RAISE CNTL_ERROR.

38 ENDCASE.

Contents of system fields

Name Val.

SY-SUBRC 2

SY-INDEX 0

SY-TABIX 1

SY-DBCNT 1

SY-FDPOS 40

SY-LSIND 0

SY-PAGNO 0

SY-LINNO 1

SY-COLNO 1

SY-PFKEY 0200

SY-UCOMM OK

SY-TITLE DENEME hızlı görünümünü yarat: Veri kaynağını seç

SY-MSGTY X

SY-MSGID CNDP

SY-MSGNO 006

SY-MSGV1

SY-MSGV2

SY-MSGV3

SY-MSGV4

SY-MODNO 2

SY-DATUM 20070724

SY-UZEIT 164836

SY-XPROG SAPMSSY1

SY-XFORM XAB_READ

Active Calls/Events

No. Ty. Program Include Line

Name

12 FUNCTION SAPLOLEA LOLEAU02 29

AC_SYSTEM_FLUSH

11 FORM SAPFGUICNTL SAPFGUICNTL 256

HANDLE_FLUSH_PBO

10 FORM SAPMSSYD SAPMSSYD 191

%_CTL_OUTPUT_FLUSH

9 MODULE (PBO) SAPMSSYD SAPMSSYD 180

%_CTL_OUTPUT_FLUSH

8 FORM SAPLAQJD_CNTRL LAQJD_CNTRLF01 45

DEFINE_JOIN

7 FUNCTION SAPLAQJD_CNTRL LAQJD_CNTRLU02 114

RSAQ_DJ_DEFINE_JOIN_CNTRL

6 METHOD SAPMS38R MS38A_DATASOURCETREE 1535

LCL_DATASOURCE=>DEFINE_JOIN_VIA_CONTROL

5 MODULE (PAI) SAPMS38R MS38AI01 405

USER_COMMAND_3200

4 FORM SAPMS38R MS38AF10 377

COMMAND_ADDQ_QUICKVIEW

3 FORM SAPMS38R MS38AF10 332

COMMAND_ADDQ

2 FORM SAPMS38R MS38AF10 23

FUNKTION_AUSFUEHREN

1 MODULE (PAI) SAPMS38R MS38RI10 453

OK_CODE_050

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

just copying from your post:

>>Application server... "temsaapp"

>>Network address...... "10.180.1.53"

>>Operating system..... "AIX"

but you are right, it would happen on windows too with a very high probability.

Runtime Errors MESSAGE_TYPE_X are transaction (ABAP code) related.

Try to find the right forum for SQVI - SAP on Windows is definitely the wrong one.

peter

Former Member
0 Kudos

Internal notes

The termination was triggered in function "ab_jmess"

of the SAP kernel, in line 1263 of the module

"//bas/700_REL/src/krn/runt/abdynpro.c#7".

The internal operation just processed is "MESS".

Internal mode was started at 20070724164815.

ABAP Control Blocks (CONT)

Index Name Fl PAR0 PAR1 PAR2 PAR3 PAR4 PAR5 PAR6 Source Code Line

2116 cmpr 00 00CA 0091 0002 LOLEAU02 27

2118 BRAN 02 0002 LOLEAU02 27

2119 BRAX 00 000F LOLEAU02 27

2120 MOVL 00 0002 0093 002D LOLEAU02 29

2122 mlq1 01 0500 080A 0058 LOLEAU02 29

2124 MOVL 00 0008 0094 002F LOLEAU02 29

2126 CLEA 00 0095 LOLEAU02 29

2127 CLEA 00 0096 LOLEAU02 29

2128 CLEA 00 0097 LOLEAU02 29

2129 CLEA 00 0098 LOLEAU02 29

2130 FUNE 01 002B LOLEAU02 29

2131 ENDF 00 0000 LOLEAU02 29

>>>>> MESS 00 0000 LOLEAU02 29

2133 BRAX 00 0027 LOLEAU02 30

2134 cmpr 00 00CA 0091 0003 LOLEAU02 30

2136 BRAN 02 0002 LOLEAU02 30

2137 BRAX 00 000F LOLEAU02 30

2138 MOVL 00 0002 0093 002D LOLEAU02 32

2140 mlq1 01 0500 080A 0058 LOLEAU02 32

2142 MOVL 00 0008 0094 002F LOLEAU02 32