iw solution email.ipl timing out?

Hi guys

it seems that 'iw_solution_email.ipl' is timing out when called from an 'email an approver' workflow.

-Entry: 'TaskTimedOut' in iwevents.log after about 1 minute. Then the task dissappears from the author (who initiated it) workflow tab in gui

-Nothing written in script's default log 'iw_solutions_debug.log' (in debug and verbose mode). So it seems it didn't even get called.

-The command works when called from command line.

-If I use the alternate script 'iwsend_mail.ipl' (with same permissions) it works, so it seems teamsite can call external scripts

Teamsite version: 6.5

Any ideas?

Thanks all

Find more posts tagged with

Comments

Adam Stoller

Hi guys

it seems that 'iw_solution_email.ipl' is timing out when called from an 'email an approver' workflow.

-Entry: 'TaskTimedOut' in iwevents.log after about 1 minute. Then the task dissappears from the author (who initiated it) workflow tab in gui

-Nothing written in scripts default log 'iw_solutions_debug.log' (in debug and verbose mode). So it seems it didn't even get called.

-The command works when called from command line.

-If I use the alternate script 'iwsend_mail.ipl' (with same permissions) it works, so it seems teamsite can call external scripts

Teamsite version: 6.5

Any ideas?

Thanks all

You'd have to enable debugging within the script and, well, debug the process. There are any number of possible reasons why this might happen, but it's pointless to speculate when you can debug the problem in situ and we cannot.

spyr79

Thanx.

I assume you meant 'enable debugging in workflow', not within the script.

I have enabled logging within the script but nothing gets written (my 2nd point). It seems that the script isn't even called

anyway, will do

nipper

Thanx.

I assume you meant 'enable debugging in workflow', not within the script.

I have enabled logging within the script but nothing gets written (my 2nd point). It seems that the script isn't even called

anyway, will do

Just to make certain everything is OK, you should verify there are no issues with the way it is being called.

Put the WFT in debug mode, get the exact command line that you are trying to invoke and run it from the DOS shell with the correct parameters, something like

...iwperl.exe .../iwsolutionsemail.ipl WF_Job_# WF_Task_# WA parameter1 parameter2

ScatterPlotColors.zip

Adam Stoller

Thanx.

I assume you meant 'enable debugging in workflow', not within the script.

I have enabled logging within the script but nothing gets written (my 2nd point). It seems that the script isn't even called

anyway, will do

I actually meant debugging the script - but I notice you didn't mention what OS you're on. If you're on Windows, are you correctly preceding the script name with the fully qualified path to iwperl and verify that iwperl is not a 0-length file (which seems to have occurred in various installations)?

spyr79

Solution found:

Access right issue. Had to change iw.cfg:

from
webserver_uid=nobody
to:
webserver_uid=root

even though the 'iw_solution_email.ipl' and 'iwsend_mail.ipl' had full access rights for all

OS was Solaris, btw

Thanx all