on 12-19-2011 1:37 PM
Hi
I am getting following error . Process terminated by signal 0
The current ABAP "SAPLSD41" program had to be terminated because the
ABAP processor detected an internal system error.
An R/3 System process was terminated by an operating system signal.
-
Possible reasons for this are:
1. Internal system error.
2. Process was terminated externally (by the system administrator).
-
Last error logged in SAP kernel
Component............ "Taskhandler"
Place................ "SAP-Server sugarland_DE1_11 on host sugarland (wp 1)"
Version.............. 1
Error code........... 11
Error text........... "ThSigHandler: signal"
Description.......... " "
System call.......... " "
Module............... "thxxhead.c"
Line................. 10852
The error reported by the operating system is:
How to correct the Error
The R/3 System work directory (e.g. /usr/sap/c11/D00/work ) often
contains a file called 'core'.
Save this file under another name.
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
Error number..... " "
Information on where terminated
Termination occurred in the ABAP program "SAPLSD41" - in "SYSTEM-EXIT".
The main program was "SAPMSRD0 ".
In the source code you have the termination point in line 0
of the (Include) program " ".
Need your advice on this?
Thanks
Srikanth
Hello,
Please check note
note 1555682 Defective stack kernel 7.00 SP23, 7.01 SP08, 7.02
Please apply latest disp+work and dbsl patches.
regards,
John Feely
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would check the "analysis" section of the dump in ST22 to see, where the core dump occurs (database client, SAP kernel) - then go from there.
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please upgrade your kernel to latest and then check. It should resolve the problem.
Hope this is useful.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Is this new installation on 2008 R2? If yes (or No), try to update to the latest kernel (SAPEXE + SAPEXEDB), dw, libdbsl to the latest.
Cheers,
Nicholas Chang
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First you try to check if this core file in work directory is huge in size. Make sure you don't get full file system situation due to it (/usr/sap Filesystem). Delete it if you have to.
Then see what is your current SAP release and current kernel patch level. If this kind of dump is regular then problem is most probably due to current kernel patch level. You should try to go for highest kernel patch available.
Also try to discuss with your functional/abap team if you can find out some other reason of this ABAP dump.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
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.