Skip to Content
author's profile photo Former Member
Former Member

Dispatcher status yellow after kernel update.

Hi exsperts.

my system SQL2005 on Windows2003.

After updating kernel from 146 to 179 system status in sapmmc turned yellow with info:

dispatcher Runnig but Dialog Queue info unavailable, J2EE:All processes runing.

second issue:

In sapmmc : AS ABAP WP Table is empty.

Any idea what is wrong ?

Below Abap Trace of disp+work.exe

-


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

-


sysno 44

sid ERD

systemid 562 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 179

intno 20050900

make: multithreaded, Unicode, 64 bit, optimized

pid 5332

Sun Oct 26 10:37:29 2008

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

length of sys_adm_ext is 576 bytes

SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (44 5332) http://dpxxdisp.c 1285

shared lib "dw_xml.dll" version 179 successfully loaded

shared lib "dw_xtc.dll" version 179 successfully loaded

shared lib "dw_stl.dll" version 179 successfully loaded

shared lib "dw_gui.dll" version 179 successfully loaded

shared lib "dw_mdm.dll" version 179 successfully loaded

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

use internal message server connection to port 3944

Sun Oct 26 10:37:34 2008

WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings http://dpxxtool2.c 5418

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

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

DpIPCInit2: start server >sap-dev_ERD_44 <

DpShMCreate: sizeof(wp_adm) 28032 (1752)

DpShMCreate: sizeof(tm_adm) 58861440 (29416)

DpShMCreate: sizeof(wp_ca_adm) 80000 (80)

DpShMCreate: sizeof(appc_ca_adm) 160000 (80)

DpCommTableSize: max/headSize/ftSize/tableSize=2000/16/2208064/2208080

DpShMCreate: sizeof(comm_adm) 2208080 (1088)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm) 0 (104)

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

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1864)

DpShMCreate: sizeof(wall_adm) (416064/346352/64/192)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000F020050, size: 62108928)

DpShMCreate: allocated sys_adm at 000000000F020050

DpShMCreate: allocated wp_adm at 000000000F0221F0

DpShMCreate: allocated tm_adm_list at 000000000F028F70

DpShMCreate: allocated tm_adm at 000000000F028FD0

DpShMCreate: allocated wp_ca_adm at 000000001284B750

DpShMCreate: allocated appc_ca_adm at 000000001285EFD0

DpShMCreate: allocated comm_adm at 00000000128860D0

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 0000000012AA1220

DpShMCreate: allocated gw_adm at 0000000012AA12A0

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 0000000012AA12D0

DpShMCreate: allocated wall_adm at 0000000012AA12E0

MBUF state OFF

DpCommInitTable: init table for 2000 entries

rdisp/queue_size_check_value : -> off

ThTaskStatus: rdisp/reset_online_during_debug 0

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> 767 blocks reserved for free list.

ES initialized.

mm.dump: set maximum dump mem to 96 MB

J2EE server info

start = TRUE

state = STARTED

pid = 5888

argv[0] = D:\usr\sap\ERD\DVEBMGS44\exe\jcontrol.EXE

argv[1] = D:\usr\sap\ERD\DVEBMGS44\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\ERD\SYS\profile\ERD_DVEBMGS44_sap-dev

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=64999

argv[5] = -DSAPSYSTEM=44

argv[6] = -DSAPSYSTEMNAME=ERD

argv[7] = -DSAPMYNAME=sap-dev_ERD_44

argv[8] = -DSAPPROFILE=D:\usr\sap\ERD\SYS\profile\ERD_DVEBMGS44_sap-dev

argv[9] = -DFRFC_FALLBACK=ON

argv10 = -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.0 3.0 4.0.1) http://dpxxdisp.c 1692

***LOG Q0K=> DpMsAttach, mscon ( sap-dev) http://dpxxdisp.c 12408

Sun Oct 26 10:37:35 2008

DpStartStopMsg: send start message (myname is >sap-dev_ERD_44 <)

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 60000000 for monitoring segment.

CCMS: Checking Downtime Configuration of Monitoring Segment.

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

DpJ2eeLogin: j2ee state = CONNECTED

DpMsgAdmin: Set release to 7000, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet http://dpxxmbuf.c 1050

DpMsgAdmin: Set patchno for this platform to 179

Release check o.K.

Sun Oct 26 10:38:14 2008

MBUF state ACTIVE

Sun Oct 26 10:38:15 2008

DpModState: change server state from STARTING to ACTIVE

Sun Oct 26 10:40:24 2008

J2EE server info

start = TRUE

state = ACTIVE

pid = 5888

http = 54400

https = 54401

load balance = 1

start_lazy = 0

start_control = SAP J2EE startup framework

Sun Oct 26 13:32:51 2008

SoftCancel request for T22 U508 M0 received from IC_MAN

