20

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.

Share this article:

20 Comments to “Workflow validation error: The request failed with HTTP stauts 405: Method Not Allowed.”

• royk
  August 18, 2010 at 11:53 am

  thanks for the post, same issue server 2008 R2.
  tried to follow your fix but stuck once i got to “I went to permissions of that application, by right clicking the “Applicaiton” and selecting “Edit Permission” and I insued that “ASP.NET Imporsenation” ”

  when i click on edit permissions i get the properties of the folder c:…workflow – which is no help. maybe i am clicking the wrong thing ?
  any pointer would be highly appreciated.

  Reply
• royk
  August 18, 2010 at 1:04 pm

  ok should be double click authentication, then the rest flows fine.
  but, now i get a different error :

  Client found response content type of ‘text/html; charset=utf-8′, but expected ‘text/xml’.

  The request failed with the error message:

  –

  IIS 7.5 Detailed Error – 500.19 – Internal Server Error

  Server Error
  Internet Information Services 7.5

  Error Summary
  HTTP Error 500.19 – Internal Server Error
  The requested page cannot be accessed because the related configuration data for the page is invalid.

  Detailed Error Information

  ModuleIIS Web Core
  NotificationBeginRequest
  HandlerNot yet determined
  Error Code0x80070005
  Config ErrorCannot read configuration file due to insufficient permissions

  Config File\?C:Program FilesMicrosoft Dynamics AX50Workflowweb.config

  Requested URLhttp://ax12:82/MicrosoftDynamicsAXWorkflow50/AxWorkflowInstance.asmx
  Physical PathC:Program FilesMicrosoft Dynamics AX50WorkflowAxWorkflowInstance.asmx
  Logon MethodNot yet determined
  Logon UserNot yet determined

  Config Source

     -1: 
  
      0: 
  
  

  Links and More Information
  This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
  View more information »

  –.

  Reply
• Amer
  August 18, 2010 at 4:53 pm

  Hi Royk,

  Ok then. Great that you reached this point. But I did not understand where exactly you get that error. Please give me more details.

  Amer

  Reply
• royk
  August 19, 2010 at 10:05 am

  thank you again for your post and reply,

  i got over the above authentication error by granting proper permissions to the local iis_iuser group to c:..workflow

  but now i get the following, once i press the validate workflow runtime url (after applying your fix)so before your fix it was 405 (method not allowed) now it is 500.19 (Cannot add duplicate collection entry of type ‘add’ with unique key attribute ‘name’ set to ‘WindowsAuthentication’):

  Client found response content type of ‘text/html; charset=utf-8′, but expected ‘text/xml’.
  The request failed with the error message:
  –

  IIS 7.5 Detailed Error – 500.19 – Internal Server Error

  Server Error in Application “AXWF/MICROSOFTDYNAMICSAXWORKFLOW50″
  Internet Information Services 7.5

  Error Summary
  HTTP Error 500.19 – Internal Server Error
  The requested page cannot be accessed because the related configuration data for the page is invalid.

  Detailed Error Information

  ModuleConfigurationValidationModule
  NotificationBeginRequest
  HandlerWebServiceHandlerFactory-Integrated
  Error Code0x800700b7
  Config ErrorCannot add duplicate collection entry of type ‘add’ with unique key attribute ‘name’ set to ‘WindowsAuthentication’

  Config File\?C:Program FilesMicrosoft Dynamics AX50Workflowweb.config

  Requested URLhttp://ax12:82/MicrosoftDynamicsAXWorkflow50/AxWorkflowInstance.asmx
  Physical PathC:Program FilesMicrosoft Dynamics AX50WorkflowAxWorkflowInstance.asmx
  Logon MethodNot yet determined
  Logon UserNot yet determined

  Config Source

     68:

  Reply
• royk
  August 19, 2010 at 1:10 pm

  ok fixed,it was my failure to set the application pool identity to MicrosoftDynamicsAXWorkflow50 (default was AXWF – sitename)thanks again

  Reply
• Amer
  August 19, 2010 at 3:09 pm

  Great!!

  I’m so happy for you.

  Reply
• gh
  August 30, 2010 at 12:36 pm

  royk,

  What exactly do you mean with “it was my failure to set the application pool identity to MicrosoftDynamicsAXWorkflow50 (default was AXWF – sitename)”

  I have the same problem

  Regards
  gh

  Reply
