cancel
Showing results for 
Search instead for 
Did you mean: 

Dispacher stopped

Former Member
0 Kudos

Hi

All SAP Guru's,

We have added two instance profile parameters as follows :

abap/heap_area_dia 2000000

abap/heap_area_nondia 2000000

but after that services could not start and shows DISPATCHER STOPPED in MMC console.

Does those parameter affects to start dispatcher or any other reason....?

Kindly help us , it's urgent

Error in log file as follows:

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

-


Thu Feb 28 16:40:43 2008

kernel runs with dp version 133(ext=102) (@(#) DPLIB-INT-VERSION-133)

length of sys_adm_ext is 312 bytes

sysno 00

sid D01

systemid 560 (PC with Windows NT)

relno 6400

patchlevel 0

patchno 155

intno 20020600

make: multithreaded, ASCII

pid 4088

***LOG Q00=> DpSapEnvInit, DPStart (00 4088) [dpxxdisp.c 1100]

shared lib "dw_xml.dll" version 155 successfully loaded

shared lib "dw_xtc.dll" version 155 successfully loaded

shared lib "dw_stl.dll" version 155 successfully loaded

shared lib "dw_gui.dll" version 155 successfully loaded

shared lib "dw_mdm.dll" version 155 successfully loaded

Thu Feb 28 16:40:48 2008

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

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

MtxInit: -2 0 0

DpSysAdmExtInit: ABAP is active

DpIPCInit2: start server >devsap_D01_00 <

DpShMCreate: sizeof(wp_adm) 17392 (828)

DpShMCreate: sizeof(tm_adm) 2379840 (11840)

DpShMCreate: sizeof(wp_ca_adm) 18000 (60)

DpShMCreate: sizeof(appc_ca_adm) 6000 (60)

DpShMCreate: sizeof(comm_adm) 192000 (384)

DpShMCreate: sizeof(vmc_adm) 0 (364)

DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)

DpShMCreate: SHM_DP_ADM_KEY (addr: 04750040, size: 2676224)

      • ERROR => DpShMCreate: ShmCreate SHM_DP_CA_KEY(rc=4) [dpxxca.c 181]

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

      • DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit2

      • DISPATCHER EMERGENCY SHUTDOWN ***

NiWait: sleep (5000 msecs) ...

NiISelect: timeout 5000 ms

NiISelect: maximum fd=1

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Thu Feb 28 16:40:53 2008

NiISelect: TIMEOUT occured (5000 ms)

DpHalt: shutdown server >devsap_D01_00 < (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

not attached to the message server

***LOG Q05=> DpHalt, DPStop ( 4088) [dpxxdisp.c 8764]

Good Bye .....

Thanks in advance.

Edited by: Navanath Dhavale on Feb 28, 2008 8:03 PM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi,

did u check the sufficiency of shared memory, before changing the buffer memory parameters. it can be checked by command

showipc <instance no>

with regards

Sudha

Edited by: Sudhakaran Srinivasan on Feb 28, 2008 3:44 PM

Former Member
0 Kudos

Thanks u much for your quick responce !

No we haven't check, but can you pls. tell us how to ressolve it .

Regards

Navanath

Answers (1)

Answers (1)

Former Member
0 Kudos

Give us info on ur OS, Database and SAP version.

with regards

Sudha

Former Member
0 Kudos

OS windows 2003

Database : oracle 9i

SAP : R/3 ECC 5

Thanks !!!

Navanath

Former Member
0 Kudos

Hi Navanath Dhavale,

Can you tell why did you added this parameter. Was it recommened by someone or what ?

From where did you received this values.

Can you please try to change this values to 2000000000 and try the same.

Hope it helps you.

Please let know about the outcomes.

Cheers

Deepanshu

Former Member
0 Kudos

Dear All,

Thanks to all whoever had replied to me.

We can remove those parameters on OS level also.

Regards,

Navanath

9867560309