WF Builder gives "Illegal node-id in Nodevalue-Table..."

[Michael Pokraka]

Hi Jocelyn,
 
The corruption was not immediately apparent, but only happened in flows t=
hat
encountered this builder 'feature' (Dan is also quite familiar with this
one). SWUD and everything else checks out 100% and once the flow is run w=
e'd
get 'No successor defined for node nnnnn' and the flow would not enter th=
e
loop (the exact point at which the builder spat out the 'Illegal...'
message). No way to recover or restart. The only way out (apart from edit=
ing
the tables directly) is to rebuild the flow from scratch.
 
If nothing else, perhaps it is prudent advice to test that particular par=
t
of the flow before continuing build.
 
Interestingly enough we'd applied some hotpacks and the problem went away=
.
Then we recently went up to patch 44 (620 system) and it seems to be back
with a vengeance.
 
Cheers
Mike
 
Dart, Jocelyn wrote:
> Mike,
> Never had it do any damage - just save and restart the builder and all =
is
> fine.
> But report it to OSS - nothing to do with workflow corruption, it's a
> builder bug.
> Jocelyn
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Michael Pokraka
> Sent: Tuesday,9 November 2004 7:00 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: WF Builder gives "Illegal node-id in Nodevalue-Table..."
>
> Greetings,
> Yep, the subject says it all, and I suspect I may have posted about thi=
s one
> before (6.20/4.7 system).
>
> We get the above message when saving a while loop in the workflow build=
er -
> usually repeated three times in the same dialog box with a number next =
to
> it.
> Does anyone get this and/or have any light to shed on it?
>
> I've logged this with OSS before, and the official answer was that this
> would take too much time to get to the bottom of. The problem is that i=
t
> _sometimes_ causes a workflow corruption (50%?) but the corruption cann=
ot be
> reliably reproduced and we should just ignore the message. They kindly
> offered to connect in and fix any resulting corrupt workflows when it
> happens... but honestly, who has time to log a call and wait for SAP to
> respond to something logged on a DEV system when all you want/need is t=
o get
> a workflow built sometime in the next day or 2.
>
> Anyway, rebuilding workflows can get rather frustrating so I thought I'=
d ask
> here once more ... clutching at straws ... any info appreciated.
>
> Cheers
> Mike
>
>