Many MESSAGE_TYPE_X ABAP dumps occurring in the system

[Former Member]

Hi,

Users are getting MESSAGE_TYPE_X Dumps for different transactions such as

AL11, CJ20N, FBL1N, CADO, AW01N, SA39, SE16, SMEN, VA02, CAPS, LT24, CJI3, VL06O, CAT2, XK03, etc...

Kindly provide solution to avoid the dump...

Some of the Termination Information are as follows:

1)Information on where terminated

Termination occurred in the ABAP program "SAPLCOZV" - in "CO_ZV_ORDER_POST".

The main program was "SAPLCNPB_M ".

In the source code you have the termination point in line 281 of the (Include) program "LCOZVU01".

-

---

2) Information on where terminated

Termination occurred in the ABAP program "SAPFGUICNTL" - in "HANDLE_DATA_STREAM_ERROR".

The main program was "SAPLSMTR_NAVIGATION ".

In the source code you have the termination point in line 501 of the (Include) program "SAPFGUICNTL".

-

---

3) Information on where terminated

Termination occurred in the ABAP program "SAPLOLEA" - in "AC_SYSTEM_FLUSH".

The main program was "SAPLSMTR_NAVIGATION ".

In the source code you have the termination point in line 29 of the (Include) program "LOLEAU02".

-

---

etc..

Few Users have upgraded the SAP GUI Patch level to the latest version. But still we are finding MESSAGE_TYPE_X Dumps..

Kindly help.

Thanks and Regards,

Sowmya

Bangalore

[Former Member · Accepted solution]

Thanks all!

[Former Member · Accepted solution]

how did you resolve this issue ? Thanks in advance.

[Former Member · Accepted solution]

Hi Sowmya,

Hope you could post your solution on the issue.

Thanks

[Former Member · Accepted solution]

What was the answer to this problem?

[Former Member · Accepted solution]

Hi Sowmya,

How did you resolve this issue? Thanks in advance.

Regards,

P2

[Former Member · Accepted solution]

MESSAGE_TYPE_X is likely kernel problem.

You'd want to update your kernel level up to latest version.

That'll solve most cases.

Best Regards,

[gaurab_banerji]

the order is in edit mode while the status of the order was changed by the program. make sure no one including you do not have that order opened up in cor2 in edit mode. its the problem for me which just got solved.

[Former Member]

i am also faced this issue .

its bz of corrected files in SAP GUI.

upgrade the GUI patch or uninstall and reinstall the same GUI same patch level..

[Former Member]

The solution is to upgrade the SAP GUI patch level.

[Former Member]

Hi Sowmya,

How did you actually solve this problem? Can you post your solution on this probelm.

Thanking you in advance!

LG

[markus_doehr2]

> In the source code you have the termination point in line 501 of the (Include) program "SAPFGUICNTL".

You're right - all those patches point to GUI problems.

What kernel patchlevel are you using?

Markus

[Former Member]

Hi Markus,

Thanks for the reply.

The kernel patch level is 2 for some users and 4 for few users with 710 Release...

Is this the only solution?

Thanks and Regards,

Sowmya

[markus_doehr2]

> The kernel patch level is 2 for some users and 4 for few users with 710 Release...

??

What you list is most likely the SAPGUI patchlevel. Neverless, both are very old (over a year), I would upgrade them to the latest (patch 12).

I wanted to know the KERNEL patchlevel:

- logon to the system and execute "System - Status"

- press on the arrow-right button next to the cancel button

- on the left hand side, what is the patchlevel?

Markus

[Former Member]

Thanks Markus.

The Kernel Patch Level of the System is 167

(DBSL Patch Level)

Regards,

Sowmya

[markus_doehr2]

> The Kernel Patch Level of the System is 167

> (DBSL Patch Level)

And the kernel itself? The problem is not related to the database interface...

Markus

[anindya_bose]

Sowmya

Go to SM51-->Click on "Release Notes"

Provide the "SAP R/3 Kernel information"