Shared Memory Issue on Windows Server 2003

[Former Member]

Dear All,

Our scenario :

SAP Servers on

OS : Windows Server 2003 R2 SP2 (64 Bit) with 64 GB RAM

SAP Version : SAP 6.0

Our SAP BASIS Team has said that our server is having shared memory issue, and thats why we have to reboot the server every week.

We are stopping SAP Application for backup every week.

On the startup it is giving Shared memory issue(As told by SAP BASIS Team).

We want to get rid of this situation.

Is there any permenant solution for this problem?

May be from OS Side or SAP Application Side?

- Ashish K

I have some log which BASIS Team has shared with us :

Edited by: ashxos on Aug 16, 2011 3:56 PM

[markus_doehr2 · Accepted solution]

> Is there any permenant solution for this problem?

> May be from OS Side or SAP Application Side?

Since Windows 2003 is quite "old" already and the general support for it ended in 2010 (http://support.microsoft.com/lifecycle/?p1=3198) I suggest you upgrade to Windows 2008 (R2).

For a more detailed debugging I suggest you open an OSS call (under component BC-OP-NT) and attach the log you have here.

What you might try is to also restart the SAP service (startsapsrv) to release all the shared memory segments that are allocated before you restart the system - as a workaround. Mid term I would definitely upgrade to Windows 2008 (R2).

Markus

[Former Member · Accepted solution]

@Markus,

> What you might try is to also restart the SAP service (startsapsrv) to release all the shared memory segments that are

allocated before you restart the system - as a workaround.

We have already tried to restart the services, but it giving the error message which is attached above.

Windows upgrade we will take in the consideration. Is there any other workaround for this?

@John Feely

We have servers having 64 GB RAM.... around 50GB is always free. Still why SAP is giving the MEMORY related issue? Why it cant utiliza remaining free memory which is there?

Thank you all for your valuable reply.

Ashish K

[former_member189546]

Hello,

For c0005 error both programmes Windows and disp+work try to

access same address space

Kernel upgrade normally sorts this.

Main note for memory parameters is

88416 Zero administration memory management

regards,

John Feely

[former_member189546]

Hello,

Check memory paramaeters with

88416 Zero administration memory management as of 4.0A/

You have error

c0000005 (Access Violation) App

Windows violation with disp+work

Normally a full kenel stack upgrade solves this

note 19466

1603415 - Kernel update

regards,

John Feely

[Former Member]

Hi,

Thank you for your valuable reply.

I am not the SAP BASIS person. Can you please explain the problem which is their?

Is this a known problem?

Is it a bug in SAP?

What parameters should be their for System having 64 GB RAM?

Thanks again...

- Ashish K

[Former Member]

This message was moderated.

[Former Member]

---

trc file: "dev_disp", trc level: 1, release: "701"

-

---

sysno 02

sid ECP

systemid 562 (PC with Windows NT)

relno 7010

patchlevel 0

patchno 111

intno 20020600

make: multithreaded, Unicode, 64 bit, optimized

pid 7328

Tue Aug 16 08:22:34 2011

kernel runs with dp version 244000(ext=110000) (@(#) DPLIB-INT-VERSION-244000-UC)

length of sys_adm_ext is 576 bytes

• SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (02 7328) [dpxxdisp.c 1287]

shared lib "dw_xml.dll" version 111 successfully loaded

shared lib "dw_xtc.dll" version 111 successfully loaded

shared lib "dw_stl.dll" version 111 successfully loaded

shared lib "dw_gui.dll" version 111 successfully loaded

shared lib "dw_mdm.dll" version 111 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3900

Tue Aug 16 08:22:38 2011

• WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5534]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: start server >encecpprdci_ECP_02 <

DpShMCreate: sizeof(wp_adm) 36800 (1752)

DpShMCreate: sizeof(tm_adm) 58861440 (29416)

DpShMCreate: sizeof(wp_ca_adm) 80000 (80)

DpShMCreate: sizeof(appc_ca_adm) 160000 (80)

DpCommTableSize: max/headSize/ftSize/tableSize=2000/16/2208064/2208080

DpShMCreate: sizeof(comm_adm) 2208080 (1088)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm) 0 (104)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1864)

