cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime errors for Branched in SXMB_MONI

Former Member
0 Kudos

Hi,

After PI 7.0 has been upgraded to SPS16, every time I try to display a message in status "Branched" from SXMB_MONI I get a runtime error. Also I got an error when trying to display it from RWB Monitor.

Messages in other statuses donu2019t have problems

Any suggestion why is that? Thanks.

Janos

Accepted Solutions (1)

Accepted Solutions (1)

former_member181985
Active Contributor
0 Kudos

Hi,

Please post the errors.

Thanks,

Gujjeti.

Former Member
0 Kudos

Hi,

It is error Message_type_X, but I don't think it is a SAPGUI problem, since I got the same problem with SAPGUI 710 and SAPGUI 640

Bellow is the extract from ST22.

Runtime Errors MESSAGE_TYPE_X

Date and Time 22.09.2008 13:50:43

Short text

The current application triggered a termination with a short dump.

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

How to correct the error

Probably the only way to eliminate the error is to correct the program.

-

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"MESSAGE_TYPE_X" " "

"SAPLOLEA" or "LOLEAU02"

"AC_SYSTEM_FLUSH"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

kkram
Contributor
0 Kudos

Looks like an issue in the HTML editor. I would suggesting raising a OSS message if a note doesn't exist already.

KK

Former Member
0 Kudos

Hi,

You need to Implement SAP note 1172765.

Solution

Upgrade to the Support Package assigned to this note or apply the correction instructions.

Hope its helpful.

Former Member
0 Kudos

The note solved the problem.Thanks a lot.

Answers (0)