Netweaver 7.02 Trial: Running but Dialog queue standstill

Hi ,
I have installed 7.02 today on my Home Premium Windows 7, 4GB RAM, and Virtual memory is set to 20480MB.
It was working fine till yesterday but suddenly the  management console reveals the reason: disp+work.EXE is "Running but Dialog Queue standstill" .
Please let me know how to resolve this issue.
Thanks
Raj
Edited by: Rkumar21 on Nov 22, 2011 6:21 AM

This is the trace.
trc file: "dev_disp", trc level: 1, release: "720"
sysno      00
sid        NSP
systemid   562 (PC with Windows NT)
relno      7200
patchlevel 0
patchno    46
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile   
Raj\sapmnt\NSP\SYS\profile\NSP_DVEBMGS00_Raj
pid        2504
Mon Nov 21 20:55:29 2011
kernel runs with dp version 125000(ext=118000) (@(#) DPLIB-INT-VERSION-125000-UC)
length of sys_adm_ext is 588 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 2504) [dpxxdisp.c   1252]
     shared lib "dw_xml.dll" version 46 successfully loaded
     shared lib "dw_xtc.dll" version 46 successfully loaded
     shared lib "dw_stl.dll" version 46 successfully loaded
     shared lib "dw_gui.dll" version 46 successfully loaded
     shared lib "dw_mdm.dll" version 46 successfully loaded
     shared lib "dw_rndrt.dll" version 46 successfully loaded
     shared lib "dw_abp.dll" version 46 successfully loaded
     shared lib "dw_sym.dll" version 46 successfully loaded
     shared lib "dw_aci.dll" version 46 successfully loaded
rdisp/softcancel_sequence :  -> 0,5,-1
use internal message server connection to port 3900
rdisp/dynamic_wp_check : 1
rdisp/calculateLoadAverage : 1
Mon Nov 21 20:55:35 2011
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 6 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  6393]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is active
DpIPCInit2: write dp-profile-values into sys_adm_ext
DpIPCInit2: start server >Raj_NSP_00                              <
DpShMCreate: sizeof(wp_adm)          31696     (2264)
DpShMCreate: sizeof(tm_adm)          5517056     (27448)
DpShMCreate: sizeof(wp_ca_adm)          64000     (64)
DpShMCreate: sizeof(appc_ca_adm)     64000     (64)
DpCommTableSize: max/headSize/ftSize/tableSize=500/16/584064/584080
DpShMCreate: sizeof(comm_adm)          584080     (1144)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=512/48/65600/90416/156064
DpShMCreate: sizeof(slock_adm)          156064     (104)
DpFileTableSize: max/headSize/ftSize/tableSize=2800/16/268864/268880
DpShMCreate: sizeof(file_adm)          268880     (80)
DpShMCreate: sizeof(vmc_adm)          30128     (2152)
DpShMCreate: sizeof(wall_adm)          (41664/36752/64/192)
DpShMCreate: sizeof(gw_adm)     48
DpShMCreate: sizeof(j2ee_adm)     3936
DpShMCreate: SHM_DP_ADM_KEY          (addr: 0000000007D60050, size: 6812336)
DpShMCreate: allocated sys_adm at 0000000007D60060
DpShMCreate: allocated wp_adm_list at 0000000007D63030
DpShMCreate: allocated wp_adm at 0000000007D63220
DpShMCreate: allocated tm_adm_list at 0000000007D6AE00
DpShMCreate: allocated tm_adm at 0000000007D6AE50
DpShMCreate: allocated wp_ca_adm at 00000000082ADD60
DpShMCreate: allocated appc_ca_adm at 00000000082BD770
DpShMCreate: allocated comm_adm at 00000000082CD180
DpShMCreate: allocated slock_adm at 000000000835BB20
DpShMCreate: allocated file_adm at 0000000008381CD0
DpShMCreate: allocated vmc_adm_list at 00000000083C3730
DpShMCreate: allocated vmc_adm at 00000000083C37E0
DpShMCreate: allocated gw_adm at 00000000083CADA0
DpShMCreate: allocated j2ee_adm at 00000000083CADE0
DpShMCreate: allocated ca_info at 00000000083CBD50
DpShMCreate: allocated wall_adm at 00000000083CBD70
DpCommAttachTable: attached comm table (header=00000000082CD180/ft=00000000082CD190)
DpSysAdmIntInit: initialize sys_adm
rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
dia token check not active (6 token)
MBUF state OFF
DpCommInitTable: init table for 500 entries
DpFileInitTable: init table for 2800 entries
DpSesCreateTable: created session table at 0000000002CB0050 (len=161328)
DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
<ES> Info: em/initial_size_MB( 3838MB) not multiple of em/blocksize_KB( 4096KB)
<ES> Info: em/initial_size_MB rounded up to 3840MB
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 959 blocks reserved for free list.
ES initialized.
DpVmcSetActive: set vmc state DP_VMC_ENABLED
DpVmcSetActive: set vmc state DP_VMC_ACTIVE
DpVmcInit2: o.k.
MPI: dynamic quotas disabled.
MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
Mon Nov 21 20:55:36 2011
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.4 3.4 4.1) [dpxxdisp.c   1638]
Mon Nov 21 20:55:38 2011
***LOG Q0K=> DpMsAttach, mscon ( Raj) [dpxxdisp.c   12244]
MBUF state LOADING
DpStartStopMsg: send start message (myname is >Raj_NSP_00                              <)
DpStartStopMsg: start msg sent
CCMS uses Shared Memory Key 73 for monitoring.
CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
Mon Nov 21 20:55:39 2011
CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1296]
MBUF state ACTIVE
DpWpBlksLow: max wp blocks in queue is 800 (80 %)
MBUF component UP
DpMsgProcess: 1 server in MBUF
DpAppcBlksLow: max appc blocks in queue is 500 (50 %)

