Skip to main content

Notifications

Microsoft Dynamics AX (Archived)

Is there a way with Ax 4.0 to setup a configuration file that will directly connect to one AOS or the other without being intercepted by the AOS manager?

Posted on by 110

We have Ax 4.0 and we run the AOS manager over 2 AOS services.

Often times I need to login multiple times until I get on the correct AOS to see the SPIDs of users.

Is there a way with Ax 4.0 to setup a configuration file that will directly connect to one AOS or the other without being intercepted by the AOS manager?

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: Is there a way with Ax 4.0 to setup a configuration file that will directly connect to one AOS or the other without being intercepted by the AOS manager?

    Could it be that the configuration that you use has multiple servers set up to connect to? AX client uses the connections in order. So if the first connection fails, it tries the second, etc. If you have your loadbalancer as the first connection in your configuration, then it will produce the results you describe above.

  • Kevin Liebergen Profile Picture
    Kevin Liebergen 110 on at
    Re: Is there a way with Ax 4.0 to setup a configuration file that will directly connect to one AOS or the other without being intercepted by the AOS manager?

    That is how I currently have my configs setup. They work fine as long as the load balancer is not online. As soon as we turn the load balancer on it intercepts the connection and balanaces us.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: Is there a way with Ax 4.0 to setup a configuration file that will directly connect to one AOS or the other without being intercepted by the AOS manager?

    I take it your situation is as follows (read from bottom to top, forgive the poor graphing):

    AOS-1   AOS-2

    AOS-loadbalancer

    Client

    Normally you let a client connect to the loadbalancer, which then decides on what AOS to connect to. However if you create a client configuration file (use AX 4.0 Client configuration manager, its under administrative tools) with connection settings directly to AOS-1 or AOS-2, you will bypass the loadbalancer and always connect to the correct AOS.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,240 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,104 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans