Developer forum

Hi Justin,
the AX2012 is not supported in the direct access from the EndpointManagement. Finance and Operation is supported but it has different service url ending part.
Can you rename your AX2012 service url to ends with "/services/dwservice" string? If not then you can install the Dynamicweb service which can connect to AX2012 and then connect your DW10 with Dynamicweb Service instead and choose the settgins like that:

BR, Dmitrij

Hey Dmitrij,

Thanks, I installed the service, but then I get:

Is NTLM supported through the service, I don't know if I need to set an extra key for that in the config of the service? I can connect to the service via a webbrowers, and the succesful connection on my previous screenshot was also made setting the endpoint authentication to NTLM.

My config is:

Hi Justin,

the NTLM is not supported, however it passes the userName, pwd and domain to the request, so it sets the:
HttpClientCredentialType.Windows for the binding.
Can you switch the authentication type to Windows in the AX server setttings?
Also you can try to remove the "BindingType" option from the service config then it will use the WSHttpBinding instead of BasicHttpBinding but I am not sure it is related to this?
Also maybe it is needed to fill the relevant CompanyName in the settings.
Once the settings config file is changed then the service needs to be restarted.

BR, Dmitrij

The documentation about AX2012 configuration is here:
https://doc.dynamicweb.com/documentation-9/integration/integration-framework-old-structure/remote-system-setup/ax2012-r3

Hi Dmitriy,

Thanks for the weekend support ;-)

We set the Authenticattion in AX to Basic for now, and that seems to resolve the login error.

We do get a new error now, I've asked the AX parntner to inspect the server log, probably not something obvious from this message:

System.ServiceModel.ServiceActivationException: The requested service, 'http://......actualurlhere..../MicrosoftDynamicsAXAif60/DWServicePort/xppservice.svc' could not be activated. See the server's diagnostic trace logs for more information.

Server stack trace:

   at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)

   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)

   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Hey Dmitriy,

For future reference, and maybe when other people run into this.

The error was caused by the IIS AppPool running under the wrong credentials. This will result in the authentication on the service level succeeding, but then within AX it will trigger the "Failed to logon to Microsoft Dynamics AX" message.

Thanks for your help!

Justin

Hi Justin,
thx for the feedback, can you share what were the settings for that in the IIS?
Then we can update our documentation about this
BR, Dmitrij

Hey Dmitiry,

I don't have a lot of additional information. The customer runs a test and production environment, somehow the application pool on the test server ran on the production user. After setting the application pool identity to the correct user (test) it worked:

So it might just warrant a line in the troubleshooting section, making sure to check the AppPool wih that specific "Failed to logon to Microsoft Dynamics AX"   message