Similar Messages

  • SAPNetweaver TRIAL - 'running but dialog queue standstill'

    Hi!
    I have a problem with Process disp+work.EXE; when i start NSP in SAP Management Console, the Status for this Process is
    'running but dialog queue standstill' and after few minutes 'stopped'.
    Can you please help me ?
    Thanks.
    MY OS : Windows XP 2002 Service Pack 3
    SAP NSP (Netweaver 7.0 ABAP TRIAL)

    Hi!
    I have a problem with Process disp+work.EXE; when i start NSP in SAP Management Console, the Status for this Process is
    'running but dialog queue standstill' and after few minutes 'stopped'.
    Can you please help me ?
    Thanks.
    MY OS : Windows XP 2002 Service Pack 3
    SAP NSP (Netweaver 7.0 ABAP TRIAL)

  • SAP Netweaver ABAP Trial - Running but Dialog Queue standstill

    Dear all,
    since today morning I am having troubles with the SAP Netweaver ABAP Trial version which has run now for over 6 months without any issues. The issues appeared suddenly and I didn't change anything to configuration / network. I am going through the forum now since a couple of hours and I have checked the following. I have read that the most common error is, that the log is full. Anyhow I have checked the log files.
    1.) Logfiles: I can't see anything in the log file saying that something is wrong. Please find enclosed the log files DEV_DISP, DEV_W0 and DEV_MS:
    DEV_DISP:
    trc file: "dev_disp", trc level: 1, release: "720"
    sysno      00
    sid        NSP
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    201
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\mwsrvsap\sapmnt\NSP\SYS\profile\NSP_DVEBMGS00_mwsrvsap
    pid        3112
    Sun Sep 07 12:04:00 2014
    kernel runs with dp version 133000(ext=118000) (@(#) DPLIB-INT-VERSION-133000-UC)
    length of sys_adm_ext is 588 bytes
    *** SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (00 3112) [dpxxdisp.c   1315]
      shared lib "dw_xml.dll" version 201 successfully loaded
      shared lib "dw_xtc.dll" version 201 successfully loaded
      shared lib "dw_stl.dll" version 201 successfully loaded
      shared lib "dw_gui.dll" version 201 successfully loaded
      shared lib "dw_mdm.dll" version 201 successfully loaded
      shared lib "dw_rndrt.dll" version 201 successfully loaded
      shared lib "dw_abp.dll" version 201 successfully loaded
      shared lib "dw_sym.dll" version 201 successfully loaded
      shared lib "dw_aci.dll" version 201 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3900
    rdisp/dynamic_wp_check : 1
    rdisp/calculateLoadAverage : 1
    Sun Sep 07 12:04:04 2014
    *** 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  6423]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    DpIPCInit2: write dp-profile-values into sys_adm_ext
    DpIPCInit2: start server >mwsrvsap_NSP_00                         <
    DpShMCreate: sizeof(wp_adm) 31696 (2264)
    DpShMCreate: sizeof(tm_adm) 5517056 (27448)
    DpShMCreate: sizeof(wp_ca_adm) 64000 (64)
    DpShMCreate: sizeof(appc_ca_adm) 64000 (64)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/16/584064/584080
    DpShMCreate: sizeof(comm_adm) 584080 (1144)
    DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    DpShMCreate: sizeof(slock_adm) 0 (296)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm) 0 (80)
    DpShMCreate: sizeof(vmc_adm) 0 (2152)
    DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)
    DpShMCreate: sizeof(gw_adm) 48
    DpShMCreate: sizeof(j2ee_adm) 3952
    DpShMCreate: SHM_DP_ADM_KEY (addr: 00000000079D0050, size: 6363600)
    DpShMCreate: allocated sys_adm at 00000000079D0060
    DpShMCreate: allocated wp_adm_list at 00000000079D3070
    DpShMCreate: allocated wp_adm at 00000000079D3260
    DpShMCreate: allocated tm_adm_list at 00000000079DAE40
    DpShMCreate: allocated tm_adm at 00000000079DAE90
    DpShMCreate: allocated wp_ca_adm at 0000000007F1DDA0
    DpShMCreate: allocated appc_ca_adm at 0000000007F2D7B0
    DpShMCreate: allocated comm_adm at 0000000007F3D1C0
    DpShMCreate: system runs without slock table
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 0000000007FCBB60
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated gw_adm at 0000000007FCBC10
    DpShMCreate: allocated j2ee_adm at 0000000007FCBC50
    DpShMCreate: allocated ca_info at 0000000007FCCBD0
    DpShMCreate: allocated wall_adm at 0000000007FCCC60
    Sun Sep 07 12:04:05 2014
    DpCommAttachTable: attached comm table (header=0000000007F3D1C0/ft=0000000007F3D1D0)
    DpSysAdmIntInit: initialize sys_adm
    rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
    dia token check not active (6 token)
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
    rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80
    EmInit: MmSetImplementation( 2 ).
    MM global diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> EsILock: use spinlock for locking
    <ES> InitFreeList
    <ES> block size is 4096 kByte.
    <ES> Info: em/initial_size_MB( 8195MB) not multiple of em/blocksize_KB( 4096KB)
    <ES> Info: em/initial_size_MB rounded up to 8196MB
    Using implementation view
    <EsNT> Using memory model view.
    <EsNT> Memory Reset disabled as NT default
    <ES> 2048 blocks reserved for free list.
    ES initialized.
    mm.dump: set maximum dump mem to 96 MB
    DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE
    MPI: dynamic quotas disabled.
    MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG CPS=> DpLoopInit, ICU ( 4.0.1 4.0.1 5.1) [dpxxdisp.c   1701]
    ***LOG Q0K=> DpMsAttach, mscon ( mwsrvsap) [dpxxdisp.c   12467]
    MBUF state LOADING
    DpStartStopMsg: send start message (myname is >mwsrvsap_NSP_00                         <)
    DpStartStopMsg: start msg sent
    CCMS uses Shared Memory Key 73 for monitoring.
    CCMS: Initalized shared memory of size 60000000 for monitoring segment.
    CCMS: Checking Downtime Configuration of Monitoring Segment.
    CCMS: AlMsUpload called by wp 1024.
    Sun Sep 07 12:04:06 2014
    CCMS: AlMsUpload successful for C:\usr\sap\NSP\DVEBMGS00\log\ALMTTREE.DAT (657 MTEs).
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1296]
    MBUF state ACTIVE
    DpWpBlksLow: max wp blocks in queue is 800 (80 %)
    MBUF component UP
    DpMsgProcess: 1 server in MBUF
    DpAppcBlksLow: max appc blocks in queue is 500 (50 %)
    DEV_W0:
    trc file: "dev_w0", trc level: 1, release: "720"
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      all, MJ
    M sysno      00
    M sid        NSP
    M systemid   562 (PC with Windows NT)
    M relno      7200
    M patchlevel 0
    M patchno    201
    M intno      20020600
    M make       multithreaded, Unicode, 64 bit, optimized
    M profile    \\mwsrvsap\sapmnt\NSP\SYS\profile\NSP_DVEBMGS00_mwsrvsap
    M pid        3208
    M
    M  kernel runs with dp version 133000(ext=118000) (@(#) DPLIB-INT-VERSION-133000-UC)
    M  length of sys_adm_ext is 588 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workp. 0 3208) [dpxxdisp.c   1377]
    I  MtxInit: 30000 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    M  DpIPCInit2: read dp-profile-values from sys_adm_ext
    M  DpShMCreate: sizeof(wp_adm) 31696 (2264)
    M  DpShMCreate: sizeof(tm_adm) 5517056 (27448)
    M  DpShMCreate: sizeof(wp_ca_adm) 64000 (64)
    M  DpShMCreate: sizeof(appc_ca_adm) 64000 (64)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=500/16/584064/584080
    M  DpShMCreate: sizeof(comm_adm) 584080 (1144)
    M  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    M  DpShMCreate: sizeof(slock_adm) 0 (296)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm) 0 (80)
    M  DpShMCreate: sizeof(vmc_adm) 0 (2152)
    M  DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)
    M  DpShMCreate: sizeof(gw_adm) 48
    M  DpShMCreate: sizeof(j2ee_adm) 3952
    M  DpShMCreate: SHM_DP_ADM_KEY (addr: 00000000100C0050, size: 6363600)
    M  DpShMCreate: allocated sys_adm at 00000000100C0060
    M  DpShMCreate: allocated wp_adm_list at 00000000100C3070
    M  DpShMCreate: allocated wp_adm at 00000000100C3260
    M  DpShMCreate: allocated tm_adm_list at 00000000100CAE40
    M  DpShMCreate: allocated tm_adm at 00000000100CAE90
    M  DpShMCreate: allocated wp_ca_adm at 000000001060DDA0
    M  DpShMCreate: allocated appc_ca_adm at 000000001061D7B0
    M  DpShMCreate: allocated comm_adm at 000000001062D1C0
    M  DpShMCreate: system runs without slock table
    M  DpShMCreate: system runs without file table
    M  DpShMCreate: allocated vmc_adm_list at 00000000106BBB60
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated gw_adm at 00000000106BBC10
    M  DpShMCreate: allocated j2ee_adm at 00000000106BBC50
    M  DpShMCreate: allocated ca_info at 00000000106BCBD0
    M  DpShMCreate: allocated wall_adm at 00000000106BCC60
    M  DpCommAttachTable: attached comm table (header=000000001062D1C0/ft=000000001062D1D0)
    M  DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 from sys_adm
    M
    M Sun Sep 07 12:04:06 2014
    M  rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  <ES> EsILock: use spinlock for locking
    X  Using implementation view
    X  <EsNT> Using memory model view.
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.
    X  mm.dump: set maximum dump mem to 96 MB
    M  DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE
    M  ThStart: taskhandler started
    M  ThInit: initializing DIA work process W0
    M
    M Sun Sep 07 12:04:08 2014
    M  ThInit: running on host mwsrvsap
    M
    M Sun Sep 07 12:04:10 2014
    M  calling db_connect ...
    B  Loading DB library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' ...
    B  Library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' loaded
    B  Version of 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' is "720.00", patchlevel (0.201)
    C
    C  DBSDBSLIB : version 720.00, patch 0.201 (Make PL 0.201)
    C  MAXDB shared library (dbsdbslib) patchlevels (last 10)
    C    (0.201) Take care of warnings during database connect (note 1600066)
    C    (0.117) Define a primary key on the temp tables for R3szchk (note 1606260)
    C    (0.114) Support of MaxDB 7.8 and 7.9 (note 1653058)
    C    (0.103) Close all lob locators at end of the transaction (note 1626591)
    C    (0.101) Fix for unknown table __TABLE_SIZES_ (R3szchk) (note 1619504)
    C    (0.098) Use filesystem counter for R3szchk (note 1606260)
    C    (0.092) Secondary connection to HANA (note 1481256)
    C    (0.089) UPDSTAT with SAPSYSTEMNAME longer as 3 characters (note 1584921)
    C    (0.081) No UPSERT on WBCROSSGT (note 1521468)
    C    (0.080) New feature batch streaming (note 1340617)
    C
    C
    C  Loading SQLDBC client runtime ...
    C  SQLDBC Module  : C:\sapdb\clients\NSP\pgm\libSQLDBC77.dll
    C  SQLDBC SDK     : SQLDBC.H  7.9.7    BUILD 010-123-243-190
    C  SQLDBC Runtime : libSQLDBC 7.9.7    BUILD 010-123-243-190
    C  SQLDBC client runtime is MaxDB 7.9.7.010 CL 243190
    C  SQLDBC supports new DECIMAL interface : 1
    C  SQLDBC supports VARIABLE INPUT data   : 1
    C  SQLDBC supports VARIABLE OUTPUT data  : 1
    C  SQLDBC supports Multiple Streams      : 1
    C  SQLDBC supports LOB LOCATOR KEEPALIVE : 1
    C  SQLDBC supports LOB LOCATOR COPY      : 1
    C  SQLDBC supports BULK SELECT with LOBS : 1
    C  SQLDBC supports BATCH STREAM          : 1
    C  INFO : SQLOPT= -I 0 -t 0 -S SAPR3
    C  Try to connect (DEFAULT) on connection 0 ...
    C  Attach to SAP DB : Kernel    7.9.07   Build 010-123-243-190
    C  Database release is SAP DB 7.9.07.010
    C  INFO : Database 'NSP' instance is running on 'mwsrvsap'
    C  DB supports UPSERT SQL syntax : 1
    C  DB supports new EXPAND syntax : 1
    C  DB supports LOB locators      : 1
    C  DB uses MVCC support          : 0
    C  DB max. input host variables  : 2000
    C  DB max. statement length      : 65535
    C  UPSERT is disabled for : WBCROSSGT
    C  INFO : SAP DB Packet_Size = 131072
    C  INFO : SAP DB Min_Reply_Size = 4096
    C  INFO : SAP DB Comm_Size = 126976
    C  INFO : DBSL buffer size = 126976
    C  INFO : SAP DB MaxLocks = 300000
    C  INFO : Connect to DB as 'SAPNSP'
    C  Command info enabled
    C  Now I'm connected to MaxDB
    C  00: mwsrvsap-NSP, since=20140907120410, ABAP= <unknown> (0)
    B  Connection 0 opened (DBSL handle 0)
    C  INFO : SAP RELEASE (DB) = 731
    M  ThInit: db_connect o.k.
    M
    M Sun Sep 07 12:04:11 2014
    M  ICT: exclude compression: *.zip,*.rar,*.arj,*.z,*.gz,*.tar,*.lzh,*.cab,*.hqx,*.ace,*.jar,*.ear,*.war,*.css,*.pdf,*.gzip,*.uue,*.bz2,*.iso,*.sda,*.sar,*.gif,*.png,*.swc,*.swf
    DEV_MS:
    trc file: "dev_ms", trc level: 1, release: "720"
    [Thr 3092] Sun Sep 07 12:03:56 2014
    [Thr 3092] ms/http_max_clients = 500 -> 500
    [Thr 3092] MsSSetTrcLog: trc logging active, max size = 52428800 bytes
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    101
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    pid        3088
    [Thr 3092] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 3088) [msxxserv.c   2278]
    [Thr 3092] load acl file = C:\usr\sap\NSP\SYS\global\ms_acl_info.DAT
    [Thr 3092] MsGetOwnIpAddr: my host addresses are :
    [Thr 3092]   1 : [10.0.0.225] mwsrvsap.local (HOSTNAME)
    [Thr 3092]   2 : [127.0.0.1] mwsrvsap (LOCALHOST)
    [Thr 3092]   3 : [10.10.0.10] mwsrvsap (NILIST)
    [Thr 3092] MsHttpInit: full qualified hostname = mwsrvsap
    [Thr 3092] HTTP logging is switch off
    [Thr 3092] set HTTP state to LISTEN
    [Thr 3092] *** HTTP port 8100 state LISTEN ***
    [Thr 3092] *** I listen to internal port 3900 (3900) ***
    [Thr 3092] *** HTTP port 8100 state LISTEN ***
    [Thr 3092] CUSTOMER KEY: >V1901974459<
    [Thr 3092] build version=720.2011.10.26
    2.) So I installed the SAP MaxDB Database Manager in order to check the logs and do an archiving. But here seems to be the issue - I can not see the NSP Database instance (see attached screenshot). But how can this be? The log file say that the db connection is ok?
    3.) What is really strange to me is the Syslog in the management console --> see log3.png. Why does it say work process in reconnect status?
    Does anybody have an idea how to solve this issue? Help is really appreciated and points will be rewarded.
    Best regards
    Maik

    Thank you first of all for your answer.
    I tried to do so, but in the MaxDB Database Manager I can add the db instance, but I am not able to connect to it (service is running).

  • Disp+work goes yellow with message:  running but dialog queue standstill

    I just installed CRM 7.0 on Windows with MaxDB 7.7.04 build 28. After the installation I was able to logon and begin applying support packs. In the middle of doing this, the system hung and I noticed the disp+work went yellow with the message "Running but dialog queue standstill". I shut down the system, rebooted the machine and started up again. The same error is occuring. Here are some log files:
    adatmp:
    Error! Connection failed to node sitaserv23 for database CRE:
    -24700,ERR_DBMSRV_NOSTART: Could not start DBM server.
    -24832,ERR_SHMNOTAVAILABLE: Shared memory not available
    -24827,ERR_SHMALLOCFAILED: ID C:\sapdb\data\wrk\CRE.dbm.shi, requested size 2600
    stderr1:
    C:\usr\sap\CRE\DVEBMGS02\work>set DBNAME=CRE
    C:\usr\sap\CRE\DVEBMGS02\work>set DBNAME=CRE
    C:\usr\sap\CRE\DVEBMGS02\work>if "" == "" (set DB_USERKEY="c" ) else (set DB_USERKEY="c_J2EE" )
    C:\usr\sap\CRE\DVEBMGS02\work>dbmcli -U "c" db_state 1>adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "ONLINE" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>dbmcli -U "c" dbm_version VERSION 1>adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.2" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.3" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.4" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.5" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.6" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.7" adatmp
    Error: Database CRE NOT started !
    I tried applying note 1041650 but this seems to be for UNIX. I don't know how to clear memory in Windows 2003 server.
    I updated the kernel to 117 with disp+work at 130. Still the same.
    Please help.
    Thanks,
    Peggy

    Here is the result
    db_state
    OK
    ONLINE
    x_cons <SID> sh ac
    SERVERDB: CRE
    ID   UKT  Win   TASK       APPL Current         Timeout Region     Wait
              tid   type        pid state          priority cnt try    item
    T113   8  0x8F0 User        956 LOG FULL (246) !      0 0               11514(s)
    So I can see that it is full.  What can I do to increase the size and/or turn off logging?
    Thanks!

  • Disp+work goes yellow with:  Running but dialog queue standstill

    I just installed CRM 7.0 on Windows with MaxDB 7.7.04 build 28.  After the installation I was able to logon and begin applying support packs.  In the middle of doing this, the system hung and I noticed the disp+work went yellow with the message "Running but dialog queue standstill".  I shut down the system, rebooted the machine and started up again.  The same error is occuring.  Here are some log files:
    adatmp:
    Error! Connection failed to node sitaserv23 for database CRE:
    -24700,ERR_DBMSRV_NOSTART: Could not start DBM server.
    -24832,ERR_SHMNOTAVAILABLE: Shared memory not available
    -24827,ERR_SHMALLOCFAILED: ID C:\sapdb\data\wrk\CRE.dbm.shi, requested size 2600
    stderr1:
    C:\usr\sap\CRE\DVEBMGS02\work>set DBNAME=CRE
    C:\usr\sap\CRE\DVEBMGS02\work>set DBNAME=CRE
    C:\usr\sap\CRE\DVEBMGS02\work>if "" == "" (set DB_USERKEY="c" )  else (set DB_USERKEY="c_J2EE" )
    C:\usr\sap\CRE\DVEBMGS02\work>dbmcli -U "c" db_state  1>adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "ONLINE" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>dbmcli -U "c"  dbm_version VERSION   1>adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.2" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.3" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.4" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.5" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.6" adatmp
    C:\usr\sap\CRE\DVEBMGS02\work>findstr "7\.7" adatmp
    Error: Database CRE NOT started !
    I tried applying note 1041650 but this seems to be for UNIX.  I don't know how to clear memory in Windows 2003 server.
    I updated the kernel to 117 with disp+work at 130.  Still the same.
    Please help.
    Thanks,
    Peggy

    Hi,
    Its better to put log archive in over write mode while installation to avoid these issues.
    Regards,
    Sahil Garg

  • Disp+work.exe - Running but dialog queue statistics unavailable

    Hi,
    We have two diferent instances in the same machine. One on them have disp+work.exe in yellow and show message "Running but dialog queue statistics unabailable". This is right, the queue statistics have no item to show, but I can login perfectly in sapgui and see the processes in tx sm50.
    Where sapmmc read from? Instance profiles? Any other file?
    Thanks for all.

    Yes, problem solved.
    I stopped windows instance service and overwrote the exe.
    Thanks for all again

  • Running but Dialog Queue info unavailable, J2EE: All processes running

    Dear SAP,
    I have start my SAP Solution Manager system. I can login.
    But the process disp+work.exe is in warning (yellow).
    I do have this warning :
    Running but Dialog Queue info unavailable, J2EE: All processes running
    Content of my dev_disp file :
    ================================================================================================
    Thu Sep 09 12:36:13 2010
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4436]
    ERROR => NiIRead: SiRecv failed for hdl 7 / sock 1308
        (SI_ECONN_BROKEN/10054; I4; ST; 192.168.110.71:53609) [nixxi.cpp    4436]
    Network error of client T27, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
    Client address of T27 is 192.168.110.71(neo-l011.lia.local)
    ***LOG Q04=> DpRTmPrep, NiBufReceive (28 BUEHLER 27 lia-l011 ) [dpxxdisp.c   12238]
    RM-T27, U28, 100     BUEHLER , lia-l011, 11:55:32, M1, W1, DSWP, 3/1
    Thu Sep 09 14:07:57 2010
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4436]
    ERROR => NiIRead: SiRecv failed for hdl 7 / sock 1308
        (SI_ECONN_BROKEN/10054; I4; ST; 192.168.110.71:55886) [nixxi.cpp    4436]
    Network error of client T31, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
    Client address of T31 is 192.168.110.71(neo-l011.lia.local)
    ***LOG Q04=> DpRTmPrep, NiBufReceive (1967 31 lia-l011 ) [dpxxdisp.c   12238]
    RM-T31, U1967, 000             , lia-l011, 14:07:54, M0, W0, SESS, 2/0
    Thu Sep 09 16:47:41 2010
    DpHdlDeadWp: restart wp (pid=9220) automatically
    ================================================================================================
    Thanks
    Best regards
    NetAdmin

    Dear SAP,
    It was a kernel problem.
    Best regards

  • Dispatcher is running but dialog queue info unavailable

    R/S All,
    My production system has been recovered after a Windows O.S. crash. SAP application gets started & we are able to
    access the database through T-codes. But at SAP mmt I am gettting "dialog queue info unabailable" in yellow colour with Dispatch (dispwork.exe). My server config. is Win2k3IBMdb2_v.9.1 + ECC 6.0.
    Kindly guide me to reslove this.

    Hi,
    Kindly check through the below links where the same issue has been resolved. Also, kindly if any windows pacthes have been installed during the process of restoration. Update the kernel to the latest level for all i.e. after updating the kernel (DB and DB independent files) update the other latest files also (like R3trans, tp, dw* etc,,)
       disp+work.EXE (Dispatcher) - Running but Dialog Queue info unavailable,...
       Dispatcher  status: Running but dialog queue info unavailable ... yellow co
       Dispatcher - Running but Dialog Queue info unavailable
    Also, please provide the dev_disp log here.
    Regards,
    Sharath Babu M

  • Dispatcher  status: Running but dialog queue info unavailable ... yellow co

    Hi there,
    I just upgraded a SAP Kernel from:
    Old Kernel:  disp+work information
    kernel release                640
    kernel make variant           640_REL
    compiled on                   NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00
    compiled for                  64 BIT
    compilation mode              Non-Unicode
    compile time                  Aug 16 2007 21:11:21
    update level                  0
    patch number                  196
    source id                     0.196
    New Kernel:    disp+work information
    kernel release                640
    kernel make variant           640_REL
    compiled on                   NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00 for "
    NTAMD64"
    compiled for                  64 BIT
    compilation mode              Non-Unicode
    compile time                  Oct 10 2010 21:35:45
    update level                  0
    patch number                  350
    source id                     0.350
    I downloaded the files:
    SAPEXE_347-20001176.SAR
    SAPEXEDB_347-20001172.SAR
    And I extracted them and copied all files to  ...usr\sap\SID\SYS\exe\run and to ...usr\sap\SID\SYS
    exe\nuc\NTAMD64
    But the Dispatcher has the yellow status with the message: Running but dialog queue info unavailable.
    Any Idea?
    Thanks in advance.
    HanseAtik

    Hi,
    I just found out that it works fine now and want to share this with you:
    The solution is:
    I downloaded and extracted the file: dw_350-20001176.sar and copied everything to exe\run and ..exe\nuc\NTADM64.
    I am happy now and evey thing is green and the business must go on. I hope this will help other too...
    Best regards
    Hanseatik

  • PI -Dispatcher - Running but Dialog Queue info unavailable

    Hi,
    In our PI dev server,
    1) We are observing the below warning..
    "Dispatcher - Running but Dialog Queue info unavailable"
    The dispatcher seems to running as well as the system is functioning properly.
    But sometimes we get Java heap size exceeding error. Also the Maintenence_ORA certificate has expired.
    2) Also we have observed the below error during cache refresh
    "Failed to read sld instance name"
    I went through some of the blogs and got to know that Kernel upgrade could be one of the solutions to point 1.
    But our PI server is already 7.1 EHP 1 and at patch level 135. (N-1 available in marketplace).
    Also let me know how relevant Maintenence_ORA certificate is ?
    Kindly suggest solutions for points 1 and 2.

    hi Prit,
    If your PI is a NT server you can read the note Note 72248 - NT: Dispatcher in status 'Yellow',SAP system running.
    kind regards.

  • Running but dialog queue info unavailable,j2ee status info unavailable

    HI ,
    We have a solution manager instance.It has both java and abap.  The problem now is     The dispatcher in the processlist    is displaying the error  "  the instance is running but dialog queue info unavailable,j2ee status info unavailable "    and the instance status is staying in yellow color.
    Guys anyone can suggest me regarding this issue..
    Thanks in advance,
    Chandana.

    Hi,
    Please check whether user id SAPJSF is locked or not. If it is not locked the please check below trace files  dev_dispatcher,std_server#.out,dev_jcontrol,std_dispatcher.out.
    Also refer SAP note 723909 - Java VM settings for J2EE 6.40/7.0
    Below thread may help you.
    J2EE status info unavailable
    Thanks,
    Sushil

  • Running but Dialog Queue info unavailable

    Hi friends,
      I installed ECC 5.0 on server2003(sql server).But now when disp+work.exe is started,this message is thrown out in MMC:"Running but Dialog Queue info unavailable".
      Although this message appear,I still can logon ECC.
      Below is developer trace in MMC for disp+work.exe:
    <i>----
    trc file: "dev_disp", trc level: 1, release: "640"
    Tue May 09 06:34:12 2006
    kernel runs with dp version 128(ext=102) (@(#) DPLIB-INT-VERSION-128)
    length of sys_adm_ext is 312 bytes
    systemid   560 (PC with Windows NT)
    relno      6400
    patchlevel 0
    patchno    43
    intno      20020600
    make:      multithreaded, ASCII
    pid        192
    ***LOG Q00=> DpSapEnvInit, DPStart (00 192) [dpxxdisp.c   1100]
         shared lib "dw_xml.dll" version 43 successfully loaded
         shared lib "dw_xtc.dll" version 43 successfully loaded
         shared lib "dw_stl.dll" version 43 successfully loaded
         shared lib "dw_gui.dll" version 43 successfully loaded
    Tue May 09 06:34:17 2006
    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  3886]
    MtxInit: -2 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: JAVA is not active
    DpShMCreate: sizeof(wp_adm)          6624     (828)
    DpShMCreate: sizeof(tm_adm)          2219848     (11044)
    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     (320)
    DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 03D10040, size: 2505416)
    DpShMCreate: allocated sys_adm at 03D10040
    DpShMCreate: allocated wp_adm at 03D117A8
    DpShMCreate: allocated tm_adm_list at 03D13188
    DpShMCreate: allocated tm_adm at 03D131B0
    DpShMCreate: allocated wp_ca_adm at 03F310F8
    DpShMCreate: allocated appc_ca_adm at 03F35748
    DpShMCreate: allocated comm_adm_list at 03F36EB8
    DpShMCreate: allocated comm_adm at 03F36ED0
    DpShMCreate: allocated vmc_adm_list at 03F65CD0
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 03F65CF8
    DpShMCreate: allocated wall_adm at 03F65D00
    MBUF state OFF
    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.
    Tue May 09 06:34:19 2006
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG Q0K=> DpMsAttach, mscon ( sheccsrv) [dpxxdisp.c   9736]
    Tue May 09 06:34:20 2006
    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 43
    Release check o.K.
    Tue May 09 06:34:35 2006
    MBUF state ACTIVE
    Tue May 09 06:34:36 2006
    DpModState: change server state from STARTING to ACTIVE
    </i>
    If anybody can solve this problem,I will be very thankful.

    OSS Note 72248
    Because the SAP service delivered with SAP MMC Snap-In draws considerably more information from the R/3 kernel currently running, identical information regarding various parameters must be available to both the SAP service as well as the R/3 kernel.Because the SAP service only reads the SAP start and default profile, the value changed in the instance profile for 'rdisp/elem_per_queue' cannot be recognized.
    Set 'rdisp/elem_per_queue' with identical value in the start profile too or make sure that this is set.
    You can check the value in ECC with transaction rz11 and look for 'rdisp/elem_per_queue'.
    With the right mouse button, click on the name of the machine in SAP MMC Snap-In and there select 'All tasks--> Restart service'.After a while, the dispatcher switches to the 'Green' status.

  • Running but Dialog Queue info unavailable  - In MMC- CKernel 700 -  SuPK133

    Hi All
    I have reciently upgraded our ECC Kernel to the latest version (SP 133) and now in the SAP MMC the status is yellow and I am getting the following message:
    Running but Dialog Queue info unavailable
    HAs anyone seen this or know how to fix it?
    Thanks in advance
    Phil

    Sorted:
    See this [Dispatcher - Running but Dialog Queue info unavailable;

  • "Running but Dialog Queue info unavailable"  with MMC "yellow" status

    after I update my SCM server's WAS 620 kernel patch to 1271,this error apears in MMC disp+work.
    and I have check notes ,find note "72248"
    but after follow the note, and add the parameter"rdisp/elem_per_queue"=2000 (default vealue) in profile ,the note do not work.
    Any idea?someone
    Best Regards

    I download latest kernel patch 1773, problem solved

  • Dialog queue Standstill after applying Java Initial configuration

    Hi All,
    I am installing NW 7.11 PI and after running Java Initial configuration with j2ee_admin user  the system is not starting anymore.
    On SAP MMC I notice the "message server connected ok"  message and java process is starting.
    Then it stops and I see message "Dialog queue standstill" and the system stops.
    I can start oracle without issues but when I run R3trans -d I get Ora 1017 error.
    I checked all notes regarding this error (400241, 1410573, etc) but no luck. I can connect to orace using  sapsr3/<password>/@<SID> without issues.  But on trans.log file I see the message that OPS$ can not connect even if I reset the password to default "sap".
    It seems to me that tje problem is related to some issue with the Java instance but am not sure.
    Please can any body help me out ?
    Thanks and best regards,
    Joao

    Hi Pranay,
    In fact not. The abap instance is also stopped. BTW, it is on Windows 2008 and oracle 11.2.
    When I stat the instances on sapmmc, i see on process list the disp+work.exe running, the message server connection ok and it tries to start the AS Java. Then I got that message "Dialog queue standstill"and then it stops.
    I can not attach the complete dev_disp and dev_server0 files because they are too long.
    See part of the dev_disp  below.
    I will send the dev_server0 in another query.
    thanks very much for your help.
    Mauricio
    DEV_DISP:
    trc file: "dev_disp", trc level: 1, release: "711"
    sysno      01
    sid        DPC
    systemid   562 (PC with Windows NT)
    relno      7110
    patchlevel 0
    patchno    135
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    F:\usr\sap\DPC\SYS\profile\DPC_DVEBMGS01_fordnc01
    pid        2772
    Thu Aug 11 09:16:58 2011
    kernel runs with dp version 120000(ext=118000) (@(#) DPLIB-INT-VERSION-120000-UC)
    length of sys_adm_ext is 584 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (01 2772) [dpxxdisp.c   1261]
         shared lib "dw_xml.dll" version 135 successfully loaded
         shared lib "dw_xtc.dll" version 135 successfully loaded
         shared lib "dw_stl.dll" version 135 successfully loaded
         shared lib "dw_gui.dll" version 135 successfully loaded
         shared lib "dw_mdm.dll" version 135 successfully loaded
         shared lib "dw_rndrt.dll" version 135 successfully loaded
         shared lib "dw_abp.dll" version 135 successfully loaded
         shared lib "dw_sym.dll" version 135 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3901
    rdisp/dynamic_wp_check : 1
    rdisp/calculateLoadAverage : 1
    Thu Aug 11 09:17:03 2011
    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  6388]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is active
    DpIPCInit2: write dp-profile-values into sys_adm_ext
    DpIPCInit2: start server >fordnc01_DPC_01                         <
    DpShMCreate: sizeof(wp_adm)          42864     (2256)
    DpShMCreate: sizeof(tm_adm)          5796848     (28840)
    DpShMCreate: sizeof(wp_ca_adm)          64000     (64)
    DpShMCreate: sizeof(appc_ca_adm)     64000     (64)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/16/584064/584080
    DpShMCreate: sizeof(comm_adm)          584080     (1144)
    DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=512/48/65600/90416/156064
    DpShMCreate: sizeof(slock_adm)          156064     (104)
    DpFileTableSize: max/headSize/ftSize/tableSize=3800/16/364864/364880
    DpShMCreate: sizeof(file_adm)          364880     (80)
    DpShMCreate: sizeof(vmc_adm)          40896     (2152)
    DpShMCreate: sizeof(wall_adm)          (41664/36752/64/192)
    DpShMCreate: sizeof(gw_adm)     48
    DpShMCreate: sizeof(j2ee_adm)     3936
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 000000000C030050, size: 7210208)
    DpShMCreate: allocated sys_adm at 000000000C030060
    DpShMCreate: allocated wp_adm_list at 000000000C0330C0
    DpShMCreate: allocated wp_adm at 000000000C0332B0
    DpShMCreate: allocated tm_adm_list at 000000000C03DA30
    DpShMCreate: allocated tm_adm at 000000000C03DA80
    DpShMCreate: allocated wp_ca_adm at 000000000C5C4E80
    DpShMCreate: allocated appc_ca_adm at 000000000C5D4890
    DpShMCreate: allocated comm_adm at 000000000C5E42A0
    DpShMCreate: allocated slock_adm at 000000000C672C40
    DpShMCreate: allocated file_adm at 000000000C698DF0
    DpShMCreate: allocated vmc_adm_list at 000000000C6F1F50
    DpShMCreate: allocated vmc_adm at 000000000C6F2000
    DpShMCreate: allocated gw_adm at 000000000C6FBFD0
    DpShMCreate: allocated j2ee_adm at 000000000C6FC010
    DpShMCreate: allocated ca_info at 000000000C6FCF80
    DpShMCreate: allocated wall_adm at 000000000C6FCFA0
    DpCommAttachTable: attached comm table (header=000000000C5E42A0/ft=000000000C5E42B0)
    DpSysAdmIntInit: initialize sys_adm
    rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
    dia token check not active (10 token)
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    DpFileInitTable: init table for 3800 entries
    DpSesCreateTable: created session table at 0000000002E10050 (len=161328)
    DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
    rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80
    EmInit: MmSetImplementation( 2 ).
    MM global diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 4096 kByte.
    Using implementation view
    <EsNT> Using memory model view.
    <EsNT> Memory Reset disabled as NT default
    <ES> 2999 blocks reserved for free list.
    ES initialized.
    Thu Aug 11 09:17:04 2011
    Es2ResCreate: Changed resource parameters to
         filenamePrefix =
         blockSizeKB    = 1024 KB
         initialSizeMB  = 240 MB
         extendSizeMB   = 120 MB
         maxSizeMB      = 5640 MB
    DpVmcSetActive: set vmc state DP_VMC_ENABLED
    DpVmcSetActive: set vmc state DP_VMC_ACTIVE
    DpVmcInit2: o.k.
    MPI: dynamic quotas disabled.
    MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 1388
      argv[0] = F:\usr\sap\DPC\DVEBMGS01\exe\jstart.EXE
      argv[1] = F:\usr\sap\DPC\DVEBMGS01\exe\jstart.EXE
      argv[2] = pf=F:\usr\sap\DPC\SYS\profile\DPC_DVEBMGS01_fordnc01
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=65000
      argv[5] = -DSAPSYSTEM=01
      argv[6] = -DSAPSYSTEMNAME=DPC
      argv[7] = -DSAPMYNAME=fordnc01_DPC_01
      argv[8] = -DSAPPROFILE=F:\usr\sap\DPC\SYS\profile\DPC_DVEBMGS01_fordnc01
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG CPS=> DpLoopInit, ICU ( 3.4 3.4 4.1) [dpxxdisp.c   1648]
    ***LOG Q0K=> DpMsAttach, mscon ( fordnc01) [dpxxdisp.c   12436]
    MBUF state LOADING
    DpStartStopMsg: send start message (myname is >fordnc01_DPC_01                         <)
    DpStartStopMsg: start msg sent
    CCMS uses Shared Memory Key 73 for monitoring.
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    Thu Aug 11 09:17:05 2011
    CCMS: Initalized shared memory of size 60000000 for monitoring segment.
    CCMS: Checking Downtime Configuration of Monitoring Segment.
    CCMS: AlMsUpload called by wp 1024.
    CCMS: AlMsUpload successful for F:\usr\sap\DPC\DVEBMGS01\log\ALMTTREE.DAT (1495 MTEs).
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpJ2eeLogin: j2ee state = CONNECTED
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1295]
    MBUF state ACTIVE
    DpWpBlksLow: max wp blocks in queue is 800 (80 %)
    MBUF component UP
    DpMsgProcess: 1 server in MBUF
    DpAppcBlksLow: max appc blocks in queue is 500 (50 %)
    Thu Aug 11 09:17:44 2011
    ERROR => DpHdlDeadWp: W0 (pid 4588) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W1 (pid 3296) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W2 (pid 4116) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W3 (pid 3240) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W4 (pid 4576) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W5 (pid 4456) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W6 (pid 3684) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W7 (pid 3540) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W8 (pid 3304) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W9 (pid 4068) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W10 (pid 3432) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W11 (pid 4952) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W12 (pid 4944) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W13 (pid 3588) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W14 (pid 4956) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W15 (pid 4044) died (severity=0, status=0) [dpxxwp.c     1548]
    ERROR => DpHdlDeadWp: W16 (pid 2096) died (severity=0, status=0) [dpxxwp.c     1548]
    DP_FATAL_ERROR => DpWPCheck: no more work processes
    DISPATCHER EMERGENCY SHUTDOWN ***
    increase tracelevel of WPs
    NiWait: sleep (10000ms) ...
    NiISelect: timeout 10000ms
    NiISelect: maximum fd=1297
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Thu Aug 11 09:17:54 2011
    NiISelect: TIMEOUT occured (10000ms)
    dump system status
    Workprocess Table (long)               Thu Aug 11 12:17:54 2011
    ========================
    Number of work processes:     17
    ========================
    No  Type      Pid    Status  Cause Start Rstr  Err Sem Time Program          Cl  User         Action                    Table
      0 DIA            -1 Ended         no    no     1   0    0                                                                       
      1 DIA            -1 Ended         no    no     1   0    0                                                                       
      2 DIA            -1 Ended         no    no     1   0    0                                                                       
      3 DIA            -1 Ended         no    no     1   0    0                                                                       
      4 DIA            -1 Ended         no    no     1   0    0                                                                       
      5 DIA            -1 Ended         no    no     1   0    0                                                                       
      6 DIA            -1 Ended         no    no     1   0    0                                                                       
      7 DIA            -1 Ended         no    no     1   0    0                                                                       
      8 DIA            -1 Ended         no    no     1   0    0                                                                       
      9 DIA            -1 Ended         no    no     1   0    0                                                                       
    10 UPD            -1 Ended         no    no     1   0    0                                                                       
    11 ENQ            -1 Ended         no    no     1   0    0                                                                       
    12 BTC            -1 Ended         no    no     1   0    0                                                                       
    13 BTC            -1 Ended         no    no     1   0    0                                                                       
    14 BTC            -1 Ended         no    no     1   0    0                                                                       
    15 SPO            -1 Ended         no    no     1   0    0                                                                       
    16 UP2            -1 Ended         no    no     1   0    0                                                                       
    Dispatcher Queue Statistics               Thu Aug 11 12:17:54 2011
    ===========================

Maybe you are looking for