Workflow Does not proceed further after activation in AX2009

(0) Share

Report

Posted on by Community Member

Hi All,

I have developed a workflow for sales free text invoices in AX2009 and I Think i have done all the required setups for the workflow to work such as , setup with batch group, setup with batch group server, workflow configuration, calendar setup etc. After doing all this after submission of my invoice, the workflow gets activated in the workflow history but does not move further with approval process.

Please can anyone puts some light on what might be wrong with the workflow.

Thanks in advance.

Regards,

Tarren Gomes.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Community Member on at

Like (0)

Report

Does anyone have any idea on this...

Was this reply helpful? Yes No
Darsh 615 on at

Like (0)

Report

Pl. look into the action > View histroy on the submitted item. and see that is that any error. is it showing stopped/pending.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Its not in any error state. its says pending.. and never proceeds further.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Also when I make use of tutorial_workflowProcessor the workflow does not gets processed. Can you tell me where i might be wrong.

Was this reply helpful? Yes No
Darsh 615 on at

Like (0)

Report

check for below things:

1) calendar -> Working time. is this setup?

2) User relations to employee

3) does your other batch jobs are running ?

if possible pl. share screen of workflow history form with tracking details tab.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes I have done the above setups, please look at the screenshot of the workflow history.

Also I when i checked the event log i got below error

Workflow instance: XXX was terminated for the following reason: The type initializer for '<Module>' threw an exception..

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Finally found the problem. This issue was because AX could not connect to IIS since it was 32 bit and the system was of 64 bit. I changed the IIS pool property Enable 32-bit application as true and the workflow worked fine.

Was this reply helpful? Yes No