hi,
i am getting abap dump when i am running st03n tcode and click on expert mode. i am here pasting the abap dump.
Runtime Error MESSAGE_TYPE_X
Occurred on 18.10.2011 at 09:16:15
-
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?
-
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
-
Error analysis
-
Short text of error message:
Control Framework : Error processing control
Technical information about the 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.
Message classe...... "CNDP"
Number.............. 006
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
-
How to correct the error
-
Probably the only way to eliminate the error is to correct the program.
-
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
-
"MESSAGE_TYPE_X" C
"SAPLOLEA" or "LOLEAU02"
"AC_SYSTEM_FLUSH"
-
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
-
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
-
System environment
-
SAP Release.............. "620"
Application server....... "Network address.......... ""
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x AMD64 Level"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "OMAX-DEV"
Database type............ "ORACLE"
Database name............ "OMD"
Database owner........... "SAPOMP"
Terminal................. "Hariomlaptop"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Apr 30 2010 21:27:06"
Created in............... "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
Database version......... "OCI_10201_SHARE "
Patch level.............. "327"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.., ORACLE 10.2.0.., ORACLE 11.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0, Windows NT 6.1"
-
User, transaction...
-
Client.............. 087
User................ "BASIS"
Language key........ "E"
Transaction......... "ST03N "
Program............. "SAPLOLEA"
Screen.............. "SAPWL_ST03N 1000"
Screen line......... 0
-
Information on where terminated
-
The termination occurred in the ABAP program "SAPLOLEA" in "AC_SYSTEM_FLUSH".
The main program was "SAPWL_ST03N ".
The termination occurred in line 29 of the source code of the (Include)
program "LOLEAU02"
of the source code of program "LOLEAU02" (when calling the editor 290).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.