Error after update SAP kernel

[Former Member]

Hello Gurus,

We have updated the SAP Kernel to SAP ERP ECC 6.0, our system is Windows 2003 and SQL Server, we had installed SAP Kernel release 172 and updated it to 254, after the update in Tx ST22 some dumps are show: SYSTEM_CORE_DUMPED

this is the full dump log:

Errores tiempo ejec. SYSTEM_CORE_DUMPED

Fecha y hora 26.09.2010 10:12:44

-

-

---

-

-

---

Texto breve

Process terminated by signal 0.

-

-

---

-

-

---

¿Qué ha sucedido?

Error in the SAP kernel.

The current ABAP "SAPLMR1M" program had to be terminated because the

ABAP processor detected an internal system error.

-

-

---

-

-

---

¿Qué puede hacer?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

-

-

---

-

-

---

Anál.errores

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 BOGPRDNW_PRD_00 on host BOGPRDNW (wp 3)"

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:

Error number..... " "

Error text....... " "

-

-

---

-

-

---

Entorno sistema

SAP-Release 700

Application server... "BOGPRDNW"

Network address...... "192.168.135.166"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "8x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 3

Shortdump setting.... "full"

Database server... "BOGPRDNW"

Database type..... "MSSQL"

Database name..... "PRD"

Database user ID.. "prd"

Char.set.... "C"

SAP kernel....... 700

created (date)... "May 3 2010 22:46:28"

create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"

Database version. "SQL_Server_8.00 "

Patch level. 254

Patch text.. " "

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0, Windows NT 6.1"

Memory consumption

Roll.... 16192

EM...... 20949200

Heap.... 0

Page.... 172032

MM Used. 16454816

MM Free. 301248

-

-

---

-

-

---

Usuario y transacción

Client.............. 400

User................ "ANDMORENO"

Language key........ "S"

Transaction......... "MIRO "

Transactions ID..... "107FC9DF052EF120BA8700237D65A060"

Program............. "SAPLMR1M"

Screen.............. "SAPLMR1M 6250"

Screen line......... 0

-

-

---

-

-

---

Info posición de cancelación

Termination occurred in the ABAP program "SAPLMR1M" - in "SYSTEM-EXIT".

The main program was "SAPLMR1M ".

In the source code you have the termination point in line 0

of the (Include) program " ".

-

-

---

-

-

---

Notas internas

The termination was triggered in function "ab_CoreInfo"

of the SAP kernel, in line 7371 of the module

"//bas/700_REL/src/krn/runt/abrabax.c#37".

The internal operation just processed is "----".

Internal mode was started at 20100926100222.

Stack trace of 'core'.

-

-

---

How we can fix this error?? this dump is generated in Tx such MIRO or MIGO

thanks

HEPC

[Former Member · Accepted solution]

Hello All,

Thanks for your answers and help. The solution was, additional to update the kernel (254) we applied the last disp+work, enq and ENSERVER packages. The kernel level now is 272. Perhaps is the solution but SAP have not published any note about that.

HEPC

[mercedes_fernandez · Accepted solution]

Hello,

the SAP note addressing this issue is 1453114, gets solved with kernel patch 700, 257

kind regards,

Mercedes

[Former Member · Accepted solution]

Hello Mercedes,

Thanks for the solution. The SAP Note 1453114 - Maximum string length is the correct for this error.

HEPC

[Former Member]

Dear HEPC,

Can you try lowering one level of your kernel and check if you have any issues? sometimes this works ..

Regards

Shailesh Mamidwar

[Former Member]

I agree with Mr. Mamidwar.

Actually it seems that you cannot do anything by yourself to fix the error. As it raised after updating the kernel, it is probably caused by an unwanted behaviour of MIGO with the new binaries. Probably SAP Support will release a note or patch soon. In the meanwhile, please try to decrease the patch level number.

Best Regards

Francisco

[mercedes_fernandez]

Hello,

to find out the reason of the CORE_DUMP is needed to check the function causing the core. In the ST22 short dump, there should be a C-Stack that returns the call sequence for the active C-functions of the process.

kind regards,

Mercedes

[Former Member]

Hello Mercedes,

I found this:

SAP (R) - R/3(TM) Callstack, Version 1.0 |

