July 24, 2010 in Blog, Dynamics AX by Amer

Workflow validation error: The request failed with HTTP stauts 405: Method Not Allowed.

I have faced this error twice, I sloved it the first time by “Enabling the 32-bit Applications” on the application pool level of the workflow.

But in another time the installation was on Windows 2008 R2, and this made things harder. Enabling the 32-bit Application did not solve the issue. This actually happened because of the conflict in this Windows between the .NET framework 2.0 and .NET framework 4.0. It also might be caused of an authentication issue, so you better check that all one by one to get this validation problem resolved.

To solve the issue, I basically have gone through these steps: (of course I followed those steps after installing the workflow and I did not uninstall it)

• Deleted the application from the IIS (the selected node in the picture below).

• Added a “Virtual Directory” to the same site and named the new virtual directory with the same name of the deleted application.
• In the physical path of the virtual directory, I pointed to the installed worklfow folder (most probably will be in “C:Program FilesMicrosoft Dynamics AX50Workflow“). This folder contains the web services of AX workflow.

•  Then, I converted the new “Virtual Directory” to “Application” by right-clicking that directory and clicking “Convert to Application”.
• I went to permissions of that application, by clicking (selecting) the “Applicaiton” you have just converted and double clicking ”Authentication” and I insured that “ASP.NET Imporsenation” and “Windows Authentication” are enabled and any other things are disabled.
• (Optional) You might disable the Kernel-mode authentication for the Windows Authentication by clicking the “Advanced settings” for the Windows Authenticaion. You cannot do that if if you have a kerberos authentication configured in your environment, if not.. then you better disable it to improve your environment performance.
• I then went to the “Handler Mapping” of the Workflow Application. I selected “WebServiceHandlerFactory-ISAPI-2.0″ and then clicked “Edit”. I insured that the “Executable” path is pointing to the .NET framework version 2.0 32-bit. (Note that this Windows contains on two versions of framework handlers and in two different folders inside the “C:WindowsMicrosoft.NET” folder.) In our case, you always have to point to the “aspnet_isapi.dll” file in the “Framework” folder not “Framework64″.

By this, you will be able to browse anyone of the *.asmx files in the Workflow Application. Also you might validate your workflow configuration.

Hopefully it has been resolved to you as well.

July 20, 2010 in Blog, Dynamics AX by Amer

Enterprise Portal “Generate Proxies” Form: ClrObject static method invocation error.

I have examined an error while trying to re-generate the proxies classes that are used in the Enterprise Portal.

When I traced the code, I discovered that this tool is actually updating .NET proxies classes based on the EP installation physical path. For some reason, this tool was not able to get that path.. the generated path was: “” (empty string).

What I did is that I got the physical path of the proxy classes, and changed the code where it tries to get that path and fixed it. This is done in ClassesSysEPDeploymentcreateDevWebsiteProxyDir.

This code shows what I did:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

public static client str createDevWebsiteProxyDir()
{
    #AOT
 
    Microsoft.Dynamics.Framework.Deployment.Portal.EPSharepointAdmin epSharepointAdmin;
    EPGlobalParameters epGlobalParam;
    str dir;
 
    select firstonly epGlobalParam;
 
    if(!epGlobalParam.DevelopmentSiteId)
        // UA!No development web site.
        throw error('@SYS108771');
 
    epSharepointAdmin = new Microsoft.Dynamics.Framework.Deployment.Portal.EPSharepointAdmin();
 
    /*comment from here
    dir = epSharepointAdmin.GetAppCodeDirectoryFromSiteId(guid2str(epGlobalParam.DevelopmentSiteId));
    comment to here*/
 
    //add this line of code (My installation was on this path)
    dir = "C:\inetpub\wwwroot\app_code";
    //In Dynamics AX VPC1, the installation is on this path <>
    dir = "C:\Inetpub\wwwroot\wss\VirtualDirectories\sharepoint80\App_Code";

Here is where the EP proxies classes to be generated and hence used by the Dynamics AX EP.

By this, the tool just worked fine .

July 8, 2010 in Blog, Dynamics AX by Amer

Create Dynamics AX Workflows in Three Easy Steps by Workflow for Dummies Wizard

As I have mentioned in an earlier post, to get my life easier with developing new Dynamics AX Workflows I have created an easy to use wizard that generates AOT objects for one Approval workflow in Dynamics AX 2009, without writing a single line of code. I have used this wizard since more than a year to develop all the workflows that I had to develop.

I have been asked many times by Dynamics AX technical and functional consultants to share that with them. And here I am sharing it with the Dynamics AX community.

By following three steps, Dynamics AX Workflow for Dummies simply:

1. Adds a Workflow Template
2. Adds a Workflow Category
3. Adds a Workflow Approval
4. Adds a workflow state field to the selected table
5. Enables the workflow for the selected form
6. Creates needed classes like the document class for the workflow document
7. Creates a query (Workflow Document)

Here are the steps that you have to follow: (pictures speak quietly)

Generated AOT Objects Parameters

After clicking Finish, you would get a Dynamics AX Project:

In order to configure the generated Workflow template, go to the module that you have selected in the wizard, and open the Workflow Configuration under the Setup menu of that module. This is what you will have:

If you are interested to have it, just comment on this post and write me your email or send me an email to amer@amer-ax.com and I will be more than happy to send the project to you.

I also would welcome any feedbacks on this.