topic Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump. in Application Development and Automation Discussions

MESSAGE_TYPE_X (Control Framework : Error processing control) dump.

Former Member — Wed, 22 Sep 2010 07:46:34 GMT

Hello Everyone,

I am getting following dump while processing an AlV report.

I have a button Filter Off, and when after running the report, i am trying to press this buttom, system gives following dump.

The error follow like this :

===========================================================================

Runtime Errors MESSAGE_TYPE_X

Date and Time 2009.12.03 19:37:16

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

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

Trigger Location of Runtime Error

Program SAPLOLEA

Include LOLEAU02

Row 29

Module type (FUNCTION)

Module Name AC_SYSTEM_FLUSH

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.

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.

20 sy-subrc = sysubrc.

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.

40 ENDFUNCTION.

===========================================================================

Please advise me about the expected root cause and solution or suggesstion of this issue.

Thanks

Regards

Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump.

Sandeep_Panghal — Wed, 22 Sep 2010 08:08:40 GMT

Have you already tried the solutions proposed in the dump , the suggestions in the procedure will rectify this .

Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump.

Former Member — Wed, 22 Sep 2010 09:31:39 GMT

Hi Sandeep,

Thanks for your input.

Following are the steps which i tried:

1. Make sure that you have imported the appropriate Support

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

system

-> Recently we upgraded the patch from 007 to 015. so right now we are on Release 600 and Level 0015 for SAP_APPL.

Also we are using SAP GUI 7.10. So do u think , this upgrade could be a reason for this dump. And in any of the case,

what could be solution.

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.

-> This dump is coming for all users and for all Machines.

Procedure 3 to 6:

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.

-> I read and followed the instruction given in note 158985. And with trace, i got following details.

Short text: Exception condition "CALL_METHOD_FAILED" raised.

What happened?: The current ABAP/4 program encountered an unexpected situation.

Error analysis:

A RAISE statement in the program "SAPLOLEA" raised

condition "CALL_METHOD_FAILED".

Since the exception was not intercepted by a super

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condit

Transaction SE37 (Function Library). You can take

function module from the display of active calls.

Trigger Location of Runtime Error:

Program SAPLOLEA

Include LOLEAU10

Row 261

Module type (FUNCTION)

Module Name AC_FLUSH_CALL_INTERNAL

Source Code Extract:

Line SourceCde

231

232 TABLES VERBS = VERBS

233 PARAMS = PARAMS

234 VARS = VARS

235 * SVARS = SVARS

236 RFC_QUEUE = RFC_QUEUE

237 XML_DATA_STREAM = XML_DATA_STREAM

238 ERROR_INFO = ERROR_INFO

239 EXCEPTIONS SYSTEM_FAILURE = 1 MESSAGE OLE_MESSAGE

240 CALL_METHOD_FAILED = 2

241 SET_PROPERTY_FAILED = 3

242 GET_PROPERTY_FAILED = 4

243 RFC_QUEUE_FAILED = 5

244 XML_DATA_FAILED = 6.

245

246 * save error return code from RFC

247 SAVE_SUBRC = SY-SUBRC.

248 SAVE_MSGLI = OLE_MESSAGE.

249

250 * check if we run in global flush mode

251 * if so we enforce a dump when a error at frontend occurs

252 DATA: FLUSHMODE TYPE C.

253 SYSTEM-CALL KERNEL_INFO 'GLOBAL_FLUSH_MODE' FLUSHMODE.

254

255 IF NOT FLUSHMODE IS INITIAL.

256 CASE SAVE_SUBRC.

257 WHEN 0.

258 WHEN 1.

259 RAISE SYSTEM_FAILURE.

260 WHEN 2.

>>>>> RAISE CALL_METHOD_FAILED.

262 WHEN 3.

263 RAISE SET_PROPERTY_FAILED.

264 WHEN 4.

265 RAISE GET_PROPERTY_FAILED.

266 WHEN 5.

267 RAISE RFC_QUEUE_FAILED.

268 WHEN 6.

269 RAISE XML_DATA_FAILED.

270 WHEN OTHERS.

271 RAISE UNKNOWN_ERROR.

272 ENDCASE.

273 ENDIF.

274

275 *- Do we have to record for CAT?

276 IF NOT CAT_RECORDING IS INITIAL.

277

278 * call CATT only for return values

279 IF NOT RETURN_VALUES_EXIST IS INITIAL.

280 CALL FUNCTION 'CAT_CONTROLS_RECORD'

But again, i am on the same point. This dump shows that, it's coming from standard program.

But how to resolve this dump.

Please let me know, if any other input is required from my side.

Regards

Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump.

CBasis — Fri, 14 Jan 2011 15:35:49 GMT

Hi PG,

did you find a solution for your problem?

I see the thread is marked as "answered", but i see no answer.

It looks like we do have the same/similar problem.

Best regards

Christian

Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump.

siddhesh_pathak4 — Tue, 15 Mar 2011 17:40:25 GMT

Cna anybody how to solve this issue? I am also facing the same issue with PI and that too for only one message.

Thanks,

Siddhesh Pathak

Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump.

amoldshinde — Wed, 13 Jul 2016 13:34:14 GMT

Hello,

Can someone provide resolution steps for this?

Thanks,

Amol

Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump.

Sandra_Rossi — Wed, 13 Jul 2016 14:01:46 GMT

It's impossible to answer simply to this question.

If it's a standard program, ask SAP support.

If you programmed a control yourself (control Framework), then this short dump simply says you have made an error, but doesn't explain the error. You need to get more information by starting a session trace, as explained in note 305363 - Create frontend trace file (https://service.sap.com/sap/support/notes/305363) -> button Customize Local Layout in the SAP GUI Window -> Options -> Trace -> choose your control (or all) -> start again your program, and verify the info in the trace file...

Re: MESSAGE_TYPE_X (Control Framework : Error processing control) dump.

sagi44 — Sun, 02 Feb 2025 16:29:49 GMT

This can occur when you have registered methods or events that are missing on the .ocx.
Make sure your registered events and methods are spelled correctly and are case sensitive.