cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Starting Dispatcher

Former Member
0 Kudos

i have updated the latest kernel patch of 175

i am getting the following error in dispatcher and i am not able ot login to the server

The dispatcher is in yellow colour.

The following is the Developer trace

Pls help me

-


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

-


Wed May 16 18:23:30 2007

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

length of sys_adm_ext is 312 bytes

sysno 00

sid BW3

systemid 560 (PC with Windows NT)

relno 6400

patchlevel 0

patchno 175

intno 20020600

make: multithreaded, ASCII

pid 2420

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

shared lib "dw_xml.dll" version 175 successfully loaded

shared lib "dw_xtc.dll" version 175 successfully loaded

shared lib "dw_stl.dll" version 175 successfully loaded

shared lib "dw_gui.dll" version 175 successfully loaded

shared lib "dw_mdm.dll" version 175 successfully loaded

Wed May 16 18:23:35 2007

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

MtxInit: -2 0 0

DpSysAdmExtInit: ABAP is active

DpIPCInit2: start server >hydhtc74451_BW3_00 <

DpShMCreate: sizeof(wp_adm) 8280 (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: 05950040, size: 2667112)

DpShMCreate: allocated sys_adm at 05950040

DpShMCreate: allocated wp_adm at 059517D8

DpShMCreate: allocated tm_adm_list at 05953830

DpShMCreate: allocated tm_adm at 05953858

DpShMCreate: allocated wp_ca_adm at 05B98898

DpShMCreate: allocated appc_ca_adm at 05B9CEE8

DpShMCreate: allocated comm_adm_list at 05B9E658

DpShMCreate: allocated comm_adm at 05B9E670

DpShMCreate: allocated vmc_adm_list at 05BCD470

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 05BCD498

DpShMCreate: allocated wall_adm at 05BCD4A0

MBUF state OFF

Wed May 16 18:23:36 2007

EmInit: MmSetImplementation( 2 ).

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation flat

<EsNT> Memory Reset disabled as NT default

<ES> 1126 blocks reserved for free list.

ES initialized.

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG Q0K=> DpMsAttach, mscon ( hydhtc74451) [dpxxdisp.c 10051]

Wed May 16 18:23:37 2007

DpStartStopMsg: send start message (myname is >hydhtc74451_BW3_00 <)

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

Wed May 16 18:23:38 2007

CCMS: start to initalize 3.X shared alert area (first segment).

DpMsgAdmin: Set release to 6400, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]

DpMsgAdmin: Set patchno for this platform to 175

Release check o.K.

Wed May 16 18:23:57 2007

MBUF state ACTIVE

Wed May 16 18:23:59 2007

DpModState: change server state from STARTING to ACTIVE

Wed May 16 18:24:01 2007

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Wed May 16 18:24:07 2007

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Wed May 16 18:24:10 2007

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Wed May 16 18:24:15 2007

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Wed May 16 18:24:17 2007

      • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Balaji,

Increase your dispatcher memory thru config tool and tr restarting ur dispatcher.

Thanks

Srinivas

Former Member
0 Kudos

Hi,

check network connection.

check Active network connection ipaddress maintained in the host file,

If you don't have network connection install MS loop back adapter ... and give ip address ,... maintain that ip in the host file ...

Regards

Radha