abap dump after patch ugrade 15

[Former Member]

Hi ,

our XI system was upgraded from SP 10 to 15. On trying to see the pipeline steps and the xml details from MONI, it is showing the abap dump. But from moni itself I can click at other execution steps. Only at this particular step-data returned from ECC, it is throwing this dump. But the interfaces are working fine and the postings are also done in SAP properly.

error below:

http://rcpt.yousendit.com/617210935/7ef0f4d60a3eeb01068e231e16aba40e

Please suggest, Thanks in advance.

Regards,

kanan

[Former Member]

Hi All,

Could any1 please look into this?

Thanks

kanan

[Former Member]

Hi All,

Any1 to reply on this? Thanks..

kanan

[Former Member]

Hi Kanan,

Your link has expired.

Try to post the error in this thread.

Carlos

[Former Member]

Hi Carlos,

Quite lengthy, Sorry..as am not able to put up the url currently, simply pastingthe error:

kanan

-

---

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.

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.

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.

[Former Member]

Hi Kanan,

When you import a SP, in your case 15 SP, you have to take into account that your kernel must

be also updated as well as your GUI SAP logon.

So, I think the clue is in

Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
system

It could be your problem.

[Former Member]

Hi Kanan

Carlos is right

You need to upgrade your kernel as well as GUI. Upgrade it and it will be resolved.

Updating GUI itself worked for me.

Thanks

Gaurav

[Former Member]

Hi Gaurav/Carlos,

Thanks for your replies. Will I be able to upgarde the GUI and Kernel myself being a developer or is it the concern of basis team?

kanan

[Former Member]

Hi Kanan,

If you didn't do it before, I recommend you to asking for help basis team.

Carlos

[Former Member]

Thanks Carlos, a question...all the scenarios are working fine and this occurs only while trying to open the xml of a particular step only. Rest all steps are viewable. So will it harm if I keep it as it is..?? This is for my knowledge.

Regards,

kanan

[Former Member]

Hi,

theoretically it should not harm anything. Just you cannot see your xml payload steps properly.

Carlos

[Former Member]

Hi Carlos,

Thanks a lot for the info. I just wanted to make sure that nothing will be harmed and will not affect any other things by this.

I will also check out with the basis team in a day or 2 and update.

Plz giv me somedays for points so that I can close this query too

Thanks again.

kanan