Multiple AOS servers using single SSRS instance

(0) Share

Report

Posted on by austin91

135

In our production AX environment (AX 2012 R2), we have two AOS servers in use. For the sake of example, I will call our two AOS servers AOS1 and AOS2.

We have found that when AOS1 is down, SSRS reports in AX do not work for users connected to AOS2. The users receive an error: "No connection could be made because the target machine actively refused it". However, if AOS2 is down, users that are connected to AOS1 are able to generate reports in AX as expected. So it would seem that some configuration for our report server is pointing explicitly to AOS1.

In Dynamics, in System administration > Business intelligence > Reporting Services > Report servers, we have two configurations setup, one for each AOS. They both specify the same report server, and are both checked as the "Default configuration".

Our goal is that if one of our two AOS servers is down (it should not matter which one), SSRS reports in Dynamics should still work for users connected to the other AOS. Can anyone offer any guidance on this? I am assume that it is possible to have multiple AOS servers supporting the same AX environment, that both use the same SSRS server and instance. Can someone confirm?

Thanks,

Austin

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Verified answer

André Arnaud de Cal... 301,020 Super User 2025 Season 2 on at

Like (0)

Report

Hi Austin,

The SSRS server has an AX client configuration setting. In this configuration you have to change the AOS settings. Probably it now points to AOS1 only. Also add AOS2 as listed server.

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (1)

Report

André's solution to include the AOS configuration might work.

If not, then you could also create a Network Load Balancer in Windows Server Roles/Features, containing the IP addresses of the 2 AOS instances. Then in the AX Client Configuration Tool on your SSRS instance, both the Local client and the Business Connector configuration needs to be changed to point to the Load Balancer's IP address instead of the specific AOS. Do not forget to refresh WCF configuration. After that restart the SSRS instance, and test if you could print with any of the AOSes down.

Was this reply helpful? Yes No
Suggested answer

pnwguy 245 on at

Like (0)

Report

Thanks Andre, this finally worked, our mistake was we were updating the Client connector, and not the Business Connector. Once we fixed the latter to include all our AOS, everything worked.

Was this reply helpful? Yes No
Vilmos Kintera 46,149 on at

Like (0)

Report

Good news for identifying the missing setup. Please make sure you mark all helpful answers as Verified, to resolve the topic.

Thank you

Was this reply helpful? Yes No
CBNestor 46 on at

Like (0)

Report

Can you tell me how you added all AOS list into the second instance? I am having the exact same issue as you

Was this reply helpful? Yes No