Skip to Content

Document Distribution WS20000137 gives error as result in the TS20000297 DMS - Standard Workflow

Hello Experts, The task TS20000297 - generate Generate distribution order package, in the WS20000137 (DMS) gives an error result and not all times. Is there any way to check this problem. This does not occur frequently .. but occurs some times only. I have given the error here. It is caught only once. and is not repeating frequently.

log1.png (52.3 kB)
Add comment
10|10000 characters needed characters exceeded

  • Hello Laszlo and Rob,

    I have added the screenshot of the same. As i mentioned it is not repeating. Could any configuration cause a problem. The CV04N is used to make this manual distribution. Is it possible to use the trace if it can give better information. Let me know on the same. Will the trace capture the manual distribution of the CV04N

  • Get RSS Feed

2 Answers

  • May 09 at 09:21 AM

    Hi,

    you can check the details in the related workflow log. For further details check:

    KBA 2618383 - Read The Workflow Technical Log

    Best Regards
    Laszlo

    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      The method DocumentDisPackage.Generate which is a part of the TS20000297 is returning the error. The catch here is it is not giving the error at all times. So when we debug the case, it is not replicated at that time. Is there any other way to check the consistency here.

  • May 09 at 09:21 AM

    hi,

    The way is to use the workflow log, technical details to figure out the contents of all of the containerelements which are send to the method of the task. then you use that information to execute the method independently of the workflow to see if you can replicate the problem, there you can also place break-points to help you in your findings.

    Kind regards, Rob Dielemans

    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      Unfortunately you can't do a lot in these rare occurrences. Either figure out exactly how to replicate it, or monitor it and next time it happens consult the system log SM21 for anything out of the ordinary around the time of execution.

      Kind regards, Rob Dielemans