ABAP dump MESSAGE_TYPE_X

[Former Member]

i am getting this dump everyday like 30 40 times. can someone help me fix this dump.

Error analysis

    Short text of error message:

    Long text of error message:

    Technical information about the message:

    Message class....... "E"

    Number.............. 661

    Variable 1.......... "SWW_WI2OBJ"

    Variable 2.......... 000000874018

    Variable 3.......... " "

    Variable 4.......... " "

How to correct the error

    Probably the only way to eliminate the error is to correct the program.

    -

    You may able to find an interim solution to the problem

    in the SAP note system. If you have access to the note system yourself,

    please use the following search criteria:

        "MESSAGE_TYPE_X" " "

        "CL_SWF_RUN_WIM_LOCAL==========CP" bzw.

     "CL_SWF_RUN_WIM_LOCAL==========CM04U"

        "IF_SWF_RUN_WIM_PERS_INTERNAL~SAVE"

    If you cannot solve the problem yourself, please send the

    following documents to SAP:

    1. A hard copy print describing the problem (short dump).

       To obtain this, select "System->List->Save->Local File (unconverted)"

       on the current screen.

System environment

    SAP-Release 710

    Application server... "DFWPSAPPI"

    Network address...... "10.125.1.10"

    Operating system..... "Windows NT"

    Release.............. "6.1"

    Hardware type........ "32x AMD64 Level"

    Character length.... 16 Bits

    Pointer length....... 64 Bits

    Work process number.. 14

    Shortdump setting.... "full"

    Database server... "DFWPSAPPI"

    Database type..... "ORACLE"

    Database name..... "PMP"

    Database user ID.. "SAPSR3"

    Terminal.......... "EEA002433T"

    Char.set.... "C"

    SAP kernel....... 720

    created (date)... "Sep 19 2011 23:29:58"

    create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"

    Database version. "OCI_10201_SHARE, 10.2.0.4.0 "

    2. A suitable hardcopy printout of the system log.

       To obtain this, call the system log with Transaction SM21

       and set the time interval to 10 minutes before and 5 minutes after

       the short dump. In the display choose "System->List->Save->

       Local File (unconverted)"

[Former Member · Accepted solution]

Hi,

What I can see from your dump that it is coming due to some issue in
Workflow. There may be some activity/task performed in workflow which is
creating this dump. You can follow below steps to trace it back.

1. Go to T-code SWI1 and enter the date and time on which you got the dump.
2. Execute the tcode, and then you can see some workitems which had been
   processed at that time. (There must not be many processes/workitems executed
   at single second)
3. Then you have to check every single workitem processed at that moment to
   see which workflow is actually causing this issue. You can check for errors in
   the workflow log.
4. Once you got the workflow number and step on which it was stuck then you
   can test it and debug it to trace back the issue. You can test the task using
   SWUS t-code.
5. You will also require the value to execute the task, you can obtain the
   same after referring back to container values of workflow.

If you are a workflow guy, then you can easily understand the above explanation,
if you are not then please take help of some workflow guy and show him the above
steps. He/she would definitely able to help you out.

Please do confirm if it is helpful for you.

Regards

Ashish Gupta

[Former Member · Accepted solution]

Hi,

In addition to my above comments, please check for workitem 874018. Because I can see from your dump that there is particular number send in the message no., this number be workitem number.  Check the task/activity performed on this step and try to trace the issue.

Regards

Ashish Gupta

[Former Member · Accepted solution]

sorry for the late response. and thanks for the answer. I do not have a workflow guy. atleast not that I know of. I will ask around and see who can help me do this task.

I will respond when I find the solution. thanks.

[iaki_vila]

Hi Faisal,

There is a couple of notes about your note:

1397010 - Error handling too strict in workflow persistence

If after to apply the below note the error persists apply the next note and contact with SAP 2040909 - Default trace for dump when writing table SWW_WI2OBJ

Regards.