Sun Oct 26 13:34:56 2008

SoftCancel request for T16 U509 M0 received from IC_MAN

Sun Oct 26 20:59:29 2008

SoftCancel request for T20 U875 M0 received from REMOTE_TERMINAL

Mon Oct 27 07:11:15 2008

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) http://nixxi.cpp 4424

ERROR => NiIRead: SiRecv failed for hdl 7 / sock 260

(SI_ECONN_BROKEN/10054; I4; ST; 172.18.254.229:1902) http://nixxi.cpp 4424

Network error of client T19, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3

Client address of T19 is 172.18.254.229(sap-dev.etos.pl)

***LOG Q04=> DpRTmPrep, NiBufReceive (17761SAPSYS 19 sap-dev ) http://dpxxdisp.c 12086

RM-T19, U17761, 000 SAPSYS, sap-dev, 06:09:33, M0, W0, SESS, 2/0

Mon Oct 27 12:25:13 2008

SoftCancel request for T28 U18469 M1 received from REMOTE_TERMINAL

Mon Oct 27 12:26:07 2008

SoftCancel request for T28 U18469 M0 received from REMOTE_TERMINAL

Mon Oct 27 17:09:37 2008

SoftCancel request for T36 U19479 M0 received from REMOTE_TERMINAL

Mon Oct 27 17:12:41 2008

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) http://nixxi.cpp 4424

ERROR => NiIRead: SiRecv failed for hdl 15 / sock 152

(SI_ECONN_BROKEN/10054; I4; ST; 172.22.17.122:4298) http://nixxi.cpp 4424

Network error of client T22, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3

Mon Oct 27 17:12:42 2008

Client address of T22 is 172.22.17.122(0278-n.etos.pl)

***LOG Q04=> DpRTmPrep, NiBufReceive (19469A.JODKO 22 0278-n ) http://dpxxdisp.c 12086

RM-T22, U19469, 401 A.JODKO, 0278-n, 16:52:23, M0, W1, VF03, 2/1

Mon Oct 27 17:23:29 2008

SoftCancel request for T19 U18317 M0 received from REMOTE_TERMINAL

Mon Oct 27 17:25:58 2008

SoftCancel request for T19 U18317 M0 received from REMOTE_TERMINAL

Tue Oct 28 07:38:37 2008

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) http://nixxi.cpp 4424

ERROR => NiIRead: SiRecv failed for hdl 6 / sock 340

(SI_ECONN_BROKEN/10054; I4; ST; 172.18.254.229:3843) http://nixxi.cpp 4424

Network error of client T17, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3

Client address of T17 is 172.18.254.229(sap-dev.etos.pl)

***LOG Q04=> DpRTmPrep, NiBufReceive (21618SAPSYS 17 sap-dev ) http://dpxxdisp.c 12086

RM-T17, U21618, 000 SAPSYS, sap-dev, 06:36:54, M0, W0, SESS, 2/0

Tue Oct 28 08:55:49 2008

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) http://nixxi.cpp 4424

ERROR => NiIRead: SiRecv failed for hdl 9 / sock 224

(SI_ECONN_BROKEN/10054; I4; ST; 172.20.1.21:1708) http://nixxi.cpp 4424

Network error of client T18, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3

Client address of T18 is 172.20.1.21(0082-d.etos.pl)

***LOG Q04=> DpRTmPrep, NiBufReceive (18414A.KACPERSKA 18 0082-d ) http://dpxxdisp.c 12086

RM-T18, U18414, 401 A.KACPERSKA, 0082-d, 10:15:55, M0, W0, , 2/0

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Oct 29, 2008 at 09:30 AM

    Hello Lukasz,

    Was mmc showing green before the kernel update?..

    if no, you can follow the above note already suggested. some parameter mismatch between start profile and instance profie can cause this.

    if it was green before, and turned yellow immediately after kenel update, then check the sap services by right clicking and properties. it should be running with the sapstartsrv from the sap kernel folder where you updated the latest executable.

    Regards,

    Debasis.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 28, 2008 at 12:01 PM

    Hi,

    Confirm me if you are using SIDADM user id to start the server and also do you have backup of your SAP old Kernel. If you have then please over write your old kernels with new kernels files and start SAP with SIDADM user id. Let me know if your issue get resolved from doing the above step. Also update the error if this is not resolved.

    Regards,

    Satyabrat.

    Edited by: Satyabrat Mohanty on Oct 28, 2008 5:33 PM

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 28, 2008 at 12:19 PM

    follow Note 72248 - NT: Dispatcher in status 'Yellow',SAP system running

    cheers,

    -Sunil

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 29, 2008 at 09:34 AM

    Hi all

    Problem resolved.

    Different versions of sapstartsrv.exe

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 29, 2008 at 09:34 AM

    thx

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.