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

Fix: CreateProcess failure - Working around External Task with long file list

Gregg Faus

I was encountering Windows CreateProcess errors (errCode=87) when dealing an External Task with a long list of arguments. Our standard workflow contains the "unlock.ipl" task where all files in the workflow are unlocked through an external task. The problem is when this list is too long, the job will get stuck because excessive argument count.

The workaround/fix is to ensure you have the following setting in your iw.cfg (under [Workflow]):
external_task_add_filelist=false

Just an FYI.

Find more posts tagged with

Comments

nipper

That is caused by a couple different things. If it works for a few files and fails for a bunch, then you have the right fix.

People also get this error when they create an iwperl file in addition to the iwperl.exe file.

ISCBorisB

I was encountering Windows CreateProcess errors (errCode=87) when dealing an External Task with a long list of arguments. Our standard workflow contains the "unlock.ipl" task where all files in the workflow are unlocked through an external task. The problem is when this list is too long, the job will get stuck because excessive argument count.

The workaround/fix is to ensure you have the following setting in your iw.cfg (under [Workflow]):
external_task_add_filelist=false

Just an FYI.

Yep... Note that this setting is global, all Workflows that still use File List arguments must be fixed.
You may want to take a look at some discussion [post=132526]here[/post]

Gregg Faus

Yep... Note that this setting is global, all Workflows that still use File List arguments must be fixed.
You may want to take a look at some discussion [post=132526]here[/post]

Good to know for others. Our only workflows using an external task use the unlock.ipl script provided by IWOV which already extracts files from workflow.

Funny that in 8 years running TeamSite, we have just now starting seeing this. That is unless the default changed from false to true at some point Smiley Happy

Adam Stoller

Good to know for others. Our only workflows using an external task use the unlock.ipl script provided by IWOV which already extracts files from workflow.

Funny that in 8 years running TeamSite, we have just now starting seeing this. That is unless the default changed from false to true at some point

No - the default never changed from its backwards-compatible-but-error-prone setting.

A lot of scripts were written that needlessly / redundantly pulled arguments off the command line (@ARGV) as well as extracted the same information from the job and/or task objects created via the first arguments on the command line - in such cases, those scripts will work regardless of the setting as long as the list of files is not too long.

In all other cases, you would need to make sure that the scripts are properly adjusted to extract information from the task object.