[Poleax]

Цитата:

Сообщение от Poleax

Только вот ошибка возникает Основное\Настройка\Параметры документооборота\вкладка Администрирование\кнопка Проверка.

+ Error: The request failed with HTTP status 405: Method Not Allowed.

Варианты решения:

• Unable to validate workflow URL in AX 2009 - Get the following error: The request failed with HTTP status 405: Method Not Allowed
  
  Цитата:

  Steps we took to resolve:
  

  1. Created a new Application called MicrosoftDynamicsAXWorkflow50 and set the application pool to MicrosoftDynamicsAXWorkflow50 and physical path to C:\Program Files\Microsoft Dynamics AX\50\Workflow
     
  2. Ensured that the application pool settings was set as per http://blogs.msdn.com/b/emeadaxsuppo...08-r2-x64.aspx
     
  3. In the Authentication settings for MicrosoftDynamicsAXWorkflow50, ensure Anonymous is disabled and only ASP.NET Impersonation and WOndows Authentication are enabled
     
  4. In the Handler mappings for MicrosoftDynamicsAXWorkflow50, ensure there are 3 entries named WebServiceHandlerFactory-ISAPI-2.0_32bit... mapped to the *.asmx path.
• Request failed with HTTP status 405: Method Not Allowed
  
  Цитата:

  If you get a Http 405 error while trying to validate the workflow url in AX you are probably running into a static file handler issue. You can verify this by going into IIS to the workflow web site, find the axworkitems.asmx within that website, right-click on it and choose Browse. If you get this error: "HTTP Error 404.17 - Not Found. The requested content appears to be script and will not be served by the static file handler" you definitely have a static file handler issue.
  
  This usually occurs when you have the 4.0 .NET framework installed on the machine. The workflow web services are built with version 2.0 of .NET. IIS has associated the workflow web service files with the 4.0 file handler and the services are not functional with that handler.
  
  To correct the issue, create a new application in IIS under the your Workflow site. Point the new application to the Program Files\Dynamics AX\50\Workflow folder. Set its application pool to the MicrosoftDynamicsWorkflow50 application pool. After doing this the issue should be resolved. The newly created application will have WebServiceHandlerfactory-ISAPI-2.0 Handler Mappings whereas the previous one had only one mapped to Asp.NET 4.0.