Friday, June 03, 2011

How to resolve SysWorkflowMessageQueueManager-run error in Microsoft Dynamics Ax 2009 Workflow




This article explains how to resolve SysWorkflowMessageQueueManager-run error in Microsoft Dynamics Ax 2009 Workflow.

Error:
ClrObject static method invocation error.
Exception has been thrown by the target of an invocation.
Applied on:
Ax 2009 SP1
The workaround- the above mentioned error there are few things to be checked.
1) Make sure the .NET Business Connector is connected to the correct AOS server or not.
To check this:
  • a) Start --> Administration tool --> Microsoft Dynamics AX 2009 Configuration.
  • b) On the tob change Configuration Traget to: Business Connector (non-interactive use only) on Connection tab check that it is connecting to correct AOS or not. It should be connected.
2) If you shutdown the AOS then you may need to restart the IIS to refresh the connection.
To restart it:
  • i) Start --> Run
  • ii) Type "IISRESET" without quote
  • iii) Click on OK buttonORa) Open command promptb) Type in "IISRESET" without the quote.
3) If you have more than one Workflow website setup for several environment on the same system then except one you are testing stop other websites.
4) Compare the Identity of the Application Pool used by Ax Workflow website with the Business Connector proxy setup in the system. If business connector proxy user id is not configured properly with Applicatoin pool the .NET Business Connector will fail to connect to the AOS.

1 comment:

  1. hi Pankaj Chaturvedi ,

    we are also facing the above issue , but how to sloving i am not getting this thing

    ReplyDelete

Enable UAT database over OneBox DevTest environment using JIT

 Dear Friends, In this Article I will show you how to enable UAT database access for Development machine using just-in-time (JIT). Many time...