DpShMCreate: sizeof(wall_adm) (416064/346352/64/192)

DpShMCreate: sizeof(gw_adm) 48

• ERROR => DpShMCreate: ShmCreate for key SHM_DP_ADM_KEY failed (4) [dpxxtool2.c 2518]

• ERROR => DpIPCInit2: DpShMCreate [dpxxtool2.c 462]

• DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit2

• DISPATCHER EMERGENCY SHUTDOWN ***

NiWait: sleep (5000ms) ...

NiISelect: timeout 5000ms

NiISelect: maximum fd=1

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Tue Aug 16 08:22:43 2011

NiISelect: TIMEOUT occured (5000ms)

• WARNING => DpHalt: sys_adm has not been initialized! [dpxxdisp.c 10575]

DpHalt: shutdown server >encecpprdci_ECP_02 < (normal)

DpJ2eeDisableRestart

Switch off Shared memory profiling

ShmProtect( 57, 3 )

ShmProtect(SHM_PROFILE, SHM_PROT_RW

ShmProtect( 57, 1 )

ShmProtect(SHM_PROFILE, SHM_PROT_RD

call semaphore clean-up function ...

***LOG Q0E=> DpSigGenHandler, Exception (c0000005) [dpnttool.c 439]

-

---

C-STACK -

---

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=7328)

When : 8/16/2011 8:22:44.452

Threads : 2

-

---

Computer Name : ENCECPPRDCI

User Name : SAPServiceECP

-

---

Number of Processors: 16

Processor Type: EM64T Family 6 Model 29 Stepping 1

Windows Version : 5.2 Current Build: 3790

-

---

State Dump for Thread Id 1a74

--> (FAULT) Stack Back Trace <--

FramePtr ReturnAd Param#1 Function Name

000000000202f2e0 000000014001789a 0000000000001ca0 disp+work!DpVmcCheckDebugProxy [dpxxvmc.c (1263)]

000000000202f400 0000000140019f04 0000000000000001 disp+work!DpHalt [dpxxdisp.c (10846)]

000000000202fc40 000000014001e5ff 00000001422b4258 disp+work!DpFatalErr [dpxxdisp.c (19016)]

000000000202fee0 000000014002ffea 0000000000000000 disp+work!DpSapEnvInit [dpxxdisp.c (1436)]

000000000202ff10 00000001400010a9 ffffffff00000002 disp+work!DpMain [dpxxdisp.c (1117)]

000000000202ff40 000000014163db40 0000000002030000 disp+work!nlsui_main [thxxanf.c (64)]

000000000202ff70 0000000077d596ac 0000000000000000 disp+work!__tmainCRTStartup [crtexe.c (594)]

000000000202ffa0 0000000000000000 00000001400010e0 kernel32!BaseProcessStart

-

---

State Dump for Thread Id dc4

--> Stack Back Trace <--

FramePtr ReturnAd Param#1 Function Name

00000000092bfe10 0000000077d5f6f1 0000000000000510 ntdll!NtFsControlFile

00000000092bfe80 000000014152830f fffffffffffffffe kernel32!ConnectNamedPipe

00000000092bff10 00000000781337d7 00000000023b32f0 disp+work!SigIMsgFunc [signt.c (679)]

00000000092bff40 0000000078133894 00000000781e95c0 MSVCR80!endthreadex

00000000092bff70 0000000077d6b71a 0000000077d6b6e0 MSVCR80!endthreadex

00000000092bffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart

-

---

-

---

Tue Aug 16 08:22:44 2011

call clean-up function ...

SigICallExitRoutine: call exithandler (DpHalt)

• WARNING => DpHalt: sys_adm has not been initialized! [dpxxdisp.c 10575]

DpHalt: shutdown server >encecpprdci_ECP_02 < (normal)

DpJ2eeDisableRestart

Switch off Shared memory profiling

ShmProtect( 57, 3 )

ShmProtect(SHM_PROFILE, SHM_PROT_RW

DpShmPrfSwitch : State already set (OFF)

ShmProtect( 57, 1 )

ShmProtect(SHM_PROFILE, SHM_PROT_RD