cancel
Showing results for 
Search instead for 
Did you mean: 

Disp+work Shutdown

Former Member
0 Kudos

Hello,

after a configuration change (parameter ztta/roll_extension) of the instance profile above the profile-manager (rz10) the disp+work are not getting started.

Can anybody help!

Here is a dev-trace.

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

shared lib "dw_xml.dll" version 274 successfully loaded

shared lib "dw_xtc.dll" version 274 successfully loaded

shared lib "dw_stl.dll" version 274 successfully loaded

shared lib "dw_gui.dll" version 274 successfully loaded

shared lib "dw_mdm.dll" version 274 successfully loaded

Tue Jun 15 16:45:33 2010

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

MtxInit: -2 0 0

DpSysAdmExtInit: ABAP is active

DpIPCInit2: start server >SE_TIF_00 <

DpShMCreate: sizeof(wp_adm) 34848 (1452)

DpShMCreate: sizeof(tm_adm) 30783384 (15384)

DpShMCreate: sizeof(wp_ca_adm) 80000 (80)

DpShMCreate: sizeof(appc_ca_adm) 160000 (80)

DpShMCreate: sizeof(comm_adm) 1160000 (580)

DpShMCreate: sizeof(vmc_adm) 0 (424)

DpShMCreate: sizeof(wall_adm) (384056/329560/64/184)

      • ERROR => DpShMCreate: ShmCreate SHM_DP_ADM_KEY [dpxxtool2.c 1586]

      • 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

Tue Jun 15 16:45:38 2010

NiISelect: TIMEOUT occured (5000 ms)

DpHalt: shutdown server >SE_TIF_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 ( 1524) [dpxxdisp.c 9162]

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

the problem is solved.

I followed notes of thread "DISPATCHER EMERGENCY SHUTDOWN".

thx!

marksmyth
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Alexander

Welcome to SDN! I see this is your first post. This is the PI (Process Integration) forum, which deals with PI technical issues only. As this is not a PI technical issue, you will have a better chance of getting a quality response to your query in another forum.

As a result, I will forward this thread to the Netweaver Administrator forum.

Regards

Mark Smyth

XI/PI Moderator

TomCenens
Active Contributor
0 Kudos

Hello Alexander

Did you perform a profile check using sappfpar after adjusting the parameter ?

as <sid>adm

sappfpar pf=<SAP system profile> check

It's possible your memory pool(s) need enlargement after you change memory parameter settings.

The sappfpar check will give error(s) and it will advise neccesary sizing for your pools so the memory setting can be used.

Kind regards

Tom