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

TeamsiteWrappererror- CgiTask

manju166

I came across an error when trying to insert a cgi-task in the workflow, I am on WindowsNT and Version 5.0.1

Error trying to open a pipe to d:\iw-home\httpd\iw-bin\wfdelay_task.cgi[1]

<cgitask name="DelayDeployment"
start="f"
owner="__TAG__('iw_user');"
description="User Delays Deployment process."
lock="f"
immediate="t">
<areavpath v="__INSERT__($area_vpath);"/>
<successors>
<successorset description="Done">
<succ v="DeploytoProduction"/>
</successorset>
</successors>
<command v='"d:\iw-home/httpd/iw-bin/wfdelay_task.cgi"'/>
<activation>
<pred v="SubmittoStaging"/>
</activation>
</cgitask>

I tried to give the command without path but still I came across the error. Please look at the attachment for the detail error.
<command v='"wfdelay_task.cgi"'/>

Any help is appreciated.
Thankyou

Edited by manju166 on 10/23/02 08:26 AM (server time).

Find more posts tagged with

Comments

Migrateduser

What's the specific error you got, and at what point in your execution of this workflow did you get the error?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

manju166

I got this error after Editor Approves the workflow and submits it to staging and than the workflow tries to open the wfdelay_task.cgi.

A blank screen opens and the error pops up saying

Teamsitewrapper
Error:Error trying to open a pipe to d:\iw-home\httpd\iw-bin\wfdelay_task.cgi

Thanks for the response

james1

> Please look at the attachment for the detail error.

I see no attachment to your message...?

What is wfdelay_task.cgi? Is it a Perl script?

-- James

--
James H Koh
Interwoven Engineering

Migrateduser

FYI...

I don't use wfdelay_task.cgi at all. My workflow calls wfdelay_change_status.cgi directly. Try that. It's possible that wfdelay_task.cgi is not coded properly to be a cgitask script.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

manju166

James, Ths script i am trying to include in CgiTask is cgi script.
the error is

Teamsitewrapper
Error:Error trying to open a pipe to d:\iw-home\httpd\iw-bin\wfdelay_task.cgi

Dave, I tried to include the wfdelay_change_status.cgi.
I still get the above error.

thankyou for response
Manju

manju166

I think I know the problem, the cgi file is created in WinNt env.
If i right click and look at the properties, the file name in dos prompt looks like WFDELA~1.CGI, I think the [1] character in my error is coming from the filename.
What I want to say is the file is not getting stored as typical .cgi file and thats why it is unable to locate the file.

Anyone has a idea as why this happens and if possible any solution appreciated.

The error I am getting is below and the [1] character at the end of the line

Teamsitewrapper
Error:Error trying to open a pipe to d:\iw-home\httpd\iw-bin\wfdelay_task.cgi[1].

Thanks
Manju

Edited by manju166 on 10/23/02 01:24 PM (server time).

Migrateduser

I can't help you with NT issues. Those scripts were written to run on Solaris. If there are customizations needed to make them run on NT, you're on your own. Sorry.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Adam Stoller

You have:
<command v='"d:\iw-home/httpd/iw-bin/wfdelay_task.cgi"'/>
in your cgitask - the path for the command is *always* and *only* within the iw-home/httpd/iw-bin directory and you aren't supposed to specify it.

Please try changing it to:
<command v='"wfdelay_task.cgi"'/>
and see if that works.

--fish
(Interwoven, Curriculum Development)

manju166

I tried to give the command with out path but no use, i still get the same error,
i wrote a simple cgi file which shows time and than deploys to production, but i still get the error, i tried to call a existing working perl code from cgi task but i still get that error.
I never wrote a cgitask earlier, is my cgi task have a syntax error.

I tried to execute from the server
http://teamsiteserver/iw-bin/wfdelay_change_status.cgi
and it works.

Does anyone have a clue as why this error occurs

Adam Stoller

I never wrote a cgitask earlier, is my cgi task have a syntax error.

I think we were all taking it on face value that you knew how to write a CGI script - in order to help narrow down the problem, try replacing your command element with:

< command v="show_env.cgi"/>

and see if that works. (it will not transition to the next task after running, but it should execute in a new browser window like a cgitask script is expected to)

If that works - then the problem is with your script.

If that doesn't work, I suggest you contact Interwoven Support so that they can work with you on resolving the problem.

--fish
(Interwoven, Curriculum Development)

manju166

I opened a call with Interwoven support, Thanks for your help

manju166

After I opened the call with Interwoven, they helped me to solve the problem and they asked me to do the following steps for .cgi files in windows NT enviornment.

1)rename <iw-home>/httpd/iw-bin/wfdelay_change_status.cgi to
<iw-home>/httpd/iw-bin/wfdelay_change_status.ipl;
2) copy <iw-home>/httpd/iw-bin/show_env.cgi to
wfdelay_change_status.cgi;
3) retest it again.

This solved my problem .

wngg2

Hi ghoti,

In order to manage all of my cgi scripts for my clients, I created sub-directories under iw-home/http/iw-bin. And in my CGI task, I added my script to the "command" tag as follow:

<command v='/iw-bin/clientA/client.cgi'/>

It worked fine when I kicked off the cgi task in Webdesk Pro view, but when I kicked off the task in Webdesk, I got the following error message:

Teamsitewrapper
Error:Error trying to open a pipe to d:\iw-home\httpd\iw- bin\clientA

However, when I move my cgi script back to the root of iw-bin and change the path on my cgi task accordingly, it worked fine for both Webdesk Pro & Webdesk.

Should I open a support case for this? Thanks.

Adam Stoller

You can - but be aware that putting scripts in sub-directories under iw-bin/ has never been officially supported - so the fact that it seems to work in some cases is more luck than anything else.

--fish
(Interwoven Senior Technical Consultant)

bibulle

For me, it seems to be a bug....(we have a lot of differents projects working in this directory)

Will it be corrected in futur release ??

Thanks

Migrateduser

I believe it is documented that all CGI scripts must be in the iw-home/httpd/iw-bin path. Therefore, it could not possibly be a bug. It certainly could be a feature request, however.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

Manju, instead of sub-dirs, try using specific file naming conventions to organize iw-bin. We (mostly) prefix all our files with "iw". You could prefix yours with something else. At least that way, you'd see all yours listed together in the directory.

bw

Bob Walden [bob.walden@interwoven.com]
Interwoven Education Group
IM: Yahoo, MSN bob_walden

manju166

HI Bob,

user "bibulle" continued my post for his problem with cgi task, its not my post anymore, my problem was fixed with interwoven support

thanks for your response
manju

Migrateduser

I had the same problem of not being able to start .cgi scripts from custom menus and I solved it with this handy hint from manju.
I was just wondering why this strange solution exists? Is it something to do with running on W2k?

Curiously

/Nick