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; } } }

WFT task not transitioning

kidkurious

Hi,
TS6.7.1. sp1 windows.
When a job is created and encounters the first external task it hangs and does not display any error, happens on all WF. It seems not to transition to the next task, no changes were made to the system and the WF worked fine previously.
I have tried to run the task via CLT and still not working.

Any ideas were to look?

Find more posts tagged with

Comments

AkhileshK

Please use first external task with log file and check in log file.
I hope, you will get some clue....

curiousmaverick

look how callback is getting used there.

Migrateduser

Put some logging (a simple print out to a new file would work) into the first section of code of your external task. This will allow you to see if it's really getting called. If it's writing to your file, then keep moving your print outs further down the code to find out where it's stopping. You're going to have to do some digging and testing on your own unless you're willing to post the code for us to see.

kidkurious

thanks for all the suggestions so far.

I dont think its the code or the way call back are being called. Because all code worked fine previously. And different types of tasks are being hung. I think it has to do with the WF module not passing the details to next task.

kidkurious

for example when trying to to execute unlock task, the task tries to determine if the task is valid (using teamsite::WFtask IsValid()), and we get an error:no tag found

ISCBorisB

...all code worked fine previously... different types of tasks are being hung

It sounds like you may have a problem with some shared Module(s), including possibly TemaSite Modules.
Take any external task Script that gives you troubles and try to compile it: "iwperl -c ScriptPath" What does it show?

kidkurious

Ran the cmd with the following results
F:\Apps\Interwoven\iw-home\custom\bin>iwperl -c wf_unlock.ipl
wf_unlock.ipl syntax OK

ISCBorisB

Ran the cmd with the following results
F:\Apps\Interwoven\iw-home\custom\bin>iwperl -c ScriptPath
Can't open perl script "ScriptPath": No such file or directory

By the "ScriptPath" I actually meant "Full Path to your problematic External Task Script including File Name and Extension". Clear?

kidkurious

sorry posted wrong line

F:\Apps\Interwoven\iw-home\custom\bin>iwperl -c wf_unlock.ipl
wf_unlock.ipl syntax OK

ISCBorisB

sorry posted wrong line

F:\Apps\Interwoven\iw-home\custom\bin>iwperl -c wf_unlock.ipl
wf_unlock.ipl syntax OK

Are you attaching DCRs to your WF? Is everything correct with DCRs Meta Data (aka "Tagging")?
Take a look at this KB Article: ERROR:02015 - No tag found

kidkurious

Have tried to submit files with and without EA, meta tags, and both still dont work.

Adam Stoller

How many active (potentially hung) jobs do you have in your system? E.g.: about how many lines of output do you see when you run iwgetwfobj from the command line?
It is possible that you have a corrupted workflow store and you may have to remove it and let it start from scratch (this will cause all existing jobs to be removed from the system)

kidkurious

All jobs in the system cannot process external tasks. When it gets to the first external task it just stops there. No obvious error in the logs either.

iwgetwfobj appears to return a complete object (I have attached file of output) the problem we are having is that no task can transition to the next task, no variables get passed to the next task, although the WF object appears to be created.
How do we repair a corrupted workflow store?

any other ideas?

ISCBorisB

All jobs in the system cannot process external tasks. When it gets to the first external task it just stops there. No obvious error in the logs either.

iwgetwfobj appears to return a complete object (I have attached file of output) the problem we are having is that no task can transition to the next task, no variables get passed to the next task, although the WF object appears to be created.
How do we repair a corrupted workflow store?

any other ideas?

There are several distinctly different Scenarios

1. WF Engine can not instantiate or execute a Workflow. That does not seem to be your case, WFs instantiate and
you can control them from GUI or CLT. Correct?

2. WF Engine can not start an External Task. Some cases I've seen:
- Incorrect locking. If ET "lock" attribute is set and attached File(s) are already locked WF Engine will try again
and again(after some timeout), possibly indefinitely.
- ET Command is corrupt. Depending on your WF settings that may happen if too many Files are attached to WF.
- WF Engine can not spawn an ET process, usually because of the low Swap memory (Windows)

3. WF Engine can not transition External Task. That practically always means ET Code problems, syntactical or run-time.

So - do you know if you are experiencing case 2 or case 3? Create a test ET that only reports and transitions, nothing else.
Run it within some WF without any Files attached. Does that work? Does ET report "I've got activated"? Does it transition
correctly?

tirrudev

External Workflow Tasks Not working in TeamSite 6.7

A new feature of TeamSite 6.7 is that external workflow tasks can run as a user instead of SYSTEM. In this case, if a user does not have permission to execute the external Perl scripts, then they should be executed as SYSTEM. This article explains how to execute external tasks as SYSTEM from TeamSite 6.7.

For the external tasks to be executed as SYSTEM in TeamSite 6.7, you need to set the following in the [authentication] section of the iw.cfg file:

[authentication]
impersonate_without_password=false

After updating iw.cfg, run iwreset -a to reset the services.

For TeamSite 6.71 Service Pack 1, please see knowledge base 60319.

Refer https://customers.autonomy.com/supp...oven/55773.html

Migrateduser

External Workflow Tasks Not working in TeamSite 6.7

A new feature of TeamSite 6.7 is that external workflow tasks can run as a user instead of SYSTEM. In this case, if a user does not have permission to execute the external Perl scripts, then they should be executed as SYSTEM. This article explains how to execute external tasks as SYSTEM from TeamSite 6.7.

For the external tasks to be executed as SYSTEM in TeamSite 6.7, you need to set the following in the [authentication] section of the iw.cfg file:

[authentication]
impersonate_without_password=false

After updating iw.cfg, run iwreset -a to reset the services.

For TeamSite 6.71 Service Pack 1, please see knowledge base 60319.

Refer https://customers.autonomy.com/supp...oven/55773.html

Working link is https://customers.autonomy.com/support/secure/docs/FAQ/Interwoven/55773.html.

kidkurious

Ok. We have resolved the issue. It appears the iwutild_cmdout.log had grown to a size of >4Gb and as a result was stalling the workflow engine.
Once we cleared out the file everything started working again.

But the file is growing at an extremely fast pace (1.6Gb in two days).

Does anybody know if anything has changed in the logging process in 6.7.1? Since we only experiened this problem after upgrade from 6.5 to 6.71 sp1 two weeks ago.

Thanks everyone for all the suggestions!

Adam Stoller

Do you see certain log messages showing up a lot?
I'm running 6.7.2 SP2 + P1 and notice that every time we run 'iwstat' the output is logged in iwutild_cmdout.log.
Also my iwat trigger script seems to put messages in that log as well (hmm, this may be something for me to look into more carefully...)