SAPMMC / disp + work.exe is Yellow

[Former Member]

Hallo,

I have the Processist.

msg_server.EXE is green.

disp + work.exe (dispatcher) is yellow status: stopped

Can anyone help me? During installation, there were no errors.

Best regards,

Ralph

[Former Member · Accepted solution]

Hi,

Check what messages do you have in jvm_server0.out, dev_server0.out and bootstrap traces,

traces in the SAPMMC -> NSP -> HOSTNAME -> Process List. Right-click on the process and choose "Developer Trace".

Finally, importing the SAP profiles in SAP transaction RZ10:

Utilities - Import profiles - of Active Server shoule solve.

Regards

Nagaraju

[Former Member · Accepted solution]

Hi,

this is the 'Developer Trace':

-

---

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

-

---

Sun Aug 08 09:36:07 2010

• ERROR => DlLoadLib: LoadLibrary(dbsdbslib.dll) Error 126 [dlnt.c 241]

Error 126 = "Das angegebene Modul wurde nicht gefunden."

sysno 00

sid NSP

systemid 560 (PC with Windows NT)

relno 7010

patchlevel 0

patchno 7

intno 20020600

make: multithreaded, ASCII, optimized

pid 4448

kernel runs with dp version 240(ext=110) (@(#) DPLIB-INT-VERSION-240)

length of sys_adm_ext is 364 bytes

• SWITCH TRC-HIDE on ***

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

shared lib "dw_xml.dll" version 7 successfully loaded

shared lib "dw_xtc.dll" version 7 successfully loaded

shared lib "dw_stl.dll" version 7 successfully loaded

shared lib "dw_gui.dll" version 7 successfully loaded

shared lib "dw_mdm.dll" version 7 successfully loaded

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

use internal message server connection to port 3900

Sun Aug 08 09:36:14 2010

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

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

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

DpIPCInit2: start server >Admin-PC_NSP_00 <

DpShMCreate: sizeof(wp_adm) 8232 (1176)

DpShMCreate: sizeof(tm_adm) 3786880 (18840)

DpShMCreate: sizeof(wp_ca_adm) 1280 (60)

DpShMCreate: sizeof(appc_ca_adm) 1200 (60)

DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048

DpShMCreate: sizeof(comm_adm) 528048 (1048)

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

DpShMCreate: sizeof(slock_adm) 0 (96)

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

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1296)

DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 06E00040, size: 4389744)

DpShMCreate: allocated sys_adm at 06E00040

DpShMCreate: allocated wp_adm at 06E01BF8

DpShMCreate: allocated tm_adm_list at 06E03C20

DpShMCreate: allocated tm_adm at 06E03C50

DpShMCreate: allocated wp_ca_adm at 071A04D0

DpShMCreate: allocated appc_ca_adm at 071A09D0

DpShMCreate: allocated comm_adm at 071A0E80

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 07221D30

DpShMCreate: allocated gw_adm at 07221D70

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 07221DA0

DpShMCreate: allocated wall_adm at 07221DA8

MBUF state OFF

DpCommInitTable: init table for 500 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 1024 kByte.

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

<ES> 127 blocks reserved for free list.

ES initialized.

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG Q0K=> DpMsAttach, mscon ( Admin-PC) [dpxxdisp.c 12204]

DpStartStopMsg: send start message (myname is >Admin-PC_NSP_00 <)

DpStartStopMsg: start msg sent

CCMS: alert/MONI_SEGM_SIZE = 0 monitoring and alerting switched off.

DpMsgAdmin: Set release to 7010, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1048]

DpMsgAdmin: Set patchno for this platform to 7

Release check o.K.

Sun Aug 08 09:36:54 2010

my types changed after wp death/restart 0x9f --> 0x9e

my types changed after wp death/restart 0x9e --> 0x9c

my types changed after wp death/restart 0x9c --> 0x98

my types changed after wp death/restart 0x98 --> 0x90

my types changed after wp death/restart 0x90 --> 0x80

