<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/message-type-x-control-framework-error-processing-control-dump/m-p/6411145#M1407913</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi James&lt;/P&gt;&lt;P&gt;I have got exactly the same problem as you had. But i did not understand how you solved it.&lt;/P&gt;&lt;P&gt;I am actually new to this and thus not very familiar with alv grid and all. So please tell me how you got over this dump.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 May 2010 14:46:13 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-05-27T14:46:13Z</dc:date>
    <item>
      <title>MESSAGE_TYPE_X (Control Framework : Error processing control) dump.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/message-type-x-control-framework-error-processing-control-dump/m-p/6411141#M1407909</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello~ everyone~&amp;lt;br&amp;gt;&lt;/P&gt;&lt;P&gt;Could you help me now... I'd like to receive some advice about this dump error "Control Framework : Error processing control".&amp;lt;br&amp;gt;&lt;/P&gt;&lt;P&gt;This dump is MESSAGE_TYPE_X error. &amp;lt;br&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;p&amp;gt;&lt;/P&gt;&lt;P&gt;The error follow like this :&lt;/P&gt;&lt;P&gt;&amp;lt;p&amp;gt;&lt;/P&gt;&lt;P&gt;===========================================================================&lt;/P&gt;&lt;P&gt;&amp;lt;p&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;p&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;Runtime Errors         MESSAGE_TYPE_X                                                               &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;Date and Time          2009.12.03 19:37:16                                                          &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;Short text                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    The current application triggered a termination with a short dump.                             &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;What happened?                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    The current application program detected a situation which really                              &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    should not occur. Therefore, a termination with a short dump was                               &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    triggered on purpose by the key word MESSAGE (type X).                                         &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;Error analysis                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Short text of error message:                                                                   &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Control Framework : Error processing control                                                   &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Long text of error message:                                                                    &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;     Diagnosis                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         An error occurred when the system tried to process the commands                           &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         from the Automation Queue on the presentation server.                                     &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         There are several possible reasons for this:                                              &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         - The installation of the SAP GUI on the presentation server is                           &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         faulty or obsolete.                                                                       &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         - There is an error in the application program                                            &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         - There is an error in the SAPGUI or an integrated control                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;     Procedure                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         1. Make sure that you have imported the appropriate Support                               &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         Package, the current kernel, and GUI patch for the release of your                        &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         system                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         2. Check whether the error occurs locally on one or a few PCs, or                         &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         generally on all PCs. Note whether the error only occurs for some                         &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         users, for example because of a specific Customizing setting.                             &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         If it only occurs locally, this suggests an installation problem                          &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         with the PC. Check the installation; if necessary, reinstall the                          &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         software. In the dump, search for the SY-MSGLI field, since it may                        &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         point to the cause of the error.                                                          &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         3. Activate the Automation Trace (in accordance with SAP Note                             &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         158985).                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         4.Start the transaction and continue until the screen immediately                         &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         before the dump.                                                                          &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         5. From the System -&amp;gt; Utilities menu, choose Autom. Queue,                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         Synchronous Processing.                                                                   &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         The status bar of the GUI displays the text:                                              &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;            "Automation synchron flush mode on"                                                    &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         6. If you now proceed with the application, the short dump will                           &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         display the ABAP call that caused the error; the Automation Trace                         &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         will contain the error on the presentation server.                                        &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         7. If necessary, load the short dump and trace files on to                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;         sapservX, so that SAP can analyze them.                                                   &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Technical information about the message:                                                       &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Message class....... "CNDP"                                                                    &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Number.............. 006                                                                       &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Variable 1.......... " "                                                                       &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Variable 2.......... " "                                                                       &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Variable 3.......... " "                                                                       &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Variable 4.......... " "                                                                       &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;Trigger Location of Runtime Error                                                                  &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Program                                 SAPLOLEA                                               &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Include                                 LOLEAU02                                               &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Row                                     29                                                     &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Module type                             (FUNCTION)                                             &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    Module Name                             AC_SYSTEM_FLUSH                                        &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;Source Code Extract                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;Line  SourceCde                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    1 FUNCTION AC_SYSTEM_FLUSH .                                                                   &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    2 *"----&lt;/P&gt;&lt;HR originaltext="-----------------------------------------------------------------" /&gt;&lt;P&gt;                     &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    3 &lt;STRONG&gt;"&lt;/STRONG&gt;"Lokale Schnittstelle:                                                                    &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    4 *"  IMPORTING                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    5 *"     VALUE(CALLED_BY_SYSTEM) TYPE  C OPTIONAL                                              &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    6 *"  EXCEPTIONS                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    7 *"      CNTL_SYSTEM_ERROR                                                                    &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    8 *"      CNTL_ERROR                                                                           &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;    9 *"----&lt;/P&gt;&lt;HR originaltext="-----------------------------------------------------------------" /&gt;&lt;P&gt;                     &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   10   data: sysubrc like sy-subrc.                                                               &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   11                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   12   CALL FUNCTION 'AC_FLUSH_CALL'                                                              &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   13        EXPORTING                                                                             &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   14             SYSTEM_FLUSH = 'X'                                                               &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   15             CALLED_BY_SYSTEM = CALLED_BY_SYSTEM                                              &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   16        IMPORTING                                                                             &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   17             MESSAGE_NR   = sysubrc                                                           &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   18             MESSAGE_TEXT = SY-MSGLI.                                                         &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   19                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   20   sy-subrc = sysubrc.                                                                        &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   21                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   22   CASE SY-SUBRC.                                                                             &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   23     WHEN 0.                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   24     WHEN 1.                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   25 *     system_error                                                                           &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   26       MESSAGE ID 'CNDP' TYPE 'X' NUMBER 007 RAISING CNTL_SYSTEM_ERROR.                       &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   27     WHEN 2.                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   28 *     method_call_error                                                                      &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;       MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.                              &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   30     WHEN 3.                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   31 *     property_set_error                                                                     &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   32       MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.                              &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   33     WHEN 4.                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   34 *     property_get_error                                                                     &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   35       MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.                              &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   36     WHEN OTHERS.                                                                             &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   37       RAISE CNTL_ERROR.                                                                      &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   38   ENDCASE.                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   39                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;   40 ENDFUNCTION.                                                                                &lt;/P&gt;&lt;P&gt;&amp;lt;br&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Dec 2009 11:25:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/message-type-x-control-framework-error-processing-control-dump/m-p/6411141#M1407909</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-03T11:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/message-type-x-control-framework-error-processing-control-dump/m-p/6411142#M1407910</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you trying to display an ALV container in a background mode?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please provide some prelude to this dump so that it will be easier to analyse .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Suhas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Dec 2009 12:03:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/message-type-x-control-framework-error-processing-control-dump/m-p/6411142#M1407910</guid>
      <dc:creator>SuhaSaha</dc:creator>
      <dc:date>2009-12-03T12:03:08Z</dc:date>
    </item>
    <item>
      <title>Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/message-type-x-control-framework-error-processing-control-dump/m-p/6411143#M1407911</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;This message appears (my case) when I use AdobeLiveCycle Designer to design Adobe forms in SAP. The reason is the integration is not perfect and sometimes the 3rd party application return a response to SAP GUI which is not expected. Conclusion: if the message appears in your 3rd party app, you should try to find a newest version and hope somebody has fixed this. &lt;/P&gt;&lt;P&gt;Regards, Otto&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Dec 2009 12:30:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/message-type-x-control-framework-error-processing-control-dump/m-p/6411143#M1407911</guid>
      <dc:creator>OttoGold</dc:creator>
      <dc:date>2009-12-03T12:30:04Z</dc:date>
    </item>
    <item>
      <title>Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/message-type-x-control-framework-error-processing-control-dump/m-p/6411144#M1407912</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have solved this problem. Thank you for your advice. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I used "cl_gui_simple_tree" in the program &lt;/P&gt;&lt;P&gt;the reason is duplicate data problem. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;take care.. thank you.. &lt;SPAN __jive_emoticon_name="grin"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;DEL&gt;-[sample code]&lt;/DEL&gt;--&lt;/P&gt;&lt;HR originaltext="-----------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  CALL METHOD G_STREE-&amp;gt;ADD_NODES&lt;/P&gt;&lt;P&gt;    EXPORTING&lt;/P&gt;&lt;P&gt;      NODE_TABLE                     = G_NODE_TABLE&lt;/P&gt;&lt;P&gt;      TABLE_STRUCTURE_NAME           = 'MTREESNODE'&lt;/P&gt;&lt;P&gt;    EXCEPTIONS&lt;/P&gt;&lt;P&gt;      FAILED                         = 1&lt;/P&gt;&lt;P&gt;      ERROR_IN_NODE_TABLE            = 2&lt;/P&gt;&lt;P&gt;      DP_ERROR                       = 3&lt;/P&gt;&lt;P&gt;      TABLE_STRUCTURE_NAME_NOT_FOUND = 4&lt;/P&gt;&lt;P&gt;      OTHERS                         = 5.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  CALL METHOD G_STREE-&amp;gt;EXPAND_NODE&lt;/P&gt;&lt;P&gt;    EXPORTING&lt;/P&gt;&lt;P&gt;      NODE_KEY = '*'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: james jang on Dec 4, 2009 3:35 AM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: james jang on Dec 4, 2009 3:50 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Dec 2009 02:34:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/message-type-x-control-framework-error-processing-control-dump/m-p/6411144#M1407912</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-12-04T02:34:33Z</dc:date>
    </item>
    <item>
      <title>Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/message-type-x-control-framework-error-processing-control-dump/m-p/6411145#M1407913</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi James&lt;/P&gt;&lt;P&gt;I have got exactly the same problem as you had. But i did not understand how you solved it.&lt;/P&gt;&lt;P&gt;I am actually new to this and thus not very familiar with alv grid and all. So please tell me how you got over this dump.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 May 2010 14:46:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/message-type-x-control-framework-error-processing-control-dump/m-p/6411145#M1407913</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-05-27T14:46:13Z</dc:date>
    </item>
  </channel>
</rss>

