cancel
Showing results for 
Search instead for 
Did you mean: 

Getting MESSAGE_TYPE_X error while creating smartforms

Former Member
0 Kudos

Hello Everybody,

I am a BASIS guy and one of my finance user is facing the following problem:

while creating a Smartform "ZSF_BIL_INVOICE5" in Pages and Windows ->Main Main Window ->%Table1 New Table 1 ->Header ->%ROW6 New Line 6 ->%Cell9 New Column9 ->%Text7 New Text7.After going through these steps an error pops Up as mentioned below:

Runtime Errors MESSAGE_TYPE_X

Date and Time 07.02.2008 09:32:04

ShrtText

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

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

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.

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

39

40 ENDFUNCTION.

User and Transaction

Client.............. 100

User................ "HSS12195"

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

Transaction......... "SMARTFORMS "

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

Screen.............. "SAPLSTXB 0100"

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

Information on where terminated

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

The main program was "SAPMSSFO ".

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

I had also gone through the Note:954372,108387.I had also applied the latest SAP GUI Patchlevel 29 for release 640 still I am facing the same problem of "MESSAGE_Type_X".Please suggest the solution for the above mentioned problem as soon as possible.

Thanks and Regards,

Ashish Thakkar.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

I have also seen this numerous times , the only solution I ever found was

Go to the latest SAPGui of 7.10 Patch level 2. I've been using it since it came out and it works flawlessly.

The Message_type_x is a problem with your SAPGui installation. If you want to do it the clean way, UNINSTALL your SAPGui and then install a new one and patch it to the latest patches.

Thanks

Please reward points