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

how to debug Workflow engine

pranav

Hi all,

Is there any way or CLT to debug workflow engine.In my case all the workflow is getting stuck inside engine.iwjoberrors.log is showing something like this

Could not run "e:\iw-home/iw-perl/bin/iwperl" "e:\iw-home/local/bin/comment.ipl" for task 513; retrying in 1 minute

In our case workflows are getting triggered from outside application. I also tried to trigger a workflow using TS GUI and it throws me some kind of XML parser Error.

Hope to get some positive replies from you guys.
TS 6.5 SP1 on windows 2000 with SP4

-Regards,
Pranav

Find more posts tagged with

Comments

Migrateduser

Pranav,

Sets the Debug flag to On in the workflow template. When the job is instantiated, rather than running the actual job, a Debug output page is created.

It contains details about what the instantiated XML looks like plus what Perl variables were declared.

Thnaks RG

Adam Stoller

Could not run "e:\iw-home/iw-perl/bin/iwperl" "e:\iw-home/local/bin/comment.ipl" for task 513; retrying in 1 minute

Have you tried running, from the command line: e:\iw-home\iw-perl\bin\iwperl -w -c e:\iw-home\local\bin\comment.ipl to verify that the script compiles correctly?

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

computed_param_report.rptdesign

pranav

Hi fish,
finally a reply from you , I was waiting for your reply..

This is the result i am getting when i run this line into TS box

ERROR:00920: Object being looked up was not found
usage: e:\iw-home/bin/iwcallback [-h] [-v] [-s servername] taskID retCode [comment]
-h Print this message
-v Print version
-s servername Use servername as TeamSite server
taskID ID of task to call back
retCode Return code to select transition
[comment] An optional comment

As i said the same thing works perfect in other Env...The only difference is the Teamsitee Version..Other Env.s are based on TS6.1 SP1.This is happening when i am triggering the workflow from my portal(Plumtree) application.

Another scenario :::
When i try to submit a DCR (from Teamsite GUI, which in effect asks me to choose one workflow and i click one of the workflows) it gives me a parsing error.I am attaching the print screen document for that error.
I checked my available_templates.cfg and it seems that this XML is valid.Rightnow i don't have any clue about this error.Hope to get some suggestion from you .

-Regards,
Pranav

jbonifaci

Did you pass the job id, task id and area path to the external task? You need to append these to whatever your external command is:
E:/iw-home/iw-perl/bin/iwperl E:/iw-home/local/bin/comment.ipl <jobId> <taskId> <areaVPath>~Jeff

test3.rptdesign

AxisScale.png

pranav

Hi,

True jeff !! i havn't passed all the extra informations you have mentioned.Actually , as i said we are triggering the workflow from Portal and the first part itself gets stuck in TS box..

Have you read the second scenario i have mentioned ? why i am getting that error ? i am simply submitting one DCR and triggering the workflow.

-Pranav

pranav

Hi all,
Any new suggestions !!!!!!!!! I am not getting any clue.In fact i cleared all the other entries from available_templating.cfg except the default submit wft .Now i try to submit files from Workarea to staging using this default submit and then also i am getting the same error.
ERROR

Invalid workflow
XML parse error in WFworkflow.pm
no element found at line 1, column 0, byte -1 at e:\iw-home\iw-perl\vendor\lib\XML\parser.pm line 187

Your help in any form is highly appreciated.
-Pranav

iw_store

Hi,

Test the comment.ipl first by removing all WF related stuff, if it working fine then add WF related stuff inside it.

It seems with your error message there is some problem in WFT itself, try to figure it out by having a log file and print to it at particulkar break points.

As you removed all the entries from AT.cfg cross check it again.

If everythink is fine, analyze task by task it will help to figure out the error.

Edited by iw_store on 09/28/05 05:51 AM (server time).

pranav

Hi,

Thanks for your advice but i am facing some problem which is not at all related with the other task(s).Rightnow i am just trying to submit the files from Workarea to staging and then also i am getting this error.So something else is creating problem.Either it is the workflow engine or some internal details which i am not able to figure out till now.

Fish!! why don't you give your valuable suggestion(s) for this post...

-Pranav

Adam Stoller

Can you post the actual WFT, as an attachment? so we can look at the actual data within it to see if there are some potentially problematic errors in the code.
Also - are you getting the error before being prompted for entering information in the instantiation page (assuming there is one) or after you've filled in fields and are attempting to initiate the actual job?

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

pranav

Hi,
Finally a reply from Fish !!! great..

I am attching the workflow file with this mail.but again i repeating some thing....

>>> The same workflow is working perfectly in 2 other envs. the only differenceis that those two Envs are hosting TS6.1 with SP1

>>> Now forget the whole workflow thing.Lets take a simple thing.I am creating a branch then a new workarrea and then i create one file in that workarea.
Now when i try to submit this file to staging ,which is no where related to my IPLs or WFTs, i get this amazing error.which i have already included earlier in this post.
>> I have deleted all the entries from AT.cfg file except the one Default Submit

>> I have been working on TS 6.5 for few months and the same workflows were working perfectly till last week.

I am not at all able to figure out where exacltly is the problem.

>> Is it with the workflow engine which is not able create an instance of the workflow ?
>>Is it available_templates.cfg file, but it is looking perfect ?
>> Is it a known isue with TS 6.5

NOTE:: The attached WFT is not in a typical format because we are triggering the workflow from java application.

-Pranav

Adam Stoller

You seem to be constantly shifting the domain of the problem.
You started with problems with a portal-interactive workflow, then you said that you were having problems with the default submit workflow -- which is where I asked to see the actual WFT code - then you post an workflow file that clearly is *not* the default submit workflow.

I'm not looking to debug your custom workflow problems - I was simply trying to help you debug the problem you were seeing with the out-of-the-box workflow

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

pranav

Hi,

YES !!! i am shifting my post from Portal-interactive workflow to specific default submit workflow problem.But the motive behind this shifting is to reach at the core of the problem.I started with the portal-workflow thing then i shrinked the domain of the problem to teamsite internal discrepency because i am not even able to submit a simple file to staging which uses the default _submit.wft ,which by default comes up with teamsite installation.
when you asked me about the WFT i thought you still want to see that portal specific workflow.Because when i said default submit workflow i always meant the workflow which is by default at this location ,iw-home\local\config\wft\default(AND WE HAVE DONE NO CHANGES IN THIS WFT FILE).

Am i clear this time OR still confused in my problem definition ?

-Regards,
Pranav

mgal

For the error

Invalid workflow
XML parse error in WFworkflow.pm
no element found at line 1, column 0, byte -1 at e:\iw-home\iw-perl\vendor\lib\XML\parser.pm line 187

You could try the suggestions in this KB article

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=48721

For the perl not executing you could try putting a .exe for iwperl

e:\iw-home/iw-perl/bin/iwperl.exe e:\iw-home/local/bin/comment.ipl

Thxs,

Mohammed Gazal.

pranav

hI,

Bingo Gazal !!!! You hit the jackpot for me.This was the core of the problem.
Thank you so much for your help.

-Regards,
Pranav