cancel
Showing results for 
Search instead for 
Did you mean: 

Disp+work process starts than dies in SAP R/3 4.7 Ent. server

Former Member
0 Kudos

I stopped SAP R/3 4.7 ent server for backup, when i restart the Microsoft management console the disp+work process turns yellow to grey.

Can any one help me to solve this problem???

O/s :Windows2000 server

database :SAPDB 7.3

Here iam attaching the log files......

sapstart,dev_rfc,dev_w0,dev_disp,stderr2,stderr3 and stderr4

sapstart.trc:

SAPSRV\Administrator is starting R/3 System at 2006/05/13 14:35:56

SAP-R/3-Startup Program

Starting at 2006/05/13 14:35:56

Startup Profile: "D:\usr\sap\ER2\SYS\profile\START_DVEBMGS01_SAPSRV"

Starting Programs

(3352) Execute: D:\usr\sap\ER2\SYS\exe\run\strdbs.cmd ER2

(3188) CreateProcess: D:\usr\sap\ER2\SYS\exe\run\msg_server.exe pf=D:\usr\sap\ER2\SYS\profile\ER2_DVEBMGS01_SAPSRV

(3856) CreateProcess: D:\usr\sap\ER2\SYS\exe\run\disp+work.exe pf=D:\usr\sap\ER2\SYS\profile\ER2_DVEBMGS01_SAPSRV

SAPSRV\Administrator is stopping R/3 System at 2006/05/13 14:44:15

(1264) Parent Shutdown at 2006/05/13 14:44:15

(1264) kill(3856) failed.

SAPSRV\Administrator is starting R/3 System at 2006/05/13 14:44:48

SAP-R/3-Startup Program

Starting at 2006/05/13 14:44:48

Startup Profile: "D:\usr\sap\ER2\SYS\profile\START_DVEBMGS01_SAPSRV"

Starting Programs

(3872) Execute: D:\usr\sap\ER2\SYS\exe\run\strdbs.cmd ER2

(3876) CreateProcess: D:\usr\sap\ER2\SYS\exe\run\msg_server.exe pf=D:\usr\sap\ER2\SYS\profile\ER2_DVEBMGS01_SAPSRV

(3844) CreateProcess: D:\usr\sap\ER2\SYS\exe\run\disp+work.exe pf=D:\usr\sap\ER2\SYS\profile\ER2_DVEBMGS01_SAPSRV

SAPSRV\Administrator is stopping R/3 System at 2006/05/13 16:24:21

(1264) Parent Shutdown at 2006/05/13 16:24:21

(1264) kill(3844) failed.

SAPSRV\Administrator is starting R/3 System at 2006/05/13 17:53:25

SAP-R/3-Startup Program

Starting at 2006/05/13 17:53:25

Startup Profile: "D:\usr\sap\ER2\SYS\profile\START_DVEBMGS01_SAPSRV"

Starting Programs

(2872) Execute: D:\usr\sap\ER2\SYS\exe\run\strdbs.cmd ER2

(948) CreateProcess: D:\usr\sap\ER2\SYS\exe\run\msg_server.exe pf=D:\usr\sap\ER2\SYS\profile\ER2_DVEBMGS01_SAPSRV

(3468) CreateProcess: D:\usr\sap\ER2\SYS\exe\run\disp+work.exe pf=D:\usr\sap\ER2\SYS\profile\ER2_DVEBMGS01_SAPSRV

SAPSRV\Administrator is stopping R/3 System at 2006/05/14 14:36:33

(1264) Parent Shutdown at 2006/05/14 14:36:33

(1264) kill(3468) failed.

SAPSRV\Administrator is starting R/3 System at 2006/05/14 14:41:50

SAP-R/3-Startup Program

Starting at 2006/05/14 14:41:50

Startup Profile: "D:\usr\sap\ER2\SYS\profile\START_DVEBMGS01_SAPSRV"

Starting Programs

(3220) Execute: D:\usr\sap\ER2\SYS\exe\run\strdbs.cmd ER2

