cancel
Showing results for 
Search instead for 
Did you mean: 

work proccess are dying after R/3 start...

Former Member
0 Kudos

Hi all,

I have installed a WAS 6.20 with SAP-DB.

I have applied all the latest kernel patches, etc for this.

The J2EE is running fine. But after I start the R/3 System and try to login to the Host with SAPlogon the disp+work.exe is always dying (when I watch it in the R/3 MMC console).

After starting the R/3 instance the dispwork proccess goes up to 12 or 13 and die one after one. In the end of the R/3 start process there is one dispwork proccess left.

I did the whole installation several times.

Its a central instance install on a Windows 2000 Server.

Here is a short output from dev_disp:

Wed Feb 16 17:18:06 2005

      • ERROR => W0 (pid 2404) died [dpxxdisp.c 11747]

      • ERROR => W1 (pid 2796) died [dpxxdisp.c 11747]

      • ERROR => W2 (pid 2876) died [dpxxdisp.c 11747]

      • ERROR => W3 (pid 2680) died [dpxxdisp.c 11747]

      • ERROR => W4 (pid 2776) died [dpxxdisp.c 11747]

      • ERROR => W5 (pid 3016) died [dpxxdisp.c 11747]

      • ERROR => W6 (pid 3020) died [dpxxdisp.c 11747]

      • ERROR => W7 (pid 3052) died [dpxxdisp.c 11747]

      • ERROR => W8 (pid 2632) died [dpxxdisp.c 11747]

      • ERROR => W9 (pid 2932) died [dpxxdisp.c 11747]

      • ERROR => W10 (pid 2940) died [dpxxdisp.c 11747]

      • ERROR => W11 (pid 2980) died [dpxxdisp.c 11747]

      • ERROR => W12 (pid 2668) died [dpxxdisp.c 11747]

      • ERROR => W13 (pid 2748) died [dpxxdisp.c 11747]

      • ERROR => W14 (pid 2572) died [dpxxdisp.c 11747]

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

      • DP_FATAL_ERROR => DpEnvCheck: no more work processes

      • DISPATCHER EMERGENCY SHUTDOWN ***

DpModState: change server state from STARTING to SHUTDOWN

Wed Feb 16 17:18:16 2005

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

MBUF state OFF

MBUF component DOWN

***LOG Q05=> DpHalt, DPStop ( 2584) [dpxxdisp.c 8116]

Does anyone have some suggestions?

Thanks for any hints!

regards

Nesimi Buelbuel

Message was edited by: Nesimi Buelbuel

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

I am having a similar problem. It's happened on a number of occasions. Once when a session was terminated between SAPGui and SAP Server because of a restart on the Gui machine. It started another time after running sgen (system bogged down and went into dialoge queue standstill). If I follow the trace files of my work processes I find that they are stopping at this error:

C Precompiler Runtime : C-PreComp 7.3.1 Build 018-100-081-474

C Precompiler runtime is SAP DB 7.3.1.018

C Try to connect (DEFAULT) on connection 0 ...

I think it may have something to do with updating the database or the precompiler runtime version. Who knows though. Is this close to the problem you are having?

Former Member
0 Kudos

I don't know how to solve this problem, however I was running into the same problem and was able to "prevent" it when I built a new system by upgrading the kernal to the highest patch leve immediately after installing the Web AS.

Former Member
0 Kudos

Hi guys, during my install I did have to do an upgrade of the precompiler runtime. Have a look at OSS note 683937 and 490325 whether this can solve your problems. Tiest.

Former Member
0 Kudos

Is this a "preview" edition or a normal R/3 system full install.

Have you searched the OSS for notes on this topic?

If this is a normal system you should probably contact the OSS

Former Member
0 Kudos

its a normal WAS 6.20 installation.

I have searched the OSS through and through.

I cant figure out why this occurs.

Former Member
0 Kudos

I would suggest you contact the OSS and create a message. These forums are not really intended for these types of problems.

But perhaps someone might respond with some ideas for you.

Former Member
0 Kudos

Nesimi, the only think I can think of is related to incorrect parameter setting in your instance profile. Did you change anything in this profile and if so, what? Tiest

Former Member
0 Kudos

I have already played around with the rdisp/wp_no_dia setting.I have put them to 1, to 6 etc. All with the same results.

The full settings in the profile is:

SAPSYSTEMNAME=XD1

INSTANCE_NAME=DVEBMGS00

SAPSYSTEM=00

rdisp/wp_no_dia=1

rdisp/wp_no_btc=2

rdisp/wp_no_vb=3

rdisp/wp_no_vb2=2

rdisp/wp_no_enq=1

rdisp/wp_no_spo=1

SAPGLOBALHOST=saptest

PHYS_MEMSIZE=609

DIR_TRANS=C:\usr\sap\trans

icm/server_port_0=PROT=HTTP,PORT=8000,EXTBIND=1

rsdb/dbid=XD1

dbs/ada/schema=sapXD1

exe/j2ee = C:\JBuilder5\SAP_J2EE_Engine\alone\go.bat

icm/HTTP/j2ee_0 = HOST=localhost,PREFIX=/,CONN=0-10,PORT=50000

rdisp/j2ee_start = 1

rdisp/j2ee_timeout = 60

rdisp/j2ee_error = 10

em/reserve_mapping_window = off

regards

Nesimi Buelbuel

Former Member
0 Kudos

Nesimi, please have a look at one or the Workprocess Log files, e.g. dev_w0. In these logfiles some more information on why the process is dying should be captured. Let me know what you have found.

Nesimi, also have a look at the instance parameter abap/buffersize and let me know what it is as well.

Kind regards, Tiest

Message was edited by: Tiest van Gool

former_member185954
Active Contributor
0 Kudos

Nesimi, can you post the dev_w0 log file contents or dev_w1 contents. I mean can you post the contents of the log for the relevant work process that is getting killed.

Regards,

Sid