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.

Similar Messages

  • 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

  • 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;

  • 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

  • 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, 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

  • "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

  • 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

  • Upgrade Prep CHECKSYSSTATS - "Dialog Queue info unavailable"

    During the prep for migration I'm getting an error stating that the system seems to be in an unsound state.
    This can be tested for by running sapcontrol as follows:
    sapcontrol -nr 03 -function GetProcessList
    28.04.2015 00:38:10
    GetProcessList
    OK
    name, description, dispstatus, textstatus, starttime, elapsedtime, pid
    disp+work, Dispatcher, YELLOW, Running but Dialog Queue info unavailable, 2015 04 27 16:05:38, 8:32:32, 1273
    igswd_mt, IGS Watchdog, GREEN, Running, 2015 04 27 16:05:38, 8:32:32, 1274
    I have not seen any system issues, yet the sapcontrol program clearly is having issues.
    I have tested this with both the source kernel (721_REL patch 400) and the target kernel from the SUM directory (742 kernel).
    Both give the same error.
    (NB I've tried the EXT version on the source level too - 721_REL_EXT)
    There is some advise that you can just skip this warning (see 1957443 - Check for system status at upgrade preparation (phase CHECKSYSSTATUS)) - however I would prefer to know what is going on here.
    I've also found a note suggesting that this could be something that happens when you remove a Java stack from a system (we just have); however it refers to J2EE status as opposed to Dialog queue info.. 1855360 - *ERROR:* Your system appears to be in an unsound state. Correct the following issues before you continue: ...J2EE status info unavailable
    I'd be very keen to see if anyone else has seen similar issues with SUM during an upgrade.

    Additionally all.
    Please note I've seen for some people this can be a problem when sapstartsrv isn't up to date with the rest of the kernel (easily possible esp. if you didn't manually kill all SAP processes during kernel updates).
    However I did kill these processes and the binaries all look aligned:
    sapcontrol -nr 03 -function GetVersionInfo
    28.04.2015 09:48:31
    GetVersionInfo
    OK
    Filename, VersionInfo, Time
    /usr/sap/<SID>/DVEBMGS03/exe/sapstartsrv, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 04:14:47), linuxx86_64, 2014 12 11 18:36:31
    /usr/sap/<SID>/DVEBMGS03/exe/disp+work, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 00:03:44), linuxx86_64, 2014 12 11 18:26:54
    /usr/sap/<SID>/DVEBMGS03/exe/gwrd, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 00:03:44), linuxx86_64, 2014 12 06 04:00:56
    /usr/sap/<SID>/DVEBMGS03/exe/msg_server, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:08:17
    /usr/sap/<SID>/DVEBMGS03/exe/dboraslib.so, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 00:03:44), linuxx86_64, 2014 12 05 23:32:49
    /usr/sap/<SID>/DVEBMGS03/exe/dbmssslib.so, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 00:03:44), linuxx86_64, 2014 12 05 23:55:44
    /usr/sap/<SID>/DVEBMGS03/exe/dbdb2slib.so, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 00:03:44), linuxx86_64, 2014 12 05 23:29:38
    /usr/sap/<SID>/DVEBMGS03/exe/dbdb4slib.so, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 00:03:44), linuxx86_64, 2014 12 05 23:31:50
    /usr/sap/<SID>/DVEBMGS03/exe/dbdb6slib.so, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 00:03:44), linuxx86_64, 2014 12 11 18:08:43
    /usr/sap/<SID>/DVEBMGS03/exe/enserver, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:11:52
    /usr/sap/<SID>/DVEBMGS03/exe/icman, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:05:12
    /usr/sap/<SID>/DVEBMGS03/exe/sapwebdisp, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:05:52
    /usr/sap/<SID>/DVEBMGS03/exe/jcontrol, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:27:04
    /usr/sap/<SID>/DVEBMGS03/exe/jlaunch, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:27:13
    /usr/sap/<SID>/DVEBMGS03/exe/jstart, 721, patch 400, changelist 1542873, opt (Dec  6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:25:50

  • Dialog Queue Info Unavailable

    Hi,
    I have  a system with NW2004s BI 7.0 installation
    I upgraded the SAP Kernel from 133 to 146.
    After i start SAP in SAP MMC, i see teh message : Dialog Queue info unavailable"  But the server is running on fine
    I have tried the following
    1. Copied the Latest dispatcher (157 patch), R3trans, tp to the kernel but  then the Dispatcher stops
    2. Restarted the machine
    Please let me the reason for this problem any other solutions for the same
    Edited by: Balaji Rajendran on Jun 16, 2008 9:26 PM

    Hi Balagi,
    Please refer the notes 396309 (Dispatcher remains yellow, although the system is running) and you can try by increase the value of rdisp/elem_per_queue=4000.
    If above two did not help then you need to apply the latest kernel, please refer to the note 19466 further information.
    Regards
    Seshu

  • 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 %)

  • 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

  • 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)

Maybe you are looking for