How to resolve Stopped (error): Target date not found in work calendar error in Microsoft Dynamics Ax 2009 Workflow

This article explains how to resolve Stopped (error): Target date not found in work calendar error in Microsoft Dynamics Ax 2009 Workflow.

Symptom:
If you see the Tracking details of your workflow process it shows "Workflow stopped (error)" and : Stopped (error): Target date not found in work calendar.

Reason:
A work calendar is missing in workflow setup.

Resolution:
The workaround on this, create a work calendar in Ax.
To do this:
Go to Basic-->Calender and create a calender. If you have already created a calender you can use that one.

Once the Calender is created, assign the calendar to the workflow setup. Lets say you are running workflow for Purchase Requisition then Go to the Accounts Payble-->Setup-->Workflow Configuration. On this form go to Details tab, select a Workflow element, in the buttom part (Approval Details) select Overview tab, check the check box "Set a time limit for the approval process". Here you will get the calender lookup to select a work calender. Assign a calender and do any other setup if you require. Save your work and make transaction for workflow to check.

I hope this will remove your Stopped (error): Target date not found in work calendar error.

Other related articles:
How to install and configure Microsoft Dynamics Ax 2009 workflow step by step
How to resolve SysWorkflowMessageQueueManager-run error in Microsoft Dynamics Ax 2009 Workflow

Warning:
There is no warranty on this article. Use at your own risk.

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.

Warning:
There is no warranty on this article. Use at your own risk.

Other related article:

How to install, configure and setup Microsoft dynamics Ax 2009 workflow step by step.

Resolution for Microsoft Dynamics Ax 2009 Role Center & Enterprise Portal (EP) Access Denied error

This article explains:
How to resolve Microsoft Dynamics Ax 2009 Role Center & Enterprise Portal (EP) Access Denied error.
How to assign permission to Microsoft Dynamics Ax 2009 Role Center & Enterprise Portal (EP) users.
How to give permission for Microsoft Dynamics Ax 2009 Role Center & Enterprise Portal (EP) users from Microsoft Windows Sharepoint Services or Server.


Problem:
When you open Microsoft Dynamics Ax 2009, the role center shows an error “Error: Access Denied” + “Current User” + “You are currently signed in as: domain name\user id” + “Sign in as a different user”.

Reason:
You don’t have the permission to access AX enterprise portal (website) which is made within windows sharepoint services or server.

Resolution:
The permission to be given to all the users who wants to access Role Center or Enterprise portal.

1)
To give the permission you have to login to the Ax enterprise portal (website) using administrator permission.On the Ax enterprise portal site there would be a button called “Site Actions” on upper right hand side. Click on Site Actions then Site Settings as shown below.


2)
Click on People and groups under Users and Permissions


3)
Click on New then Add Users.


4)
Add user(s) from domain you are using for AX and WSS. Once the user(s) is added, give permission accordingly as shown below.


5)
From below screen you can search user(s) and add them.

6)

Once the user(s) added and permission assigned, click on OK button.

Now you have given the permission to the user(s). It should not give you any error like Access Denied.

NOTE: There is No warranty on this article, use at your own risk.

How to install and configure Microsoft Dynamics Ax 2009 workflow step by step

NOTE: There is NO warranty on this article, use at your own risk.

This article explains:

How to install Microsoft Dynamics AX 2009 Workflow step by step

How to configure Microsoft Dynamics AX 2009 Workflow step by step

How to setup Microsoft Dynamics AX 2009 Workflow step by step

About Workflow:

The Microsoft Dynamics AX workflow infrastructure enables user configurable workflows in Microsoft Dynamics AX application modules with specific focus on task and approval workflows. The workflow runtime manages configuration and executation of workflows while the application modules will manage activation and business logic associated with workflows.Microsoft Dynamics AX 2009 workflow uses Windows Workflow Foundation (.Net framework), AX batch framework, Internet Information Services (IIS), Active Directory (AD) users, .Net Business Connector for AX and web services.

Prerequisite:

You should have basic knowledge of AX.Basic AX should be installed on your system.Create two users in AD. One is for workflow another is for business connector proxy. The password should not be expired or changed for these users.If you have already created, no need to create now.Add these users to AX.

Steps to follow:

1) Open AX client then open the System service accounts form and add users for workflow.Go to Administrator > Setup > Security > System service accounts.

2) If you want to use a separate website for workflow then create a website in IIS or you can use the default website. If you use default website the setup process will create a sub site under default website.

I have created a new website called AxWfl as shown above. It’s not mandatory to create a separate website for this but recommended.

3) Run AX setup file and install workflow. If .Net Business Connector is not installed AX setup will install it itself.

4) Once the setup process is done successfully open AX client.

5) From Basic main menu create a Calendar. Here I have created the calendar called 24Hours.

6) Create a batch job for workflow. Go to the Basic > Batch job list – user form and create a batch job. Here I have created a job called Wfl.

7) Go the Administration > Setup > Workflow infrastructure configuration wizard form.Run the wizard and follow the instructions and finish it.

8) Now make a setup for Purchase Requisition. Go to Accounts Payable > Setup > Workflow configurations form. Here configure the workflow with required conditions. A Workflow Configuration is bound to a single Workflow Template. In this process you need to select the calendar you created in step 5.

Once the purchase requisition workflow setup is over go to AOT > Forms > PurchReqTable > Designs > Design. Right click on Design then properties and check whether is Workflow Enabled or not.

9) Once you have done all these then create purchase requisition using respective user, perform all the tasks you instructed during workflow configuration/setup and submit it. After submission you can see the history of workflow.

10) Now open AX client using approver user id and see the task assigned and complete it.

Using approver user id approve it and check that the purchase order has been created or not. I hope it will create a purchase order.