Message_type_x aborts

[Former Member]

We have been having these aborts on a mix of situations since going to ECC 6.0. Many users at gui 6.20 patch 65, a few including myself at 7.10 patch 3. We are using kernel 0104. The aborts seem to be hit/miss. The dump also gets into instructions on doing traces etc.

I have used st03/st03n several times since going to 6.0, and yesterday was surprised, when a click on the app server with the st03 display aborted with message_type_x. Kind of out of the blue, the only patching being IBM ptfs. This has been working ok.

I checked all three of our instances. DEV and PRD act the same way aborts. QAS works fine. All the environments are the same. DEV and QAS run off the same iSeries partition. I’ve went to multiple different pc with different gui installs and the results is the same.

Anyone with ideas…what is going on with this?. I’ve seen note 1035246, the reasoning in that note is not applicable. A search here shows another user with similar issue and note 852158 solved his issue, and that is not our problem.

[michael_ruth3]

Jerry,

it is a GUI issue, I told them that a couple years ago.

What are you doing back working for them, I thought you retired?

[Former Member]

Hi Jerry,

If you got succes to resolve this issue than please provide the solution.

Regards

Anuj jain,

[markus_doehr2]

First, MESSAGE_TYPE_X doesn't indicate a GUI failure by default. It's just a "generic" exception many programmers @ SAP raise if "something" is going wrong.

I have seen many of indeterministic errors with the SAPGUI, sometimes I see, that saplogon.exe or sapgui.exe is not terminated even if there's no more window visible and thus restarting makes the system dump.

The GUI itself is a really complex beast using lots of COM+ technology (I have hear there are more than 1000 DLLs/OCX'es registered on installation) - and all that need to work together nicely.

If we see such errors, we request the user to reboot his machine, in 99,9 % of the cases this solves the problem. If it does not, we reinstall the GUI. Those problems are just too indeterministic and un-reproducable to dig further down, it's just too cumbersome.

--

Markus

[Former Member]

I went to multiple different pc, both 6.20 and 7.10 gui's. It's happening in two of three instances. It was NOT happening some days back. Reboot is the first thing I did, and I also used SAP* to see if id related, it's not.

Volker the dump says it's in AC_SYSTEM_FLUSH. Is this 10 lines back?? I think you're wanting whats before this module.

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.

[Former Member]

Hi Jerry,

that sounds weared ....

this is typically a GUI problem ;-(((

I would suggest to restart the PC and test and then to reinstall the SAPGUI an test and then if it still fails, to open an OSS ticket ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

I will open a ticket.

I went to several different pc's because I was thinking sapgui...and that is one of the reasons for doing that. I don't believe it's really the gui. And with it working in QAS tends to support that. But with it aborting DEV/PRD, but not QAS, really has me scratching my head.

[Former Member]

Hi Jerry,

I think, the most interesting would be to see the ABAP source code and abotu 10 lines above ... not every Message_type_x has to do with the GUI ...

... it just means: the program WANTS to crash down ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de