ST22: START_CALL_SICK



Share this article :

Sympton

The short dump in transaction code ST22 contains the message ABAP/4 runtime error START_CALL_SICK

Caused

The are multiple cases that caused by this ABAP runtime error. To dig into details, you may need to scroll down till the “Error analysis” part. Some of causes are,

 "enqueue name is empty"

 

 "no application server offers an BTC service"

Solution

1. Start transaction code SICK or SM28 to analyze the error.

2. For error “enqueue name is empty”, go to transaction code RZ10 and check the below parameter is at least 1.

rdisp/wp_no_enq

3. For error “no application server offers an BTC service”, go to RZ10 and check the below parameter is at least 1.

rdisp/wp_no_btc

4. Restart the system.

5. If error still occurred, apply new kernel upgrade and restart the system.

Related posts

BR0310W: Connect to database instance failed
RSPO1055: SAP Spool Installation Check
Change SAP Transport Request Description
STMS: Create_Enqueue_Request on Import Request
© 2017 ITsiti. All Rights Reserved
Powered by KEEM