• DP_FATAL_ERROR => DpWPCheck: no more work processes

• DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

NiWait: sleep (10000ms) ...

NiISelect: timeout 10000ms

NiISelect: maximum fd=701

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Sun Aug 08 09:37:04 2010

NiISelect: TIMEOUT occured (10000ms)

dump system status

Workprocess Table (long) Sun Aug 08 07:37:04 2010

========================

No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table

-

---

0 DIA 3712 Ended no 1 0 0

1 DIA 3552 Ended no 1 0 0

2 DIA 2356 Ended no 1 0 0

3 UPD 4460 Ended no 1 0 0

4 ENQ 3228 Ended no 1 0 0

5 BTC 3004 Ended no 1 0 0

6 SPO 1816 Ended no 1 0 0

Dispatcher Queue Statistics Sun Aug 08 07:37:04 2010

===========================

I can not start SAP-Logon.

Regards,

Ralph

[p330068 · Accepted solution]

Hi Ralph,

Please start database server max db from Start > Run >> services.msc >> here find database server and change the start up type as 'Automatic' and then start it.

Also update the host and service file for NSP. then start NSP server from SAPMMC like NSP > All Task > Start.

Search in SDN for more details

Hope it will helps

Regards

Arun Jaiswal

[Former Member · Accepted solution]

Hi,

Please ensure that the following environment variables are correctly set in your system:

1. DBMS_TYPE

(as per your database value should be ora for oracle, ada for SAPDB/MAXDB)

2. PATH

(please include path to kernel /exe/run directory here because this directory contains the dbsdbslib.dll file)

If this also does not help, only then set the following environment variables as well:

DIR_PROFILE=<dir>:\usr\sap\<SID>\SYS\profile

DIR _LIBRARY=<drive>:\usr\sap\<SID>\SYS\exe\run

Regards,

Shitij

[Former Member]

Hi,

I am having an error when I logon to our DEV system. I am getting this:

Can you help me on this?

Thank you!

Regards,

AJ

[Former Member]

We have faced almost similar issue while installing our Solution Manager.

Problem

That time some dispatcher was in yellow status when the system was indeed up. Some time

this causes system down due to not connection btwn message server and dispatcher.

Reason

Patch level difference between \usr\sap\sap\<sid>\sys\exe\run\...\sapstartsrv.exe and \usr\sap\<sid>\DVEBMGS**\exe\sapstartsrv.exe

Resolution what we have implemented

Please update the kernel to latest in both \usr\sap\sap\<sid>\sys\exe\run\uc\ntadm64\...

and \usr\sap\<sid>\DVEBMGS**\exe\. Take a restart. Please note that the sapstartsrv.exe file is come

with either sapstart_23-20001354.sar or startsap_8-20001354.sar. It is not an usual component of

SAPEXE.SAR or SAPEXEDB.SAR.

Hope it will help you to resolve the issue. Let me know if the issue persists.

Regards,

Partha

[Former Member]

Hi Experts,

I have clean up registry entry and re-install MAXDB.

If sapmmc was started, all buttons are green.

Then Sap Logon starts and the following error occurred:

connection to partner '127.0.0.1:sapdp00' broken

Component NI(network interface)

Release 710

Version 39

Module nixxi.cpp

Line 4554

Method NiIRead

Return Code -6

system Call recv

Error No 10054

Error Text WSAECONNRESET: Connection reset by peer

Counter 1

Regards,

Ralph

[p330068]

Hi Ralph,

Please update the host file in your system at Start > RUN > drivers > etc > host file

update it like below

127.0.0.1 localhost

<Server IP> <Host name>

then try to check it.

Hope it will helps

Rgards

Arun Jaiswal

[Former Member]

Hi,

connection to partner '127.0.0.1:sapdp00' broken
Component NI(network interface)

Try to logon to the SAP instance from the server itself. If you are able to login to the SAP instance from the server then the issue should be with the network or with the firewall.

Regards,

Varadharajan M