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

Lille Help - Stuck Workflow Job

Captain_Moor

Hi there guys & girls, I am new to this forum and relativly new to teamsite itself.

Any help that you can offer would be greatly appreicated.

We are running iwserver: 6.1.0 Build 51214 Interwoven 20050810 on Win2003.

What the issue is that we have a task that is being pushed through a "No Approval Workflow", but for some reason is not being deployed.

Upon investigating this issue in the iwjobserrors.log all I am getting is:

[Thu May 08 14:50:35 2008] Could not run d:/iw-home/iw-perl/bin/iwperl d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl for task 1796218; retrying in 1 minute

Now the task in question is for around 220 PDf files, is there a limit to the amount of Items that can be deployed at one time?? Or am I looking in the wrong place.

Like I said I am fairly new to TS and any help you can give me would be great.

Thanks,

Tim

Find more posts tagged with

Comments

chris__d

Well, your system may be different to ours, but we find that it is appropriate to send out smaller amounts of files in a number of workflows, rather than a large amount of files in one go.

Are you having success in deploying smaller amounts of files with the workflow?

Nikunj

Hi,
First check your ipl is it working fine.
1. Check if your ipl have no compilation error.
e.g iwhome\iw-perl\bin\iwperl -c d:/iw-home/iw-perl/bin/iwperl d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl

Output shud be status ok..
2. Now try running your ipl from cmd.. pass jobid and taskid as paramater.
e.g.
iwhome\iw-perl\bin\iwperl -c d:/iw-home/iw-perl/bin/iwperl d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl 123 1234
Hope this helps you out..

msrinivas

Hi there guys & girls, I am new to this forum and relativly new to teamsite itself.

Any help that you can offer would be greatly appreicated.

We are running iwserver: 6.1.0 Build 51214 Interwoven 20050810 on Win2003.

What the issue is that we have a task that is being pushed through a "No Approval Workflow", but for some reason is not being deployed.

Upon investigating this issue in the iwjobserrors.log all I am getting is:

[Thu May 08 14:50:35 2008] Could not run d:/iw-home/iw-perl/bin/iwperl d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl for task 1796218; retrying in 1 minute

Now the task in question is for around 220 PDf files, is there a limit to the amount of Items that can be deployed at one time?? Or am I looking in the wrong place.

Like I said I am fairly new to TS and any help you can give me would be great.

Thanks,

Tim

There could be a 0 byte file called iwperl (not iwperl.exe) in d:/iw-home/iw-perl/bin.

If so stop all TS services, delete that 0 byte file and then edit your wft for:

d:/iw-home/iw-perl/bin/iwperl d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl

to

d:/iw-home/iw-perl/bin/iwperl.exe d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl

Restart TS services.

HTH

Adam Stoller

Hi there guys & girls, I am new to this forum and relativly new to teamsite itself.

Any help that you can offer would be greatly appreicated.

We are running iwserver: 6.1.0 Build 51214 Interwoven 20050810 on Win2003.

What the issue is that we have a task that is being pushed through a "No Approval Workflow", but for some reason is not being deployed.

Upon investigating this issue in the iwjobserrors.log all I am getting is:

[Thu May 08 14:50:35 2008] Could not run d:/iw-home/iw-perl/bin/iwperl d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl for task 1796218; retrying in 1 minute

Now the task in question is for around 220 PDf files, is there a limit to the amount of Items that can be deployed at one time?? Or am I looking in the wrong place.

Like I said I am fairly new to TS and any help you can give me would be great.

Thanks,

Tim

Have you tried running this workflow process with fewer files (like say 5 or 10)?
If that doesn't work - the problem is probably with the script.
If that works - the problem is probably with your iw.cfg file (and perhaps your script - depending on how it was written) - you'll want to add the following line to your iw.cfg:

...
[workflow]
exteranal_task_add_filelist=false
...

Then run an iwreset. As long as your script retrieves its list of files from a TeamSite::WFtask object instead of from @ARGV - you should be fine.

ISCBorisB

[Thu May 08 14:50:35 2008] Could not run d:/iw-home/iw-perl/bin/iwperl d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl for task 1796218; retrying in 1 minute

What is the "lock" attribute of the stuck task? If attached Files are already locked WF Engine will try again and again(after some timeout), possibly indefinitely.

If that's the case, set 'lock' to false and use dedicated 'locktask' instead. This way you can determine locking Success or Failure and
fork your Workflow to process these outcomes accordingly.