(3236) CreateProcess: D:\usr\sap\ER2\SYS\exe\run\msg_server.exe pf=D:\usr\sap\ER2\SYS\profile\ER2_DVEBMGS01_SAPSRV

(3244) CreateProcess: D:\usr\sap\ER2\SYS\exe\run\disp+work.exe pf=D:\usr\sap\ER2\SYS\profile\ER2_DVEBMGS01_SAPSRV

SAPSRV\Administrator is stopping R/3 System at 2006/05/14 14:47:09

(1264) Parent Shutdown at 2006/05/14 14:47:09

(1264) kill(3244) failed.

2.dev_w0

-


trc file: "dev_w0", trc level: 1, release: "620"

-


*

  • ACTIVE TRACE LEVEL 1

  • ACTIVE TRACE COMPONENTS all, M

*

B

B Sun May 14 14:42:14 2006

B create_con (con_name=R/3)

B Loading DB library '5\dbadaslib.dll' ...

M *** ERROR => DlLoadLib: LoadLibrary(5\dbadaslib.dll) Error 126 [dlnt.c 226]

M Error 126 = "The specified module could not be found."

B *** ERROR => Couldn't load library '5\dbadaslib.dll'

[dbcon.c 3789]

M systemid 560 (PC with Windows NT)

M relno 6200

M patchlevel 0

M patchno 674

M intno 20020600

M pid 3296

M

M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 3296) [dpxxdisp.c 1028]

I MtxInit: -2 0 0

M DpShMCreate: sizeof(wp_adm) 20304 (752)

M DpShMCreate: sizeof(tm_adm) 1690816 (8412)

M DpShMCreate: sizeof(wp_ca_adm) 18000 (60)

M DpShMCreate: sizeof(appc_ca_adm) 6000 (60)

M DpShMCreate: sizeof(comm_adm) 192000 (384)

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

M DpShMCreate: SHM_DP_ADM_KEY (addr: 00100040, size: 1985344)

M DpShMCreate: allocated sys_adm at 00100040

M DpShMCreate: allocated wp_adm at 00100560

M DpShMCreate: allocated tm_adm_list at 001054B0

M DpShMCreate: allocated tm_adm at 001054D8

M DpShMCreate: allocated wp_ca_adm at 002A2198

M DpShMCreate: allocated appc_ca_adm at 002A67E8

M DpShMCreate: allocated comm_adm_list at 002A7F58

M DpShMCreate: allocated comm_adm at 002A7F70

M DpShMCreate: allocated ca_info at 002D6D70

M DpShMCreate: allocated wall_adm at 002D6D78

X

X Sun May 14 14:42:16 2006

X EmInit: MmSetImplementation( 2 ).

X <ES> client 0 initializing ....

X Using implementation std

M <EsNT> Memory Reset enabled as NT default

X ES initialized.

M calling db_connect ...

B create_con (con_name=R/3)

B Loading DB library '5\dbadaslib.dll' ...

M *** ERROR => DlLoadLib: LoadLibrary(5\dbadaslib.dll) Error 126 [dlnt.c 226]

M Error 126 = "The specified module could not be found."

B *** ERROR => Couldn't load library '5\dbadaslib.dll'

[dbcon.c 3789]

M ***LOG R19=> tskh_init, db_connect ( DB-Connect 008192) [thxxhead.c 1102]

M in_ThErrHandle: 1

M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 8437]

M

M Info for wp 0

M

M stat = 4

M reqtype = 1

M act_reqtype = -1

M tid = -1

M mode = 255

M len = -1

M rq_id = -1

M rq_source = 255

M last_tid = 0

M last_mode = 0

M rfc_req = 0

M report = > <

M action = 0

M tab_name = > <

M

M *****************************************************************************

M *

M * LOCATION SAP-Server SAPSRV_ER2_01 on host SAPSRV (wp 0)

M * ERROR tskh_init: db_connect

M *

M * TIME Sun May 14 14:42:16 2006

M * RELEASE 620

M * COMPONENT Taskhandler

M * VERSION 1

M * RC 13

M * MODULE thxxhead.c

M * LINE 8569

