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

Task failing to execute

System

I have a workflow that is importing over 10000 files into an edition to be deployed to 5 destination servers. The workflow is 10 steps. On the 4th task it is supposed to publish the edition to ControlHub. This process fails to initiate. I am running ControlHub 2.1 and Opendeploy 6.1. I am recieving the following errors in the following logs:
IWTrace.log: ERROR: CreateProcess failure - 206

IWEvents.log: [Wed Feb 28 14:08:51 2007] cuc\dlarsen master TaskInvokeExternal BCA Staging Deployment 0x1d248 Publish_Edition 0x1d250

IWJobErrors.log: [Wed Feb 28 14:00:50 2007] Could not run C:\Interwoven\CAPS\ControlHub\iw-perl\bin\iwperl C:\Interwoven\CAPS\ControlHub/local/bin/cmsPublishEdition.ipl for task 119376; retrying in 1 minute

The command being executed during the task is: . This .ipl is used through all my workflows without problems until this recent issue. Any help is appreciated.

David L.

Find more posts tagged with

Comments

nipper

de ja vu all over again.

I am seeing the exact same issue using the default configurable deployment. I have not changed it in months. All of a sudden the deployments are not working.

The job hangs in the external task.

If I run the external task from the command line (providing the job, task & area) then the deployemtn works, callback works and job completes.

What OS & rev of TS ?

I am on Win2k TS 6.7.1

I also use the same WF on another server, TS 6.5 SP2 and it works great.

I do suggest you file with support.

Andy

nipper

I have a workflow that is importing over 10000 files into an edition to be deployed to 5 destination servers. The workflow is 10 steps. On the 4th task it is supposed to publish the edition to ControlHub. This process fails to initiate. I am running ControlHub 2.1 and Opendeploy 6.1. I am recieving the following errors in the following logs:
IWTrace.log: ERROR: CreateProcess failure - 206

IWEvents.log: [Wed Feb 28 14:08:51 2007] cuc\dlarsen master TaskInvokeExternal BCA Staging Deployment 0x1d248 Publish_Edition 0x1d250

IWJobErrors.log: [Wed Feb 28 14:00:50 2007] Could not run C:\Interwoven\CAPS\ControlHub\iw-perl\bin\iwperl C:\Interwoven\CAPS\ControlHub/local/bin/cmsPublishEdition.ipl for task 119376; retrying in 1 minute

The command being executed during the task is: . This .ipl is used through all my workflows without problems until this recent issue. Any help is appreciated.

David L.

This may help you.

You have iwperl not iwperl.exe

Somehow I got an empty iwperl file. No .exe. Removed that file and it worked .

Andy

Migrateduser

I am running W2K3 sp1. We are running ControlHub 2.1 instead of Teamsite, but Controlhub is based on Teamsite.

David

nipper

Check for a file iw-perl/bin/iwperl without the .exe.

May be a zero length file

If so, remove it

Migrateduser

I actually saw the thread for your instance and hoped that would be my problem as well, but there is no perl file in the bin directory or otherwise. In the perl of the workflow file it defines the value of where perl is as this:

my $iwperl = $iwhome . "${dirsep}iw-perl${dirsep}bin${dirsep}iwperl";

I know that in perl the "." is a special character. How do I add the ".exe" into the path without **** up the perl.

David

Adam Stoller

I actually saw the thread for your instance and hoped that would be my problem as well, but there is no perl file in the bin directory or otherwise. In the perl of the workflow file it defines the value of where perl is as this:

my $iwperl = $iwhome . "${dirsep}iw-perl${dirsep}bin${dirsep}iwperl";

I know that in perl the "." is a special character. How do I add the ".exe" into the path without **** up the perl.

David

You can simply add a ".exe" to the end of that definition - and assuming there is an iwperl.exe in your IWHOME/iw-perl/bin directory - you should be fine.

Personally, I'd get rid of those ${dirsep}'s and replace them with '/'s - but that's me.

Migrateduser

I added the .exe to the workflow command for iwperl. It still has the same issue as before. Does anyone know what the error in the IWTrace.log stands for?:
IWTrace.log: ERROR: CreateProcess failure - 206

I have found a few references to other error codes but not for 206. Can someone point me to a reference for those error codes?

David

nipper

I had talked to someone in support and this is a rather generic error.

Can you put the WF in debug mode, open a shell and run the command from the DOS shell ?

copy and past the entire line, appending the workflow ID, task IF and area /default/main/../WORKAREA/mine of a job that is "stuck" in that task.

Post any errors