AXForum  
Вернуться   AXForum > Microsoft Dynamics AX > DAX Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 07.07.2010, 23:05   #1  
Blog bot is offline
Blog bot
Участник
 
25,626 / 848 (80) +++++++
Регистрация: 28.10.2006
emeadaxsupport: Unable to validate workflow URL in AX 2009 - Get the following error: The request failed with HTTP status 405: Method Not Allowed
Источник: http://blogs.msdn.com/b/emeadaxsuppo...t-allowed.aspx
==============

We came across a recent issue where we have a new Windows Server 2008 R2 with nothing else installed other then the AX 2009 Workflow extensions and the server has been patched with the latest windows update patches that includes asp.net 4.0. The application pool of the workflow web service was already modified as per http://blogs.msdn.com/b/emeadaxsuppo...08-r2-x64.aspx, however when you tried to validate the workflow infrastructure configuration wizard, you get the same error:

The request failed with HTTP status 405: Method Not Allowed


To troubleshoot this, we verified that the workflow folder had the appropriate NTFS permissions, and that the application pool runs as .net framework 2.0 classic and not 4.0. However when we browse one of the web service pages, AxWorkItem.asmx, we get the following error:

HTTP Error 404.17 - Not Found
The requested content appears to be script and will not be served by the static file handler.


This indicates we have an asp.net handler issue and it cannot find the correct handler to process the .asmx file. So looking at the handler mappings for the MicrosoftDynamicsAXWorkflow50 application, identified that there was only one *.asmx handler and this was mapped to ASP.NET 4.0 (C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll)

We tried re-registering asp.net 2.0 using aspnet_regiis.exe but this did not help. However just deleting the virtual application and recreating it again manually using IIS Manager, recreated it with all the default required asp.net 2.0 handlers and this resolved the issue.

Steps we took to resolve:

(1) Deleted MicrosoftDynamicsAXWorkflow50 virtual directory in IIS, under the default web site

(2) 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

(3) Ensured that the application pool settings was set as per http://blogs.msdn.com/b/emeadaxsuppo...08-r2-x64.aspx

(4) In the Authentication settings for MicrosoftDynamicsAXWorkflow50, ensure Anonymous is disabled and only ASP.NET Impersonation and WOndows Authentication are enabled

(5) In the Handler mappings for MicrosoftDynamicsAXWorkflow50, ensure there are 3 entries named WebServiceHandlerFactory-ISAPI-2.0_32bit... mapped to the *.asmx path.

--author:Anup Shah--editor:Anup Shah--date:07/July/2010


Источник: http://blogs.msdn.com/b/emeadaxsuppo...t-allowed.aspx
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
Ошибка бизнес-процесса Tarasov E Dynamics CRM: Разработка 9 18.02.2010 14:02
emeadaxsupport: Unable to validate the AX 2009 Workflow Webservice URL on a Windows Server 2008 R2 x64 Blog bot DAX Blogs 0 05.01.2010 19:16
emeadaxsupport: List of fixes that improve performance of certain features in Dynamics AX 2009 Blog bot DAX Blogs 0 13.10.2009 19:06
axStart: Microsoft Dynamics AX 2009 Hot Topics Web Seminar Series Blog bot DAX Blogs 0 06.08.2008 12:05
Говорят вышел SP2 для Axapta 3. Кто нибуть что знает на эту тему? soin DAX: Прочие вопросы 10 13.10.2003 10:43

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 09:01.