on 06-16-2009 8:01 AM
Dear Team,
In my Product server This ABAP Dump is continues is comming.
Runtime Errors RAISE_EXCEPTION
Date and Time 16.06.2009 12:06:47
Short text
Exception condition "SYSTEM_FAILURE" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
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
A RAISE statement in the program "SAPLOLEA" raised the exception
condition "SYSTEM_FAILURE".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
-
How to correct the error
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:
"RAISE_EXCEPTION" " "
"SAPLOLEA" or "LOLEAU10"
"AC_FLUSH_CALL_INTERNAL"
or
"SAPLOLEA" "SYSTEM_FAILURE"
or
"RSMON000_ALV " "SYSTEM_FAILURE"
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.
System environment
SAP-Release 700
Application server... "appkg"
Network address...... "192.168.11.25"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "sapprd1"
Database type..... "ORACLE"
Database name..... "PRD"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on....... "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 16192
EM...... 8379680
Heap.... 0
Page.... 16384
MM Used. 3597152
MM Free. 4779680
User and Transaction
Client.............. 500
User................ "BASIS"
Language key........ "E"
Transaction......... "SM50 "
Transactions ID..... "4A36846A40A30C42E1000000C0A80B19"
Program............. "SAPLOLEA"
Screen.............. "SAPLSLVC_FULLSCREEN 0500"
Screen line......... 0
Information on where terminated
Termination occurred in the ABAP program "SAPLOLEA" - in
"AC_FLUSH_CALL_INTERNAL".
The main program was "RSMON000_ALV ".
In the source code you have the termination point in line 352
of the (Include) program "LOLEAU10".
Source Code Extract
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This error message you can see in lot of problems. So it is hard to give solution. Most of the case will be with SAPGUI. Try to get latest version or patch of SAPGUI. You should also try to reinstall Internet Explorer on the affected workstation as GUI uses some components of IE. You must also load newest Microsoft patches too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check note 2061219
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Guest,
Did you solve this error? I`m with the same problem.
Thanks,
Fernanda
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
I got the same error and detected that it's caused by cstring data, eg.
data: begin of itab,
i_char type char2, "-this field's ok
i_string type string, "-this field cause error
end of itab.
data: go_spreadsheet type ref to I_OI_SPREADSHEET.
...
dump in this step
CALL METHOD go_spreadsheet->insert_one_table
EXPORTING
data_table = itab
fields_table = ...
rangename = ...
wholetable = ...
no_flush = ...
IMPORTING error = ...
retcode = ...
...
-> so you can change data type from string(cstring) to char.
RG,
Hung.
> A RAISE statement in the program "SAPLOLEA" raised the exception
> condition "SYSTEM_FAILURE".
> "RAISE_EXCEPTION" " "
> "SAPLOLEA" or "LOLEAU10"
> "AC_FLUSH_CALL_INTERNAL"
> Patch level. 146
This happens when an OLE call from the system (flush) to the SAPGUI is failing.
I would
- install the latest SAPGUI patchlevel on the affected PCs
- upgrade your kernel to the latest patchlevel (we had likewise issues and they were fixed with the latest kernels)
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Markus,
Is there any other way other than Kernal upgrade to solve this dump..? At the moment I am not in a position to upgrade the Kernal level. I have applied the latest GUI patch level in my PC...
The error message is
Short text
Exception condition "SYSTEM_FAILURE" raised.
"RAISE_EXCEPTION" " "
"SAPLOLEA" or "LOLEAU10"
"AC_FLUSH_CALL_INTERNAL"
or
"SAPLOLEA" "SYSTEM_FAILURE"
Regards,
Senthilraj Selvaraj
> Is there any other way other than Kernal upgrade to solve this dump..? At the moment I am not in a position to upgrade the Kernal level. I have applied the latest GUI patch level in my PC...
The problem is related to a communication between GUI and server. If there's another solution I don't know. I just know that we had likewise errors that were fixed with a kernel patch.
You can always create an OSS call (BC-FES-GUI) and ask SAP for another solution.
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.