on 04-14-2015 7:40 AM
Hi,
We have ECC 6.0. All the end users are getting dump when they login the system from SAP GUI.
We got the same dump one month back, that time we restarted the system temprarily the problem got solved. Agin this time we have got the same dump for all the users. We have not done any patching also.
Please suggest me how to solve and let me know if you need any more informaiton.
Thanks & Regards
Rao.
Dear Rao,
Message_Type_X Dump is likely Kernel Problem.
You need to Update Your Kernel level up to Latest Version.
That may solve your problem.
Regards,
Himanshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello rao ch,
You may check if there is change in role of the users and note 357693.
Best regards,
Yuki
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Regarding this issue, you can also refer to SAP KBA notes below:
1603032 - "Dump with MESSAGE_TYPE_X in SAPLOLEA and AC_SYSTEM_FLUSH and LOLEAU02"
1954476 - "Basic check points for MESSAGE_TYPE_X dump"
Regards,
Bíborka
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rao,
would you please attach the dump?
Many thanks,
Andreas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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). | |
What can you do? Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system | |
administrator. Using Transaction ST22 for ABAP Dump Analysis, you can look | |
at and manage termination messages, and you can also | |
keep them for a long time. | |
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.......... " " | |
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. |
Hi Rao,
have you already tried the latest gui patch?
All SAP GUI patches are made available on SAP Service Marketplace. For more detailed information about where the patches are stored, see SAP Note 563161. SAP Note 330793 describes how you can download the patches.
The installation of SAP GUI patches is described in detail in the SAP GUI installation guide. This guide is available at http://scn.sap.com/docs/DOC-25456.
SAP Note 535308 also contains useful information about installing patches.
Best regards,
Andreas
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.