M * COUNTER 1

M *

M *****************************************************************************

M

M Entering TH_CALLHOOKS

M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP

M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 672]

M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 237]

M Entering ThSetStatError

M Entering ThReadDetachMode

M call ThrShutDown (1)...

M ***LOG Q02=> wp_halt, WPStop (Workproc 0 3296) [dpnttool.c 346]

3. dev_rfc.trc

        • ERROR file opened at 20060419 104033 India Standard , SAP-REL 620,0,1574 RFC-VER 3 673347 MT-SL

T:73832 Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1422

T:73832 <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION

T:73832 <* RfcCallReceive [1] : returns 3:RFC_SYS_EXCEPTION

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

>TS> Wed Apr 19 10:52:34 2006

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

>TS> Wed Apr 19 10:52:35 2006

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

>TS> Wed Apr 19 10:53:15 2006

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

>TS> Wed Apr 19 10:55:12 2006

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

>TS> Wed Apr 19 10:58:17 2006

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

>TS> Wed Apr 19 11:01:11 2006

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

>TS> Wed Apr 19 11:02:21 2006

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

>TS> Wed Apr 19 11:02:22 2006

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

>TS> Wed Apr 19 11:05:32 2006

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCall [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcCallReceive [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcSendData [1] : returns 18:RFC_INVALID_HANDLE

T:73832 <* RfcDispatch [1] : returns 18:RFC_INVALID_HANDLE

        • ERROR file opened at 20060421 202203 India Standard , SAP-REL 620,0,841 RFC-VER 3 568712 MT-SL

T:4468 Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1402

T:4468 <* RfcDispatch [1] : returns 1:RFC_FAILURE

        • ERROR file opened at 20060428 194717 India Standard , SAP-REL 620,0,841 RFC-VER 3 568712 MT-SL

>TS> Fri Apr 28 19:47:18 2006

T:73164 Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1402

T:73164 <* RfcDispatch [1] : returns 1:RFC_FAILURE

        • ERROR file opened at 20060512 214308 India Standard , SAP-REL 620,0,841 RFC-VER 3 568712 MT-SL

T:5504 Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1402

T:5504 <* RfcDispatch [1] : returns 1:RFC_FAILURE

4.dev_disp.trc

-


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

-


Sun May 14 14:42:07 2006

kernel runs with dp version 3(ext=1) (@(#) DPLIB-INT-VERSION-3)

length of sys_adm_ext is 304 bytes

systemid 560 (PC with Windows NT)

relno 6200

patchlevel 0

patchno 674

intno 20020600

pid 3244

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

shared lib "dw_xml.dll" version 674 successfully loaded

shared lib "dw_xtc.dll" version 674 successfully loaded

shared lib "dw_stl.dll" version 674 successfully loaded

Sun May 14 14:42:11 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 3212]

MtxInit: -2 0 0

DpShMCreate: sizeof(wp_adm) 20304 (752)

DpShMCreate: sizeof(tm_adm) 1690816 (8412)

DpShMCreate: sizeof(wp_ca_adm) 18000 (60)

DpShMCreate: sizeof(appc_ca_adm) 6000 (60)

DpShMCreate: sizeof(comm_adm) 192000 (384)

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

DpShMCreate: SHM_DP_ADM_KEY (addr: 001C0040, size: 1985344)

DpShMCreate: allocated sys_adm at 001C0040

DpShMCreate: allocated wp_adm at 001C0560

DpShMCreate: allocated tm_adm_list at 001C54B0

DpShMCreate: allocated tm_adm at 001C54D8

DpShMCreate: allocated wp_ca_adm at 00362198

DpShMCreate: allocated appc_ca_adm at 003667E8

DpShMCreate: allocated comm_adm_list at 00367F58

DpShMCreate: allocated comm_adm at 00367F70

DpShMCreate: allocated ca_info at 00396D70

DpShMCreate: allocated wall_adm at 00396D78

Sun May 14 14:42:12 2006

MBUF state OFF

EmInit: MmSetImplementation( 2 ).

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation std

<EsNT> Memory Reset enabled as NT default

<EsNT> EsIUnamFileMapInit: Initialize the memory 2458 MB

<ES> 2457 blocks reserved for free list.

ES initialized.

***LOG Q0K=> DpMsAttach, mscon ( SAPSRV) [dpxxdisp.c 9115]

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

Sun May 14 14:42:13 2006

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

DpMsgAdmin: Set release to 6200, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

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

DpMsgAdmin: Set patchno for this platform to 674

Release check o.K.

Sun May 14 14:42:52 2006

      • ERROR => W0 (pid 3296) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W0

      • ERROR => W1 (pid 3304) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W1

      • ERROR => W2 (pid 3312) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W2

      • ERROR => W3 (pid 3320) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W3

      • ERROR => W4 (pid 3328) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W4

      • ERROR => W5 (pid 3336) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W5

      • ERROR => W6 (pid 3344) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W6

      • ERROR => W7 (pid 3784) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W7

      • ERROR => W8 (pid 3820) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W8

      • ERROR => W9 (pid 3584) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W9

      • ERROR => W10 (pid 3668) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W10

      • ERROR => W11 (pid 3632) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W11

      • ERROR => W12 (pid 3652) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W12

      • ERROR => W13 (pid 3616) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W13

      • ERROR => W14 (pid 3648) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W14

      • ERROR => W15 (pid 3628) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W15

      • ERROR => W16 (pid 3656) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W16

      • ERROR => W17 (pid 4024) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W17

      • ERROR => W18 (pid 3928) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W18

      • ERROR => W19 (pid 3880) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W19

      • ERROR => W20 (pid 3432) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W20

      • ERROR => W21 (pid 3124) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W21

      • ERROR => W22 (pid 3800) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W22

      • ERROR => W23 (pid 3804) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W23

      • ERROR => W24 (pid 3812) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W24

      • ERROR => W25 (pid 3832) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W25

      • ERROR => W26 (pid 3480) died [dpxxdisp.c 11523]

force unlock of wp_adm mutex W26

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

      • DP_FATAL_ERROR => DpEnvCheck: no more work processes

      • DISPATCHER EMERGENCY SHUTDOWN ***

DpModState: change server state from STARTING to SHUTDOWN

Sun May 14 14:42:57 2006

***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 9341]

MBUF state OFF

MBUF component DOWN

***LOG Q05=> DpHalt, DPStop ( 3244) [dpxxdisp.c 7883]

5.stderr2

D:\usr\sap\ER2\DVEBMGS01\work>set DBNAME=ERc

D:\usr\sap\ER2\DVEBMGS01\work>if "" == "" (set DB_USERKEY="c" ) else (set DB_USERKEY="c_J2EE" )

D:\usr\sap\ER2\DVEBMGS01\work>dbmcli -U "c" dbm_version VERSION 1>dbversion.out

D:\usr\sap\ER2\DVEBMGS01\work>findstr -i "OK" dbversion.out 1>dbmcli.err

D:\usr\sap\ER2\DVEBMGS01\work>if errorlevel 1 goto err_dbm

D:\usr\sap\ER2\DVEBMGS01\work>findstr -i "7.4" dbversion.out 1>adatmp

D:\usr\sap\ER2\DVEBMGS01\work>if errorlevel 1 (set dbmcli_cmd="db_warm" ) else (set dbmcli_cmd="db_online" )

D:\usr\sap\ER2\DVEBMGS01\work>dbmcli -U "c" "db_warm"

OK

Database ER2 successfully started !

6. stderr3

rslgwr1(21): Searching for overlap point in pre-existing SysLog file...

7.stderr4

maximum pfclock time: 4294sec (1)

***

      • work process W0 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

***

      • work process W2 died => tskh_init: db_connect

IcmBndMain: handle for "localhost:8001" successfully sent to server

maximum pfclock time: 4294sec (1)

***

      • work process W23 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 1155

adjust_clock: delta 1106

***

      • work process W26 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

***

      • work process W10 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 757

***

      • work process W20 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 9312

adjust_clock: delta 1040

***

      • work process W7 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

***

      • work process W18 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

***

      • work process W12 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

***

      • work process W1 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

***

      • work process W14 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 760

***

      • work process W11 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 1129

***

      • work process W25 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 3589

adjust_clock: delta 631

***

      • work process W24 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 757

adjust_clock: delta 652

adjust_clock: delta 514

***

      • work process W8 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

***

      • work process W22 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 1192

***

      • work process W21 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

***

      • work process W3 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

***

      • work process W16 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 1617

adjust_clock: delta 1609

***

      • work process W5 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 9714

***

      • work process W17 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 2063

***

      • work process W19 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 746

***

      • work process W6 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 2040

***

      • work process W4 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

***

      • work process W15 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

adjust_clock: delta 1089

***

      • work process W13 died => tskh_init: db_connect

maximum pfclock time: 4294sec (1)

***

      • work process W9 died => tskh_init: db_connect

      • ICM up and operational (pid: 3272) ***

Shutdown ICM server ....maximum pfclock time: 4294sec (1)

      • ICM shutdown completed (pid: 3272) ***

***

      • DISPATCHER EMERGENCY SHUTDOWN => DpEnvCheck: no more work processes

maximum pfclock time: 4294sec (1)

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi Sreepathi,

Your error log says some DB DLL file is not found. Check if all your DB services are up. You may do so in WINDOWS CONTROL PANEL --> Administrative tools --> Services.

Regards

Ak.

Former Member
0 Kudos

Hi Arun,

Thanks for immediate reply. I checked,all DB service SAPDB<SID> is up running.

For your info...WE have another instance on the same box using the same database which is up running.

The problem is with disp+work process only, message server working fine.

regards,

sreepathi

Former Member
0 Kudos

hi Sreepathi,

i guess you need to import that dbadaslib seperately coz, this file is gone missing... Check these OSS Notes 325402. it will help i guess

Regards

ak

Former Member
0 Kudos

Hi ,

try restarting the machine and starting SAP again.

I guess some processes are not killed.

Unable to load dbadaslib ,does'nt mean that it is not there.

Regards,

Bapujee Naidu

Former Member
0 Kudos

Hi,

Disp+work process started but when i try to logon using other userid it throws a error"DB-Error -0".I can able to logon client 000 using sap*.

Please help me to come out of this problem...

thanks & regards

sreepathi

Message was edited by: Sreepathi

Former Member
0 Kudos

hi Sreepathi,

I checked the OSS notes. There is a solution given there Check this note: 760175. That is not your exact solution for your problem but it seems there is a problem in the combination of the SAP_BASIS Package and Kernel.

Probably a kernal patching and SAP_Basis upgrade should solve the problem.

btw you say "I can able to logon client 000 using sap*". is this right or did u mean to say you CAN'T but mistakenly typed can!

what user is giving this problem for you?

Regards

Ak.

Message was edited by: Arunkumar Ravi

Former Member
0 Kudos

Hi AK,

Thanks for your help. Yes i can able to logon to 000 using SAP* but not with other user id's.

We have SAP_Basis patch level 41 but Kernel 6.20 patch level is only 674.

Kindly send me step by step kernel upgrade guide..

thanks & regards,

sreepathi

Former Member
0 Kudos

hi Sreepathi,

Go to service.sap.com/instguides look for the upgrade document there.

Regards

Ak.

Former Member
0 Kudos

Hi Sreepathi,

To Down load Kernel,Go to Support packages and patches in Service market place...click on OTHER...select your required version of kernel...Down load the following files from ...Db independent link and ur Db version..The list is...

1.sapstart

2.saposcol

3.Kernel Part1 & Part2

4.R3trans

5.tp

6.Database library

7.dsr lib

8.SAPCAR

9.DBATOOLS

10.R3LOAD

11.DISP+Work Package

Go to ‘usr\sap\SID\sys\exe’ Directory.

Create a folder called ‘runold’.

Create a folder ‘runnew’ on ‘usr\sap\SID\sys\exe’.

Copy all the above files downloaded from the Sap Market place in to this ‘runnew’ folder.

Copy the file ‘sapcar’ from ‘usr\sap\SID\sys\exe\run’ to ‘runnew’ and rename it to ‘sapcar1’.

Uncar all the files in ‘sapnew’ using ‘sapcar1’.

Shutdown SAP.

Move the contents of ‘usr\sap\SID\sys\exe\run’ to ‘runold’.

Copy the contents of ‘runnew’ to ‘usr\sap\SID\sys\exe\run’

Restart the SAP.

Check the kernel upgrade replications in SM51-->Release Notes

Hope this helps,if useful plz award points.

Regards,

Bapujee Naidu

Former Member
0 Kudos

Hi Bapujee,

I upgraded kernel 6.20 (Patch level 1602)as per the details you mentioned. when i restarted the server the message server starts perfectly,but disp+work process turns to yellow than dies(during that time WP Table is blank).

Also attaching dev_w0 file.

thanks & regards,

sreepathi

-


trc file: "dev_w0", trc level: 1, release: "620"

-


*

  • ACTIVE TRACE LEVEL 1

  • ACTIVE TRACE COMPONENTS all, M

*

B

B Tue May 16 23:38:55 2006

B create_con (con_name=R/3)

B Loading DB library 'D:\usr\sap\ER2\SYS\exe\run\dbadaslib.dll' ...

B Library 'D:\usr\sap\ER2\SYS\exe\run\dbadaslib.dll' loaded

B Version of 'D:\usr\sap\ER2\SYS\exe\run\dbadaslib.dll' is "620.02", patchlevel (0.1599)

B New connection 0 created

M systemid 560 (PC with Windows NT)

M relno 6200

M patchlevel 0

M patchno 1602

M intno 20020600

M make: multithreaded, ASCII

M pid 3180

M

M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 3180) [dpxxdisp.c 1088]

I MtxInit: -2 0 0

M DpShMCreate: sizeof(wp_adm) 12920 (760)

M DpShMCreate: sizeof(tm_adm) 1835536 (9132)

M DpShMCreate: sizeof(wp_ca_adm) 18000 (60)

M DpShMCreate: sizeof(appc_ca_adm) 6000 (60)

M DpShMCreate: sizeof(comm_adm) 192000 (384)

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

M DpShMCreate: SHM_DP_ADM_KEY (addr: 05D10040, size: 2122960)

M DpShMCreate: allocated sys_adm at 05D10040

M DpShMCreate: allocated wp_adm at 05D10678

M DpShMCreate: allocated tm_adm_list at 05D138F0

M DpShMCreate: allocated tm_adm at 05D13918

M DpShMCreate: allocated wp_ca_adm at 05ED3B28

M DpShMCreate: allocated appc_ca_adm at 05ED8178

M DpShMCreate: allocated comm_adm_list at 05ED98E8

M DpShMCreate: allocated comm_adm at 05ED9900

M DpShMCreate: allocated ca_info at 05F08700

M DpShMCreate: allocated wall_adm at 05F08708

X EmInit: MmSetImplementation( 2 ).

X <ES> client 0 initializing ....

X Using implementation std

M <EsNT> Memory Reset enabled as NT default

X ES initialized.

M

M Tue May 16 23:38:57 2006

M calling db_connect ...

C

C DBADASLIB : version 620.02

C SAPDB shared library (dbadaslib) patchlevels (last 10)

C (0.1599) Set isolation level calls optimized (note 762712)

C (0.1491) ThGetWpId corrected (note 624930)

C (0.1412) Support of SAPDB database hints (note 652096)

C (0.1411) LobGetpiece returns a failure if no data available (note 720343)

C (0.1355) SAPDB supports DBSL_CMD_INI_KRN_CALLBACK (note 624930)

C (0.1352) CHECKPOINT NOWAIT removed (note 708201)

C (0.1278) UPDSTAT without tracefile (note 696689)

C (0.1267) Explain problem with RAW values and IN-clause fixed (note 692188)

C (0.1189) Explain for database version 7.5 changed (note 680586)

C (0.1115) Object consistency (note 650475)

C

C

C INFO : SQLOPT= -I 0 -t 0 -F SAPDB.3180.pct

C Precompiler Runtime : C-PreComp 7.3.1 Build 007-000-087-566

C Precompiler runtime is SAP DB 7.3.1.007

C *** ERROR => Using non supported SAP DB precompiler runtime version: 7.3.1.007

[dbslada.c 5093]

C *** ERROR => Min. version for this release must be 7.3.1.010

[dbslada.c 5095]

M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c 1200]

