Hi everyone!
I was struggling with some DNS issues earlier today and while troubleshooting the issue I tried to create a new client configuration and save it as a AXC file, using the IP address for the AOS server.
I used the "AX 2012 Configuration" program to create a new configuration, and selected "Original configuration" under the "Copy configuration from" section.
I deleted all entries on the Connection tab and added a new entry, with the IP address of my AOS server (not using the server name), with the ports for both "TCP/IP" and "WSDL": 2712 and 8101.
I clicked the "Refresh Configuration" button that contacts the AOS server and retrieves the complete WCF configuration and stores it with the configuration.
I clicked the "Apply" button and now exported the configuration to a file.
I double clicked the new configuration file and expects the AX 2012 client to start, but instead I got an error within a split second: "The Application Object Server name or port number is incorrect. Check the values in the Microsoft Dynamics AX Server Configuration Utility, and try again".
I started Wireshark to see what network calls that were being generated while the AX client was starting and to my surprise no network calls related the AX 2012 was generated.
I double checked with another installation that was running perfectly and worked fine, here I would see a DNS request for the name and shortly after a call for the AOS' IP address on port 2712. In this installation I was using a configuration with a server name in the configuration.
From my point of view it seems that the AX Client is validating the values inside the AXC file before performing the initial network call for the AX AOS instance.
Q: What do you guys think about this?
Note 1: I tripled checked everything with a AX 2009 installation and here the IP address entry works just fine.
Note 2: I did open the AXC file to see what was saved regarding the WCF configuration. I could see that there was serveral entries with "net.tcp://" but I could not connect to these with a standard browser. By changing the value from "net.tcp://" to "http://" and changing the port from "8201" to "8101" I was able to get a WSDL file in my browser. E.g. http://10.10.10.10:8101/DynamicsAx/Services/SysWindowsAppApprovalsServices
Note 3: I did try both from the server hosting the AOS Service instance (we got a local AX Client installed) and from a remote PC/Server with a AX Client installed. No luck.
Note 4: While write this post I actually performed the same on AX 2012 R2 CU7, but only from the server hosting the AOS Service instace (I didn't have a remote PC/Server with the correct AX Client build). Here the IP trick works like in the good old days.
Q: Have any of you guys ever gotten a AX client (AX 2012 R3 or higher) working with a configuration file that only contained the IP address for the server hosting the AX AOS instance?