Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
This page is intended to provide a consolidated list of published documentation, sources of information, known issues, solutions as well as tips and tricks for troubleshooting Workflow for Microsoft Dynamics AX 2009.
Most of the Critical Workflow hotfixes are included in Rollup 4 (RU4) or higher; To find the latest Rollup see Hot Fixes Released for Microsoft Dynamics AX 2009
The following KB articles can be applied separately, but it is recommended to move to the latest Rollup Hotfixes.
This section lists the most common issues encountered in Workflow for Microsoft Dynamics® AX and the solution recommended by the Microsoft Dynamics® AX Support team. Please note that there may be some different setting required for installing workflow with IIS 6.0, IIS 7.0, or IIS 7.5. You may need to work with IIS resources for IIS related errors or problems.
Workflow documents are not processing in a development/ test environment after restoring the database or in a production environment after changing batch or AOS server configuration.
The server setup, batch groups, and Workflow URL may be incorrect and would need to be changed for the new Environment.
See Checking Database entries after restoring a Microsoft Dynamics 2009 SQL Database to another Domain or Environment
See Unable to validate the AX 2009 Workflow Webservice URL
Use this information along with any Event Id’s of 1001 to confirm the times when the AOS crashes.
When I manually browse any aspx pages in the Workflow virtual directory I get a HTTP Error: 404.17
See Troubleshoot Error 404.17 - Not Found
If you are testing workflow and do not wish to wait for the batch job to process, you may run the workflow tutorial instead. To do this in Microsoft Dynamics AX go to AOT | Forms | Tutorial_WorkflowProcessor. DO NOT use the Tutorial_WorkflowProcessor in production as you can inadvertently remove records from queue if you click the Clear button. Settings to change after restoring the database. Deployment Recommendations:
Long processing times for workflow batch jobs
There may be times when the workflow batch jobs are taking longer than normal to process workflow documents where user assignments are made. This can happen when old workflows are left in the system and not completed or are canceled. The following SQL statements can be used to help identify this issue and aid you in locating the documents that may need to be cancelled.
If you are experiencing issues downloading the install file or documentation on CustomerSource/PartnerSource, please contact ITMBSSUP@microsoft.com