Hello~ everyone~<br>
Could you help me now... I'd like to receive some advice about this dump error "Control Framework : Error processing control".<br>
This dump is MESSAGE_TYPE_X error. <br>
<p>
The error follow like this :
<p>
===========================================================================
<p>
<p>
<br>Runtime Errors MESSAGE_TYPE_X
<br>Date and Time 2009.12.03 19:37:16
<br>
<br>
<br>Short text
<br> The current application triggered a termination with a short dump.
<br>
<br>What happened?
<br> The current application program detected a situation which really
<br> should not occur. Therefore, a termination with a short dump was
<br> triggered on purpose by the key word MESSAGE (type X).
<br>
<br>Error analysis
<br> Short text of error message:
<br> Control Framework : Error processing control
<br>
<br> Long text of error message:
<br> Diagnosis
<br> An error occurred when the system tried to process the commands
<br> from the Automation Queue on the presentation server.
<br> There are several possible reasons for this:
<br> - The installation of the SAP GUI on the presentation server is
<br> faulty or obsolete.
<br> - There is an error in the application program
<br> - There is an error in the SAPGUI or an integrated control
<br> Procedure
<br> 1. Make sure that you have imported the appropriate Support
<br> Package, the current kernel, and GUI patch for the release of your
<br> system
<br> 2. Check whether the error occurs locally on one or a few PCs, or
<br> generally on all PCs. Note whether the error only occurs for some
<br> users, for example because of a specific Customizing setting.
<br> If it only occurs locally, this suggests an installation problem
<br> with the PC. Check the installation; if necessary, reinstall the
<br> software. In the dump, search for the SY-MSGLI field, since it may
<br> point to the cause of the error.
<br> 3. Activate the Automation Trace (in accordance with SAP Note
<br> 158985).
<br> 4.Start the transaction and continue until the screen immediately
<br> before the dump.
<br> 5. From the System -> Utilities menu, choose Autom. Queue,
<br> Synchronous Processing.
<br> The status bar of the GUI displays the text:
<br> "Automation synchron flush mode on"
<br> 6. If you now proceed with the application, the short dump will
<br> display the ABAP call that caused the error; the Automation Trace
<br> will contain the error on the presentation server.
<br> 7. If necessary, load the short dump and trace files on to
<br> sapservX, so that SAP can analyze them.
<br>
<br> Technical information about the message:
<br> Message class....... "CNDP"
<br> Number.............. 006
<br> Variable 1.......... " "
<br> Variable 2.......... " "
<br> Variable 3.......... " "
<br> Variable 4.......... " "
<br>
<br>Trigger Location of Runtime Error
<br> Program SAPLOLEA
<br> Include LOLEAU02
<br> Row 29
<br> Module type (FUNCTION)
<br> Module Name AC_SYSTEM_FLUSH
<br>
<br>Source Code Extract
<br>Line SourceCde
<br> 1 FUNCTION AC_SYSTEM_FLUSH .
<br> 2 *"----
<br> 3 ""Lokale Schnittstelle:
<br> 4 *" IMPORTING
<br> 5 *" VALUE(CALLED_BY_SYSTEM) TYPE C OPTIONAL
<br> 6 *" EXCEPTIONS
<br> 7 *" CNTL_SYSTEM_ERROR
<br> 8 *" CNTL_ERROR
<br> 9 *"----
<br> 10 data: sysubrc like sy-subrc.
<br> 11
<br> 12 CALL FUNCTION 'AC_FLUSH_CALL'
<br> 13 EXPORTING
<br> 14 SYSTEM_FLUSH = 'X'
<br> 15 CALLED_BY_SYSTEM = CALLED_BY_SYSTEM
<br> 16 IMPORTING
<br> 17 MESSAGE_NR = sysubrc
<br> 18 MESSAGE_TEXT = SY-MSGLI.
<br> 19
<br> 20 sy-subrc = sysubrc.
<br> 21
<br> 22 CASE SY-SUBRC.
<br> 23 WHEN 0.
<br> 24 WHEN 1.
<br> 25 * system_error
<br> 26 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 007 RAISING CNTL_SYSTEM_ERROR.
<br> 27 WHEN 2.
<br> 28 * method_call_error
<br>>>>>> MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
<br> 30 WHEN 3.
<br> 31 * property_set_error
<br> 32 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
<br> 33 WHEN 4.
<br> 34 * property_get_error
<br> 35 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
<br> 36 WHEN OTHERS.
<br> 37 RAISE CNTL_ERROR.
<br> 38 ENDCASE.
<br> 39
<br> 40 ENDFUNCTION.
<br>