nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problems with iwgetwfobj

Vrar · 2006-04-11T20:23:37+00:00

Anyone else see anything like this? <id…

Vrar

Anyone else see anything like this?

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<wfregistry>
<workflows/>
<activeworkflows/>
<tasks/>
<activetasks>
<id v="32503"/>
<id v="32535"/>
<id v="32575"/>
<id v="32603"/>
<id v="32630"/>
<id v="32657"/>
<id v="33282"/>
<id v="33312"/>
<id v="33350"/>
<id v="33380"/>
<id v="33417"/>
<id v="33484"/>
<id v="33514"/>
<id v="36022"/>
<id v="36036"/>
<id v="37737"/>
<id v="37774"/>
<id v="37802"/>
<id v="37829"/>
<id v="38004"/>
<id v="38041"/>
<id v="38075"/>
<id v="38112"/>
<id v="38412"/>
<id v="39247"/>
<id v="40138"/>
<id v="40456"/>
<id v="40596"/>
<id v="40624"/>
<id v="41208"/>
</activetasks>
</wfregistry>

I can't find these tasks anywhere else in the system. Do they relate to some system process i don't know about? If not, how can i get rid of them? Every command line tool I've tried says these tasks do not exist, yet here they are from iwgetwfobj.

So confused, please help! Smiley Sad

Find more posts tagged with

Comments

Gregg Faus

You can find more more information these tasks by using the query syntax for the "iwgetwfobj" command. Or if you don't care, just exec the "imrmjob" command passing in the workflow_id like so:
iwrmjob 32503

Adam Stoller

Hmm - looks like maybe you have a corrupted workflow store.
(active tasks without active jobs)

I suggest you contact IWOV Support - my guess is they'll have you blow away the workflow store and re-create it - but it's best you work with them on it.

DavidMusser

I had something like this (but less of them) and I used the

>iwrmjob -s production.example.com 7734 as was mentioned before... for some reason I think I either had to type in the -s and server name, or if you use it and don't have it exact then it will say not found.

Fish could still be right in that there is perhaps corruption. I would remove them if possible, and then see if they happen again. Did the server crash or reset during a busy time?

-D

Anyone else see anything like this?

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<wfregistry>
<workflows/>
<activeworkflows/>
<tasks/>
<activetasks>
<id v="32503"/>
<id v="32535"/>
<id v="32575"/>
<id v="32603"/>
<id v="32630"/>
<id v="32657"/>
<id v="33282"/>
<id v="33312"/>
<id v="33350"/>
<id v="33380"/>
<id v="33417"/>
<id v="33484"/>
<id v="33514"/>
<id v="36022"/>
<id v="36036"/>
<id v="37737"/>
<id v="37774"/>
<id v="37802"/>
<id v="37829"/>
<id v="38004"/>
<id v="38041"/>
<id v="38075"/>
<id v="38112"/>
<id v="38412"/>
<id v="39247"/>
<id v="40138"/>
<id v="40456"/>
<id v="40596"/>
<id v="40624"/>
<id v="41208"/>
</activetasks>
</wfregistry>

I can't find these tasks anywhere else in the system. Do they relate to some system process i don't know about? If not, how can i get rid of them? Every command line tool I've tried says these tasks do not exist, yet here they are from iwgetwfobj.

So confused, please help!

kaalraa

I suggest both to contact IWOV support to cleaned up your workflow registry store as this displays only in case of corrupt workflows.

Vrar

Thank you all for the great feedback. Just an FYI to any who are interested. Interwoven suggested shutting down TeamSite after all current workflows have been completed, then renaming the "workflow" folder under the iw-store to "workflow.old".

After renaming the folder, start TeamSite up again and it creates a whole new workflow registry. The previous workflows are no longer available, but they can still be accessed if need be by shutting down TeamSite yet again and renaming the "workflow.old" back to "workflow".

Again thank you all for your help.

kaalraa

Thanks for sharing and would definitely appreciate the same. Smiley Happy

Thank you all for the great feedback. Just an FYI to any who are interested. Interwoven suggested shutting down TeamSite after all current workflows have been completed, then renaming the "workflow" folder under the iw-store to "workflow.old".

After renaming the folder, start TeamSite up again and it creates a whole new workflow registry. The previous workflows are no longer available, but they can still be accessed if need be by shutting down TeamSite yet again and renaming the "workflow.old" back to "workflow".

Again thank you all for your help.