TS6.5 CCPro - cgitask - error opening pipe?

Environment

Gag - I'm not sure if this is because I'm woking on Windows for the first time in a while - but I'd like to think that's the source of the problem...

I have a cgitask defined with: <command v="****_wf_editdcr.cgi"/>I've created iw-home/httpd/iw-bin/****_wf_editdcr.ipl and copied show_env.cgi to ****_wf_editdcr.cgi in the same directory.
My cgitask script is essentially a "dummy" script right now - trying to get past this problem (below) - the script looks like this:#!c:/Interwoven/TeamSite/iw-perl/bin/iwperl
print qq[Content-type: text/html\n\n];
print qq[Hello\n];When I try to Start Input Task from the CCPro UI - I get the following message:
TeamSite : Wrapper
Error: Error trying to open a pipe to
C:\Interwoven\TeamSite\httpd\iw-bin\****_wf_editdcr.cgi(480).

There's nothing in any of the log files as far as I can tell (nothing meaningful in iwevents.log other than saying a task transition took place to get to my cgitask; nothing useful in iwui/servleted_out.log, and absolutely nothing in iwui/servletd_err.log)

If I change my wft to run show_env.cgi - it runs just fine -- so the show_env.cgi wrapper binary that I copied as a ****_wf_editdcr.cgi should also be fine. I even checked with dir /x to make sure that the wrapper and perl script line up: Directory of C:\Interwoven\TeamSite\httpd\iw-bin

02/18/2005 12:07 PM 716,800 ****_~2.CGI ****_wf_editdcr.cgi
02/18/2005 01:04 PM 7,079 ****_~2.IPL ****_wf_editdcr.iplI then tried moving my IPL file aside and copied tt>show_env.ipl to ****_wf_editdcr.ipl and I get the same error message as before .. so it seems it has to be the wrapper that's broken - but I can't figure out how.

We do have cygwin installed on this machine - and I checked with ls -l and sum and the binary wrappers are identical:iw-bin > ls -l show_env.cgi ****_wf_editdcr.cgi
-rwx------+ 1 Administrators None 716800 Feb 9 02:35 show_env.cgi
-rwx------ 1 ghoti None 716800 Feb 18 12:07 ****_wf_editdcr.cgi
iw-bin > sum show_env.cgi ****_wf_editdcr.cgi
44747 700 show_env.cgi
44747 700 ****_wf_editdcr.cgiAnyone have any ideas to offer?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

Johnny

this is a real long shot... windows was a while ago but...

do cgi's need to be executable in their own right?..

as in spoon feeding the perl command in a batch/cmd file. ?

or/and i *think* apache does honor the shebang line.. so check that too...

I could be totally off.

John Cuiuli

Michael

hmm a bit of a stab in the dark sorry...

you say that if you use show_env.cgi and show_env.ipl it works but if you copy both these files and try and use them it doesn't work? that is a bit bizarre!

any chance it could be permission related? if you check out the security tab are they both permissioned the same way?

can't think of anything else sorry.

cheers
Michael

Adam Stoller

Well - I figured out a way around it - and it's actually a good solution - but I'm still confused why my original attempt failed like that.

Instead of<command v="****_wf_editdcr.cgi"/> I changed it to <command v="****_wf_editdcr.ipl"/> - and it worked! so much for needing the wrapper.

I'll remain confused about the original method not working - but I'm happy with the alternative means of operation...(give me Unix!)
Thanks anyway.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

I think the original failed because of permissions...in the "ls -l" listing, the original show_env.cgi is owned by Administrators and has a "+" at the end of the attributes...doesn't look like an equivalent (cp -p) copy...I would have thought a windows copy would have made an actual full copy, not changed properties of it...did you try copy-pasting it in place, so it defaults to "Copy of show_env.cgi" and then rename it?

as for why you need the wrapper at all, I haven't got an answer for that...all my cgi tasks work fine using:
<command='/iw-bin/<path-to-file>/filename.cgi'>

maybe the wrapper is to translate cgi parameter passing to perl script parameters? for those who only know how to write strictly perl .ipl scripts?

-Rori

Adam Stoller

The reason the wrapper is there is for historical purposes (which I had forgotten).
Pre 5.x - TeamSite [on Windows] relied on IIS [or some other customer-supplied webserver] to manage things like cgitask scripts - and IIS refused to honor ".ipl" as an executable program and refused to honor non-binary ".cgi" files - so the wrapper was created to act as a binary mediary which IIS would accept and then it, in turn, would simply exec the perl script of the same name as the wrapper (with .cgi => .ipl).

This issue pretty much went away with 5.x and the introduction of iw-webd (Apache) being used by TeamSite to manage the UI.

I *thought* I could just create the ".cgi" script and use that - but it didn't seem to work - so I opted back to using the wrapper - which also didn't work (and you might be right about why) - and then I just tried specifying the ".ipl" file (which was now .ipl because I had tried the wrapper approach) and that worked fine - and, in my opinion is a better solution than using the wrapper anyway.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com