• Amer
  August 31, 2010 at 3:55 pm

  gh,

  What Royk meant to say that he has changed the “Application Pool” of the Workflow site into “MicrosoftDynamicsAXWorkflow50″. You could do that by setting it up in the “Basic Settings” of the Workflow Site in the IIS.

  Reply
• Gonzalo García
  November 11, 2010 at 5:37 pm

  Hi Amer, I followed all the instructions in this post and I also got stuck where royk got stuck, I made the changes on the application pool and now I get this error when I try to validate the URL in DAX:

  System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.ComponentModel.Win32Exception: Access is denied
  at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)
  at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
  at System.Diagnostics.NtProcessManager.GetFirstModuleInfo(Int32 processId)
  at System.Diagnostics.Process.get_MainModule()
  at System.Workflow.Runtime.PerformanceCounterManager.SetInstanceName(String instanceName)
  at System.Workflow.Runtime.WorkflowRuntime.StartRuntime()
  at Microsoft.Dynamics.Framework.Workflow.AxWorkflowRuntime.get_WindowsWorkflowRuntime()
  at Microsoft.Dynamics.Framework.Workflow.WorkflowInstanceManager.Ping()
  at Microsoft.Dynamics.Framework.Workflow.WebServices.AxaptaWorkflowInstance.Ping()
  — End of inner exception stack trace —

  Now I am doing all this in Windows 7, I don’t know if I need to do something else or it is simply impossible to make workflows work on a non server operating system.

  Reply
  • Jailyn
    July 24, 2011 at 2:26 am

    Gee wliilekrs, that’s such a great post!

    Reply
• Amer
  November 24, 2010 at 10:07 am

  Ok, now I have modified the post to reflect what you guys have found unclear.

  Gonzalo, after you insured that all the steps are made above.. have you tried to browse any of the workflow asmx services? if yes, what do you get?

  Reply
• Deep
  December 4, 2010 at 10:48 am

  Hi,

  I am facing the same issue as Gonzalo

  System.Web.Services.Protocols.SoapException: Server was unable to process request from IIS am able to browse .asmx files without any error can you please tell me how this can be resolved.

  TIA…

  Reply
• Awni Al-Sadeq
  February 21, 2011 at 6:20 pm

  Hi,

  I had the same issue. Finally I’m able to fix it.
  You don’t need to remove the application and recreate it. You just need to make sure that there is a mapping for the *.asmx handler.
  This can be done by double clicking on “Handler mappings” of the MicrosoftDynamicsAXWorkflow50 application.
  Click on Add script map link. type: *.asmx in the requested path. type: WebServiceHandlerFactory-ISAPI-2.0 in the name and type: %windir%Microsoft.NETFrameworkv2.0.50727aspnet_isapi.dll in the executable.

  This should work it out!!

  Reply
• Amer
  February 21, 2011 at 6:36 pm

  Hi Awni,

  I’m glad it worked by that!

  I would go to this scenario in the beginning, however if it didn’t work I would go back again and start with the procedure I described in the post. This change only will not do the job in some cases, so you have to insure that all of your configuration is correctly set up and then do that change.

  Many thanks Awni!

  Reply
• Roger
  March 16, 2011 at 8:37 am

  Hi Amer,

  I was also getting the “System.Web.Services.Protocols.SoapException: Server was unable to process request” error when trying to validate the workflow url. I managed to fix it by adding new rules in Windows Firewall to allow the port I was using.

  Hope this helps.

  Reply
• samurai_developer
  May 16, 2011 at 6:10 am

  Did not work for me “The request failed with HTTP status 404: Not Found.”

  is the error on validate inspite of doing the changes in your post.

  Kindly help.

  Reply
  • Amer
    May 18, 2011 at 8:32 pm

    Hi Samurai, will I’m afraid that this is a totally different error my friend . Have you checked if you created a usual HTML page and put it in the virtual directory of the Workflow.. what would happen?

    Reply
• Indira
  June 9, 2011 at 9:55 am

  Awni, the resolution you had given is simple and worked like a champ. Thanks.

  Reply
  • Amer
    June 10, 2011 at 11:38 pm

    Great

    I had that issue two weeks back.. I did try what you and Awni mentioned but infortunatley it did not work. So I went through the steps I listed in the post and finally i got it worked.

    Congratulations anway.

    Reply
• Ahmad Shafout
  March 31, 2012 at 10:57 am

  Dear Amer,
  Thank u very much.I follow ur steps and it’s work fine … thanks

  Reply

Dynamics AX 2012 Event

Recent Posts

Tags

Archives

Random Testimonial

What's the little bird saying?