M in_ThErrHandle: 1

M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 8812]

M

M Info for wp 0

M

M stat = 4

M reqtype = 1

M rq_info = 0

M act_reqtype = -1

M tid = -1

M mode = 255

M len = -1

M rq_id = -1

M rq_source = 255

M last_tid = 0

M last_mode = 0

M int_checked_resource(RFC) = 0

M ext_checked_resource(RFC) = 0

M int_checked_resource(HTTP) = 0

M ext_checked_resource(HTTP) = 0

M report = > <

M action = 0

M tab_name = > <

M

M *****************************************************************************

M *

M * LOCATION SAP-Server SAPSRV_ER2_01 on host SAPSRV (wp 0)

M * ERROR tskh_init: db_connect

M *

M * TIME Tue May 16 23:38:57 2006

M * RELEASE 620

M * COMPONENT Taskhandler

M * VERSION 1

M * RC 13

M * MODULE thxxhead.c

M * LINE 8957

M * COUNTER 1

M *

M *****************************************************************************

M

M Entering TH_CALLHOOKS

M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP

M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 672]

M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 233]

M Entering ThSetStatError

M Entering ThReadDetachMode

M call ThrShutDown (1)...

M ***LOG Q02=> wp_halt, WPStop (Workproc 0 3180) [dpnttool.c 356]