Copyright (C) SAP AG. All rights reserved.

Application exception occurred:

Exception : c0000005 (Access Violation)

App : disp+work.EXE (pid=1476)

When : 9/26/2010 10:12:44.68

Threads : 2

Computer Name : BOGPRDNW

User Name : SAPServicePRD

Number of Processors: 8

Processor Type: EM64T Family 6 Model 23 Stepping 10

Windows Version : 5.2 Current Build: 3790

State Dump for Thread Id 508

FramePtr ReturnAd Param#1 Function Name

00000000083d6ab0 000000000076c5ce 00000000000000fe msvcrt!memcpy

00000000083d6b60 000000000076e5a4 000000000ae153c5 disp+work!DiagoWriteRow [diagotab.c (2328)]

00000000083d6c70 000000000076ebd2 0000000034683000 disp+work!DiagoTableLoop [diagotab.c (1482)]

00000000083d6f30 000000000076eeef 000007fe57c55e9c disp+work!DiagoTable [diagotab.c (389)]

00000000083d7110 00000000007664da 000000000ae11c01 disp+work!DiagoTableControl [diagotab.c (232)]

00000000083d71b0 00000000007661e0 000000000ae1130c disp+work!DiagoContainer [diagoutn.c (3952)]

00000000083d7250 0000000000766495 0000000000000002 disp+work!DiagoDynpro [diagoutn.c (3580)]

00000000083d72f0 00000000007661e0 000000000ae10d0c disp+work!DiagoContainer [diagoutn.c (3942)]

00000000083d7390 0000000000766495 000000000ae0f534 disp+work!DiagoDynpro [diagoutn.c (3580)]

00000000083d7430 00000000007661e0 000000000ae0f40c disp+work!DiagoContainer [diagoutn.c (3942)]

00000000083d74d0 0000000000766495 0000000000000000 disp+work!DiagoDynpro [diagoutn.c (3580)]

00000000083d7570 00000000007661e0 000000000ae0f000 disp+work!DiagoContainer [diagoutn.c (3942)]

00000000083d7610 0000000000766809 0000000000000000 disp+work!DiagoDynpro [diagoutn.c (3580)]

00000000083d7cf0 0000000000751ccd 000000000001cfc7 disp+work!DiagoArea [diagoutn.c (130)]

00000000083d7da0 000000000075287a 000000000ae0daa5 disp+work!DiagoDynproOrList [diagoutp.c (1194)]

00000000083d8790 00000000007532d7 0020002000000002 disp+work!diagoutput [diagoutp.c (750)]

00000000083d88c0 0000000000745c9a 000007ffaf8d0050 disp+work!diagmout [diagoutp.c (246)]

00000000083d8ee0 000000000063e367 0000000000000000 disp+work!diagmsgo [sapdiag.c (196)]

00000000083d90d0 0000000000684230 000007fe58011a40 disp+work!dytrcexit [dymain.c (2679)]

00000000083d9160 0000000000689bda 0000000000000000 disp+work!dynpoutf [dymainstp.c (4701)]

00000000083d9210 0000000000642993 0000000000000000 disp+work!dynprctl [dymainstp.c (361)]

00000000083dfc30 00000000004f564b 0000000000000013 disp+work!dynpen00 [dymain.c (1920)]

00000000083dfeb0 00000000004306db 000000000ad1f080 disp+work!TskhLoop [thxxhead.c (4652)]

00000000083dfee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1166)]

00000000083dff10 0000000001a52761 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]

00000000083dff70 0000000077d596ac 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]

00000000083dffa0 0000000000000000 0000000001a525f0 kernel32!BaseProcessStart

State Dump for Thread Id 1548

FramePtr ReturnAd Param#1 Function Name

000000000f4bfe40 0000000077d5f6f1 00000000084729d0 ntdll!NtFsControlFile

000000000f4bfeb0 000000000193802f 0000000000000000 kernel32!ConnectNamedPipe

000000000f4bff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]

000000000f4bff70 0000000077d6b71a 0000000077d6b6e0 msvcrt!endthreadex

|000000000f4bffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart

I expect is the dump part that you need.

HEPC

Edited by: Hernando Polania Cadena on Sep 27, 2010 9:36 PM