This is the error you receive while trying to access ASMX web service from Windows 7 64-Bit / Windows 2008 Server 64-Bit and IIS 7.
The request failed with HTTP status 405: Method Not Allowed.
When you validate workflow from Dynamics Ax, it actually tries to invoke ping method on AxWorkflowInstance.asmx web service. If successful, returns true else false.
And if you try to browse this ASMX web service directly, most probably you will hit the error mentioned below…
HTTP Error 404.17 – Not Found
The requested content appears to be script and will not be served by the static file handler.
To resolve this do following two things:
Step 1: Set application pool correctly.
Set “Enable 32-Bit Application” property to true in the advance settings of your application/virtual directory’s application pool.
Also make sure that application pool is running in Classic mode and on 2.0 version of the .NET Framework.
Step 2: Check if you have 32 bit mapping for ASMX files.
- Open Handler Mappings of your site, application or virtual directory. This is the place where you setup all ISAPI extensions and native modules.
- Check for 32 bit WebServiceHandlerFactory-ISAPI-2.0 ISAP mapping for all ASMX files. Create one if does not exist by clicking on Add Module Mapping…
Click yes on the dialog box.
You can also add it manually to the web.config of your web application. In this case Ax workflow application (C:Program FilesMicrosoft Dynamics AX50Workflow). Setting is…
Please join this blog if you liked this post.
Also feel free to post your comment / feedback / queries.