Captain_Moor

Well, your system may be different to ours, but we find that it is appropriate to send out smaller amounts of files in a number of workflows, rather than a large amount of files in one go.

Are you having success in deploying smaller amounts of files with the workflow?

Hi there Chirs_D, thanks for your response. Yes currently our workflow is working fine apart from these occurrences of failures with large amounts of files.

When the user deploys each file independently they are all being processed correctly.

Thanks for your comments

Captain_Moor

Hi,
First check your ipl is it working fine.
1. Check if your ipl have no compilation error.
e.g iwhome\iw-perl\bin\iwperl -c d:/iw-home/iw-perl/bin/iwperl d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl

Output shud be status ok..
2. Now try running your ipl from cmd.. pass jobid and taskid as paramater.
e.g.
iwhome\iw-perl\bin\iwperl -c d:/iw-home/iw-perl/bin/iwperl d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl 123 1234
Hope this helps you out..

Hi Nikunj, thanks for your help. I have run the scripts on our system and they have completed without error. However there has been now output to screen saying "Status O.K". Not sure on wither you where meaning this would be visible or not.

I have then tried the same command with the Task and Job ID from the command line but there was once again no screen output and the Job is still sitting there.

We are running an much earlier version of TS, so not sure wither this would be causing these issues.

Thanks for your help mate.

Captain_Moor

There could be a 0 byte file called iwperl (not iwperl.exe) in d:/iw-home/iw-perl/bin.

If so stop all TS services, delete that 0 byte file and then edit your wft for:

d:/iw-home/iw-perl/bin/iwperl d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl

to

d:/iw-home/iw-perl/bin/iwperl.exe d:/iw-home/custom/ccc/bin/wfRouteFileAttach.ipl

Restart TS services.

HTH

Thanks msrinivas, but all files within that directory are above 1kb and all iwperl files have correct extentions.

Thanks for your help with this issue.

Captain_Moor

Have you tried running this workflow process with fewer files (like say 5 or 10)?
If that doesn't work - the problem is probably with the script.
If that works - the problem is probably with your iw.cfg file (and perhaps your script - depending on how it was written) - you'll want to add the following line to your iw.cfg:
...
[workflow]
exteranal_task_add_filelist=false
...
Then run an iwreset. As long as your script retrieves its list of files from a TeamSite::WFtask object instead of from @ARGV - you should be fine.

Hi there Ghoti, the workflow does indeed work as intended with flew files attached.

But before I make the recomended alterations to the iw.cfg can I ask what exactly this is setting and what implications this may have.

Live I said earlier, I am new to Teamsite and have little Senior Support here.

Thanks for your help guys, its all much appreicated.

Adam Stoller

Hi there Ghoti, the workflow does indeed work as intended with flew files attached.

But before I make the recomended alterations to the iw.cfg can I ask what exactly this is setting and what implications this may have.

Live I said earlier, I am new to Teamsite and have little Senior Support here.

Thanks for your help guys, its all much appreicated.

The default behavior of workflow is to put every single file attached to the job on the command line when invoking the externaltask script -- when you have a large number of files associated with the job, you tend to go beyond the limits of the OS for either number of command line arguments or total length of command line (or both) - by making the setting I suggested, the files no longer get added to the command line.

In the script code you would need to see if you are doing something like this:

my ($jobid, $taskid, $areavpath, @files) = @ARGV;

and change it to something like this:

my ($jobid, $taskid) = @ARGV;
#... create task object, ensure it is valid ...
my $areavpath = $task->GetArea();
my @files = $task->GetFiles();

You need to make sure that both changes exist (i.e. both the iw.cfg setting and the externaltask script code) - and you need to run iwreset after making the change to the iw.cfg

Nikunj

Hi Ghoti,
From where can we get all this details like:
"exteranal_task_add_filelist"

Because i guess pdfs doesnt give much information on this.
Thanks in advance. It wuld be really helpful..

Adam Stoller

Hi Ghoti,
From where can we get all this details like:
"exteranal_task_add_filelist"

Because i guess pdfs doesnt give much information on this.
Thanks in advance. It wuld be really helpful..

It's covered, at least in some detail, in the 6.5 SP1 and newer Workflow Developer's Guides - but it is also documented in IWHOME/etc/iw.cfg.example if I recall correctly.

Nikunj

ya i had read that pdf but did get much from it... Smiley Sad

..
Thanks...actually this forum is for all those stuffs only...:d..