Disp+work in Yellow flag (Win 2003; MaxDB; NW2004s, BI-ABAP+Java)

[Former Member]

Hi Gurus,

We have Win 2003, MaxDB in NW2004s with BI-ABAP+Java.

When we tried to start SAP via MMC, disp+work in Yellow flag . Can anyone tell how to move forward.

Please find error below:

-

---

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

-

---

sysno 01

sid BI1

systemid 560 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 52

intno 20050900

make: multithreaded, Unicode, optimized

pid 3684

Tue Dec 12 13:51:40 2006

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

length of sys_adm_ext is 572 bytes

• SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (01 3684) [dpxxdisp.c 1231]

shared lib "dw_xml.dll" version 52 successfully loaded

shared lib "dw_xtc.dll" version 52 successfully loaded

shared lib "dw_stl.dll" version 52 successfully loaded

shared lib "dw_gui.dll" version 52 successfully loaded

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

use internal message server connection to port 3901

Tue Dec 12 13:51:45 2006

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

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

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

DpIPCInit2: start server >ootspdbs01_BI1_01 <

DpShMCreate: sizeof(wp_adm) 12672 (1408)

DpShMCreate: sizeof(tm_adm) 3954072 (19672)

DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064

DpShMCreate: sizeof(comm_adm) 528064 (1048)

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

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1452)

DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 060B0040, size: 4607512)

DpShMCreate: allocated sys_adm at 060B0040

DpShMCreate: allocated wp_adm at 060B1E28

DpShMCreate: allocated tm_adm_list at 060B4FA8

DpShMCreate: allocated tm_adm at 060B4FD8

DpShMCreate: allocated wp_ca_adm at 0647A570

DpShMCreate: allocated appc_ca_adm at 06480330

DpShMCreate: allocated comm_adm at 06482270

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 06503130

DpShMCreate: allocated gw_adm at 06503170

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 065031A0

DpShMCreate: allocated wall_adm at 065031A8

Tue Dec 12 13:51:46 2006

MBUF state OFF

EmInit: MmSetImplementation( 2 ).

MM diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation flat

<EsNT> Memory Reset disabled as NT default

<ES> 511 blocks reserved for free list.

ES initialized.

J2EE server info

start = TRUE

state = STARTED

pid = 900

argv[0] = E:\usr\sap\BI1\DVEBMGS01\exe\jcontrol.EXE

argv[1] = E:\usr\sap\BI1\DVEBMGS01\exe\jcontrol.EXE

argv[2] = pf=E:\usr\sap\BI1\SYS\profile\BI1_DVEBMGS01_ootspdbs01

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1042

argv[5] = -DSAPSYSTEM=01

argv[6] = -DSAPSYSTEMNAME=BI1

argv[7] = -DSAPMYNAME=ootspdbs01_BI1_01

argv[8] = -DSAPPROFILE=E:\usr\sap\BI1\SYS\profile\BI1_DVEBMGS01_ootspdbs01

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.0 3.0 4.0.1) [dpxxdisp.c 1617]

***LOG Q0K=> DpMsAttach, mscon ( ootspdbs01) [dpxxdisp.c 11414]

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

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 60000000 for 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 [dpxxmbuf.c 1050]

DpMsgAdmin: Set patchno for this platform to 52

Release check o.K.

[former_member192350]

I've also seen this after you upgrade the kernel but haven't restarted the service. See notes 72248, 396309, and 142100 for more information on the service & MMC interaction.

Rich

[Former Member]

Hi Techie Gurus,

We're still facing the problem, to be precise:

1) In MMC Console, We are trying to start the SAP System and it started but few.

2) In Process List of SAP MMC & SID:

- Msg_server.exe(Green) with status as "running"

- disp+work.exe(Yellow) with status as "running, Message Server connection ok, Dialog Queue time 0.00 sec, J2EE: Some process running

- igswd.exe(Green) with status as "Running".

3) J2EE Process Table:

- SDM(Green); pid(3904) with Status as "RUnning" & Debug as "Switched off"

- dispatcher(Green); pid(3092) with status as "Running" & Debug as "Disabled"

- server0(Grey); pid(0) with status as "stopped" & debug as "Disabled"; Exitcode (-11113)

Background:

We have created J2EE_Guest in SAP back end which is working find. Visual Administrator is not working and suddently port got changed to some 8000. Also tried to check telnet for 3900 which also held by another port( we think). Hope this background info helps.

Appreciate help from tech gurus asap.

[Former Member]

right click on the server0 and have a look at it's tracefile.

what did you see there?

regards

Peter

[Former Member]

Hello,

But it seems your R3 and J2EE both are started.

Best Regards,

Sachin.

[Former Member]

Hi Sachin,

Its in yellow state which means not started completely.

Kindly let us know if you have any solution.

[Former Member]

Hi,

yellow doesnt mean sytem is down

yellow may be of different reasons

1. message server is not connecting to dispatcher

2. disp queue is taking long time

...........

.

.

.

.

if it is in grey or red then there is a serious error

Samrat