Share
Report
190Hi Everyone!
I was trying to prepare for some NLB implementation and created a DNS record with the desired name. While I was waiting for the NLB to being built I thought I could just point the new DNS record to the IP address of the first server hosting the AOS Service instance. Then I would change the configurations on all my AX components and would be ready for the NLB, without the need to change anything afterwards.
Boy was I wrong!
I created a new AX Client configuration file (AXC) using 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 name of the new DNS record that point to my server hosting the AOS Service, 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 was doing this locally on the server hosting the AOS Service, just to test everything, before going through all my components.
I double clicked the new configuration file and expects the AX 2012 client to start, but instead I got an error: "The Application Object Server is unavailable. Check your configuration and network connection and try again".
Then I thought to my self that I could just use the IP address for the server in my configuration file, to make sure that everything works as expected. Look at my post regarding that: https://community.dynamics.com/ax/f/33/t/159074
So I was beaten by the new security implementation from AX 2012 R3 when using the IP address as stated in the above post.
I then went on to try creating a AX Client configuration file (AXC) on a remote server with an AX Client installed. I followed the above steps and double clicked the new configuration file on the remote server.
The AX Client started and everything works like a charm!
Now I am really confused...
Going back to my good "old" AX 2012 R2 CU7 installation and tried the same thing. Create a new DNS record that points to the IP address of the server hosting the AOS Service instance. Create a new AX Client configuration file (AXC) locally on the server using the above steps, using the new DNS record.
I double clicked the new configuration file locally on the server hosting the AX 2012 R2 CU7 AOS Service instance.
The AX Client started and everything works like a charm!
Great, so I know it did work back in the "old" days.
Q: Can some one explain to me what I need to do to make the new DNS record work locally on the server hosting the AOS Service instance when it seems to work perfectly from the remote server?
Q: Anyone got a working NLB solution for RPC calls and WCF service calls, using either Windows NLB or a third party solution (software / hardware) running AX 2012 R3 or higher?
Should I just "ignore" the locally behavior on the servers running the AOS Service instances and make everything else use the new DNS record while waiting for the NLB to being built?
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
