cancel
Showing results for 
Search instead for 
Did you mean: 

disp+work.EXE (Dispatcher) fails to start

Former Member
0 Kudos

Hi,

We have NW 2004s PI (XI) server. It was running fine for quite a some time ago but suddenly, the disp+work.exe process fails to start. Here is a copy of developer trace:

-


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

-


sysno 01

sid DI1

systemid 560 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 52

intno 20050900

make: multithreaded, Unicode, optimized

pid 4576

Mon Jan 08 15:45:23 2007

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

length of sys_adm_ext is 572 bytes

      • SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (01 4576) [dpxxdisp.c 1231]

shared lib "dw_xml.dll" version 52 successfully loaded

shared lib "dw_xtc.dll" version 52 successfully loaded

shared lib "dw_stl.dll" version 52 successfully loaded

shared lib "dw_gui.dll" version 52 successfully loaded

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

use internal message server connection to port 3901

Mon Jan 08 15:45:28 2007

      • 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 5233]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

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

DpIPCInit2: start server >USMDLSDOWA122_DI1_01 <

DpShMCreate: sizeof(wp_adm) 25344 (1408)

DpShMCreate: sizeof(tm_adm) 3954072 (19672)

DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064

DpShMCreate: sizeof(comm_adm) 528064 (1048)

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

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1452)

DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 06D40040, size: 4620184)

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

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

      • 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

Mon Jan 08 15:45:33 2007

NiISelect: TIMEOUT occured (5000ms)

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

wait for end of work processes

not attached to the message server

cleanup EM

EmCleanup() -> 0

Es2Cleanup: Cleanup ES2

***LOG Q05=> DpHalt, DPStop ( 4576) [dpxxdisp.c 10087]

Good Bye .....

Can anyone help?

Jay

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000D370050, size: 5958768)

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

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

      • DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit2

      • DISPATCHER EMERGENCY SHUTDOWN ***

Check in Task Manager for the process "sapstartsrv.exe", if it is running.These services will not stop, even if you stop the system.Either restart the service by following the below mentioned procedure,

1)Start -> Run

2)services.msc

3)look for "SAP<SID>_<CI INSTANCE NUMBER>" & "SAP<SID>_<SCS INSTANCE NUMBER>"

4)Stop the services.

or kill the process in task manager & again start your system, it should startup

fine.

Any more help, kindly let me know.

Former Member
0 Kudos

Thank you guys, it works

Former Member
0 Kudos

Hi Jay,

Please verify the system date, sometimes reboot will help.

Cheers,

Nagesh....

Former Member
0 Kudos

Since you are running on Wintendo: A reboot often helps when you run into the shared memory issues.

-AD

Former Member
0 Kudos

HI,

There can be 2 reasons:-

1. Memory settings -Check your memory settings for dispatcher and server

2. Ports issue- possible there is port conflict with some other process

Locate your std_server<x>.out file and std_dispatcher.out file. There you may find clue to your problem.

Regards

Bipin Joshi