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

iwsendmail got stuck

baskar

We have done migration from Teamsite 6.1 SP1 to Teamsite 6.7.1 SP2.
While testing the workflows all notification emails task are strucking.
I checked by copying the command property of that email task and found executing succesfully in command prompt login as user root permission.
As teamsite 6.7.1 uses utild services for running external tasks do i need to do any configuration to enable workflows to execute my email notification ipl.

Find more posts tagged with

Comments

baskar

I am sorry i have specified migartion to Teamsite 6.7.1 SP2.Its actually Teamsite 6.7.1.

Adam Stoller

We have done migration from Teamsite 6.1 SP1 to Teamsite 6.7.1 SP2.
While testing the workflows all notification emails tasks are strucking sticking or hanging.
I checked by copying the command property of that email task and found executing succesfully in command prompt login as user root permission.
As teamsite 6.7.1 uses utild services for running external tasks do i need to do any configuration to enable workflows to execute my email notification ipl.

When you executed it from the command - did you include all the implicit command line parameters?

What command are you using? iwsend_mail.ipl, iw_solution_mail.ipl, something else ?

Have you tried enabling debugging, or adding debugging code, to the script being used?

baskar

We are using iwsend_mail.ipl and made little customizations in it.

I tested in the command prompt with the parameters jobid,taskid,workareavpath and its running fine. But from the workflow job its getting hanged.

nipper

Then your code syntax is correct, however you are likely not running the correct routine for callback.

baskar

Well i am getting email as well as it callback properly the next task when i run from command prompt login as email task owner's userid .so i dont think the issue is with callback.

Adam Stoller

Well i am getting email as well as it callback properly the next task when i run from command prompt login as email task owner's userid .so i dont think the issue is with callback.

Can you post the actual <command .../> directive in your WFT where you're invoking the script?

Have you enabled debugging in your slightly modified (copy of?) iwsend_mail.ipl and within the iw.cfg (under the [iwsend_mail] section)?

Have you checked to see what's happening when it runs from the workflow?

Have you added additional debugging?

We can't tell what you have or haven't done because we're not in your environment having your problem - so the more you tell us, with more detail - the better chance that one of us might figure out what's going on without having to physically be there.

ReportTimeDuration.txt

SalesReport.rptdesign.txt

baskar

Please find the command i got using debugging feature in Workflow in the attachment text file

[url="http://172.12.200.10/iw'"/"]I set the debugging feature on in iw.cfg .but dont find any entry in log file.

My debugging code in sendmail also not working as the ipl has not been called.If i run from commnad prompt its updating corrcetly.

The email task just got hanged..Any idea .Is it becoz of // used in http:// as it is special chartacter for "" double quotes
[/url]

Adam Stoller

Please find the command i got using debugging feature in Workflow in the attachment text file

I set the debugging feature on in iw.cfg .but dont find any entry in log file.

My debugging code in sendmail also not working as the ipl has not been called.If i run from commnad prompt its updating corrcetly.

The email task just got hanged..Any idea .Is it becoz of // used in http:// as it is special chartacter for "" double quotes

Please try changing the task definition so that you have:[html]...

...

value="Pages need a technical intervention - please go to the CMT at http://172.20.218.10/iw"/>

...[/html]And see if that helps at all.
As for debugging - since you already have your own copy of the script (which should be located in some directory other than iw-home/bin) - go through it and add debugging lines:

...
   debug("print something here ...");
...

to help track what happens when the code is executed from the workflow.

samplesuppress.rptdesign