Run Time Errormessage Type X MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR

[Former Member]

Hi ,

Users receiving short dumps:  Message_Type_X

Users I talked to were trying to open SAP Inbox.  But there are A LOT of short dumps for the same Message_Type_X  today.

I'm worried this might be a bigger issue than just one user.

ST22 Dump Details

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:
     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.

    Technical information about the message:
    Message class....... "CNDP"
    Number.............. 006
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "

How 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.

em environment
SAP Release..... 731
SAP Basis Level. 0006

Application server... -
Network address...... "-"
Operating system..... "AIX"
Release.............. "6.1"
Hardware type........ "00C2995A4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 89
Shortdump setting.... "full"

Database server... "hwuu051"
Database type..... "ORACLE"
Database name..... "CDE"
Database user ID.. "SAPSR3"

Terminal.......... "WHUR2CE0113N9N"

Char.set.... "C"

SAP kernel....... 721
created (date)... "Feb 28 2013 11:44:44"
create on........ "AIX 1 6 00CFADC14C00"
Database version. "OCI_112, 11.2.0.2.0, V1, default"

Patch level. 100
Patch text.. " "

Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11
SAP database version. 721
Operating system..... "AIX 1 6, AIX 1 7"

Memory consumption
Roll.... 0
EM...... 4189792
Heap.... 0
Page.... 24576
MM Used. 3433648
MM Free. 753472

and Transaction
Client.............. 100
User................ "ARNOLDL"
Language key........ "E"
Transaction......... " "
Transaction ID...... "5322665AE89E2BE0E10080000ADA0818"

EPP Whole Context ID.... "5322805BE6242170E10080000ADA0818"
EPP Connection ID....... "53226643DB152570E10080000ADA0818"
EPP Caller Counter...... 1

Program............. "SAPLOLEA"
Screen.............. "SAPLSGOSITS 0200"
Screen Line......... 0
Debugger Active..... "none"

Server-Side Connection Information
    Information on caller of Remote Function Call (RFC):
    System.............. "CDE"
    Installation Number. 0020078768
    Database Release.... 731
    Kernel Release...... 721
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchronous and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "

    Client.............. 100
    User................ "ARNOLDL"
    Transaction......... "/PBS/FBL1N"
    Call Program........."CL_GOS_TOOLBOX_VIEW===========CP"
    Function Module..... "GOS_EXECUTE_SERVICE"
    Call Destination.... "NONE"
    Source Server....... "-
    Source IP Address... "-

    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0

    Note:
    - For Releases < 4.0, information on the RFC caller not available.
    - The installation number is available from caller Release > 700

    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    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 "SAPLOLEA" - in "AC_SYSTEM_FLUSH".

The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 29
of the (Include) program "LOLEAU02".

rce Code Extract

e  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 'CN

33     WHEN 4.

34 *     property_get_e

35       MESSAGE ID 'CN

36     WHEN 8.

37 *     maximal number

38       MESSAGE ID 'CN

39     WHEN OTHERS.

40       RAISE CNTL_ERR

41   ENDCASE.

42

43 ENDFUNCTION.

Is it SAP GUI issue..?

[Former Member · Accepted solution]

Please perform checks according to SAP KBA 1603032 - Dump with MESSAGE_TYPE_X in SAPLOLEA and AC_SYSTEM_FLUSH and LOLEAU02.

[Former Member · Accepted solution]

Thanks For your Reply'

Any additional Suggestion.....

I am doin it Already

[Former Member · Accepted solution]

Please give a little bit more information about what has been done.