Message was edited by: Sreepathi

Former Member
0 Kudos

hi,

<i> *** ERROR => Using non supported SAP DB precompiler runtime version: 7.3.1.007

[dbslada.c 5093]

C *** ERROR => Min. version for this release must be 7.3.1.010

[dbslada.c 5095]

M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c 1200]

M in_ThErrHandle: 1

M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 8812]</i>

I guess that's why your disp+work is yellow. See if you can fix it.

Regards

Ak.

Former Member
0 Kudos

Hi Sreepathi,

Have you downloaded all the kernel files as I have mentioned?

Especially DBLibrary and Disp+work packages?

Regards,

BApujee Naidu

Former Member
0 Kudos

Hi Bapujee,

Now i upgraded the "run" directory by downloading and uncaring the following files in run folder

LIB_DBSL_1926-10001660.SAR,

DW_1945-10001664.SAR,

STRDBS_2-10001660.SAR,

SAPEXEDB_1602-10001660.SAR,

and SAPEXE_1602-10001664.SAR.

after restarting sap server and o/s, dispacher starts than stops(Now i can see values in WP Table before it is blank).

But the problem not solved....

regards,

sreepathi

Former Member
0 Kudos

Hi sreepathi,

The error is here I suppose ..

"*** ERROR => Using non supported SAP DB precompiler runtime version: 7.3.1.007

[dbslada.c 5093]

C *** ERROR => Min. version for this release must be 7.3.1.010

[dbslada.c 5095]"

Please see OSS notes 674065 and 557227 which have the solution for this problem..

But I still i have one query...how can a SAP system which is stopped for backup is giving all these problems?

Did u change any profile parameters previously?

Let me know if these notes are of any help!

Regards,

Bapujee Naidu

Former Member
0 Kudos

Hi Bapujee,

Thanks the server is up after installing the SAPDB 7.3.1.10 PRECOMPILER as per the notes 674065 and 557227.

Thanks once again....

regards,

sreepathi

(sreepathi.p@gmail.com)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi all

i've the same disp+work problem but in a CRM 5.0 environment.

The disp+work service become yellow for 1 minute and then die.

The only thing that i did was turn off the server.

None was installed or changed Before turn off of course i turn off both the sap and oracle services.

Have you any idea to solve this problem?

thank you

Dan