Work Process : Status 'New'

[Former Member]

Dearest

Could someone explain me when exactly a work process has status: 'New'

We had a problem recently on our servers where the application server died, all WP had status 'New' ( and didn't go to status 'Waiting' like they should ? )

Thank you for your time

Kind regards

System Info:

NW 7.21 EXT Patchlevel 214

Windows X64

MS SQL 2012

[Former Member · Accepted solution]

We made a message to SAP for this issue.

The problem occured because of changing profile parameters:

es/implementation and rdisp/wp_auto_restart.

[Former Member]

check the following post

http://scn.sap.com/thread/3150493

[nirmal_konchada]

Hello,

Can you please check if you have space available in the SAP tablespace.

Regards,

Nirmal.

[Former Member]

Hi

Thanks for your answer, where exactly can I check this? In t-code DB02 under Space? if so everything seems to be ok.

Edit: There are no tablespaces in MS SQL?

Kr

[Reagan]

Hello

You need to first check the work process trace files present in the work directory.

I suspect an issue at the database level.

Check whether there is some space issue with the log are of the MSSQL

Regards

RB

[Former Member]

Hey

Plenty of free space left.

Are there any other reasons that may cause this work process behaviour?

Kr

[Reagan]

You need to check the work process trace file

Regards

RB

[Former Member]

Thu Mar 27 11:33:30 2014

*** ERROR => DpHdlDeadWp: W12 (pid 3488) died (severity=0, status=0) [dpxxwp.c     1740]

-> after 1 day

*** ERROR => DpHdlDeadWp: W0 (pid 4312) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W1 (pid 4204) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W2 (pid 4688) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W3 (pid 4300) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W4 (pid 2436) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W5 (pid 4388) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W6 (pid 4452) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W7 (pid 3160) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W8 (pid 4160) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W9 (pid 2800) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W10 (pid 4260) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W11 (pid 5060) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W12 (pid 4844) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W13 (pid 4792) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W14 (pid 1800) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W15 (pid 3344) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W16 (pid 4780) died (severity=0, status=0) [dpxxwp.c     1740]

*** ERROR => DpHdlDeadWp: W18 (pid 632) died (severity=0, status=0) [dpxxwp.c     1740]

-> result = crash

[Reagan]

Unfortunately there is no sufficient information to guide you.

You need to provide the complete log for dev_disp and dev_w0 trace files and if possible dev_ms.

Regards

RB