Skip to Content
0
Former Member
Dec 20, 2006 at 06:54 PM

ABAp dump in program "LOLEAU02"

496 Views

Runtime errors MESSAGE_TYPE_X

I have attached the dump analysis report

Error analysis

-


Short text of error message:

Control Framework : Error processing control

Technical information about the message:

Diagnosis

An error occurred when the system tried to process the commands

from the Automation Queue on the presentation server.

There are several possible reasons for this:

- The installation of the SAP GUI on the presentation server is

faulty or obsolete.

- There is an error in the application program

- There is an error in the SAPGUI or an integrated control

Procedure

1. Make sure that you have imported the appropriate Support

Package, the current kernel, and GUI patch for the release of your

system

2. Check whether the error occurs locally on one or a few PCs, or

generally on all PCs. Note whether the error only occurs for some

users, for example because of a specific Customizing setting.

If it only occurs locally, this suggests an installation problem

with the PC. Check the installation; if necessary, reinstall the

software. In the dump, search for the SY-MSGLI field, since it may

point to the cause of the error.

3. Activate the Automation Trace (in accordance with SAP Note

158985).

4.Start the transaction and continue until the screen immediately

before the dump.

5. From the System -> Utilities menu, choose Autom. Queue,

Synchronous Processing.

The status bar of the GUI displays the text:

"Automation synchron flush mode on"

6. If you now proceed with the application, the short dump will

display the ABAP call that caused the error; the Automation Trace

will contain the error on the presentation server.

7. If necessary, load the short dump and trace files on to

sapservX, so that SAP can analyze them.

Message classe...... "CNDP"

Number.............. 006

Variable 1.......... " "

Variable 2.......... " "

Variable 3.......... " "

Variable 4.......... " "

Variable 3.......... " "

Variable 4.......... " "

-


How to correct the error

-


Probably the only way to eliminate the error is to correct the program.

-

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:

-


"MESSAGE_TYPE_X" C

"SAPLOLEA" or "LOLEAU02"

"AC_SYSTEM_FLUSH"

-


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....... "dausjfc0"

Network address.......... "167.228.43.182"

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

Release.................. "5.2"

Hardware type............ "00C9F79E4C00"

Character length......... 8 Bits

Pointer length........... 64 Bits

Work process number...... 4

Short dump setting....... "full"

Database server.......... "dausjfc0"

Database type............ "ORACLE"

Database name............ "CCD"

Database owner........... "SAPR3"

Character set............ "diocletian"

SAP kernel............... "640"

Created on............... "Feb 27 2006 21:35:45"

Created in............... "AIX 1 5 00538A4A4C00"

Database version......... "OCI_920 "

Patch level.............. "116"

Patch text............... " "

Supported environment....

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

10.2.0.."

SAP database version..... "640"

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

-


User, transaction...

-


Client.............. 321

User................ "USLIF90"

Language key........ "E"

Transaction......... "SA38 "

Program............. "SAPLOLEA"

Screen.............. "SAPLGRAP 0210"

Screen line......... 0

-


Information on where termination occurred

-


The termination occurred in the ABAP program "SAPLOLEA" in "AC_SYSTEM_FLUSH".

The main program was "YQ9_UPLO ".

The termination occurred in line 29 of the source code of the (Include)

program "LOLEAU02"

of the source code of program "LOLEAU02" (when calling the editor 290).

-


Source code extract

-


000010 FUNCTION AC_SYSTEM_FLUSH .

000020 *"----


000030 ""Lokale Schnittstelle:

000040 *" IMPORTING

000050 *" VALUE(CALLED_BY_SYSTEM) TYPE C OPTIONAL

000060 *" EXCEPTIONS

000070 *" CNTL_SYSTEM_ERROR

000080 *" CNTL_ERROR

000090 *"----


000100 data: sysubrc like sy-subrc.

000110

000120 CALL FUNCTION 'AC_FLUSH_CALL'

000130 EXPORTING

000140 SYSTEM_FLUSH = 'X'

000150 CALLED_BY_SYSTEM = CALLED_BY_SYSTEM

000160 IMPORTING

000170 MESSAGE_NR = sysubrc

000180 MESSAGE_TEXT = SY-MSGLI.

000190

000200 sy-subrc = sysubrc.

000210

000220 CASE SY-SUBRC.

000230 WHEN 0.

000240 WHEN 1.

000250 * system_error

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

000270 WHEN 2.

000280 * method_call_error

-


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

000300 WHEN 3.

000310 * property_set_error

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

000330 WHEN 4.

000340 * property_get_error

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

000360 WHEN OTHERS.

000370 RAISE CNTL_ERROR.

000380 ENDCASE.

000390

000400 ENDFUNCTION.

-


Contents of system fields

Can some one help me to solve this issue.

vel.