Tasks not getting completed on WF instantiation

I am working on TS 6.5.On Workflow instantiation there are no tasks in the completed tasks pane.My very first task is the 'Deploy to Staging' external task & it gets stuck up over there & comes out only on timeout.This is happening in all the Workflows on my development environment.But these workflows are working fine on production environment.
Basically task transitioning is not happening & even the log file is not getting created which is there in the ipl file meant for Deploy to Staging.When i simply run the ipl file ,it is executed & log file is created but by means of Workflow thats not the case.
Basically my WFT isn't able to call on the ipl script in an external task.
Is there a possibility of any config file being modified & TeamSite Server hasn't been restarted.This might lead to a WFT not being able to run an ipl script ?
An immediate help would be highly obliged.

Find more posts tagged with

Comments

Adam Stoller

I am working on TS 6.5.On Workflow instantiation there are no tasks in the completed tasks pane.My very first task is the 'Deploy to Staging' external task & it gets stuck up over there & comes out only on timeout.This is happening in all the Workflows on my development environment.But these workflows are working fine on production environment.
Basically task transitioning is not happening & even the log file is not getting created which is there in the ipl file meant for Deploy to Staging.When i simply run the ipl file ,it is executed & log file is created but by means of Workflow thats not the case.
Basically my WFT isn't able to call on the ipl script in an external task.
Is there a possibility of any config file being modified & TeamSite Server hasn't been restarted.This might lead to a WFT not being able to run an ipl script ?
An immediate help would be highly obliged.

Are you one Windows? If so, a number of folks have found a zero-length file called "iwperl" in IWHOME/iw-perl/bin/ and resolve the problem by either removing that file and/or changing all the references to iwperl to iwperl.exe

Beyond that - everything else is specific to your environment - which we can't see and thus it is difficult, if not impossible, to assist you further.

nikhil_palav

I am working on windows and the iwperl file at the said location isn't an empty file. I have checked the ipl as well and it runs absoloutely fine from the command line with the iwperl command from the said path.The problem might lie at the instance when we call on the ipl script in an external task from the wft.Are there some variables that needs to be checked which are being passed to the ipl script implicitly besides job id & task id.
Could there be some access issue or any log file that i need to check ?
Do let me know incase i am missing some crucial information.

Adam Stoller

I am working on windows and the iwperl file at the said location isn't an empty file. I have checked the ipl as well and it runs absoloutely fine from the command line with the iwperl command from the said path.The problem might lie at the instance when we call on the ipl script in an external task from the wft.Are there some variables that needs to be checked which are being passed to the ipl script implicitly besides job id & task id.
Could there be some access issue or any log file that i need to check ?
Do let me know incase i am missing some crucial information.

You said the scripts work on your production system but not in your development environment - right?
Here are some questions that might help: