Connection with AOS cannot be established Event ID 110

(0) Share

Report

Posted on by Community Member

Hi, we are getting intermittent errors with our clients connecting to an AOS server.

They connect through a terminal service app and after around 48 hours we receive calls that they can no longer connect, either receiving a black screen/the AX client dropping out or an error on screen:

Logon error: connection with the application object server could not be established.

I can RDP into the AOS server and open the client on that machine ok. Connecting to a terminal server and opening the client drops out the same as the Terminal clients.

The terminal server shows the following event id error:

The description for Event ID 180 from source Microsoft Dynamics AX cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Microsoft Dynamics AX Business Connector Session 3.

RPC exception 1726 occurred in session 3 process is Ax32.exe thread is 12392(User: $2EE5, ClientType: GUI)

Microsoft Dynamics AX Business Connector Session 3.

RPC exception 1726 occurred in session 3 process is Ax32.exe thread is 12392(User: $2EE5, ClientType: GUI)

The AOS service is showing no event errors. I have ensured the clinet/server versions are the same Ax 2012 CU 6 and checked over networking etc.

Has anyone experienced this before? We are looking at having to roll back to a non production system and contacting Microsoft directly but it would be fantastic if anyone has a fix we can try.

Thank you.

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

fsilva-jr 20 on at

Like (0)

Report

Hello Kelvin!

When you say "terminal services app" do you mean the "Remote Desktop Services" or some other application like Citrix?

How much servers do you have?

Do you have firewall enabled or even anti-vírus installed in your servers?

Was this reply helpful? Yes No
Suggested answer

Denis Macchinetti 16,444 on at

Like (1)

Report

Hi Kelvin

I suggest you to install the last Kernel Update according with your AX version.

Take a look at blogs.msdn.com/.../overview-of-ax-build-numbers.aspx

Additionally, try to refresh your AXC configuration file.

So, open the Dynamics AX Configuration Utility, go through Connection Tab and press the Refresh Configuration Button.

Press Apply and save again the configuration.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi,

We have tried the following:

Reduced the terminal servers down to one machine to focus on a fix. (other environments accessed from this server work ok, we use several for testing etc). The AOS is a single machine.

Disabled anti virus on both the terminal server and the AOS.

Ensured that firewalls are turned off on both machines.

We have refreshed the AXC configuration on the AOS and used this file.

I have deleted ALL AUC files from user local directories and I have reset the GUID in syssqmsettings to force a rebuild on client cache.

I have changed the AXC server setting on the AOS to use it's IP address rather than PC name to rule out any DNS issues.

I have used telnet to test the ports for the AOS connections etc between the machines ok.

As usual, we have rebooted all systems including SQL etc.

We have just discovered that this issue is also in our Production environment (it only has the one environment). So we believe it is a config issue that has gotten past testing.

Was this reply helpful? Yes No
Suggested answer

fsilva-jr 20 on at

Like (0)

Report

What about the Terminal Services configuration from the TS server? Is it configured to end users sessions?

And the Power Configuration of your TS Server? Is it configured for High Performance and for not to turn off the display?

Little details, but importants!

Was this reply helpful? Yes No
Jacqueline Olson 641 on at

Like (0)

Report

Kevin,

Check out these blogs: Read the first paragraph of the first blog.

http://blogs.msdn.com/b/rds/archive/2007/09/28/terminal-services-remoteapp-session-termination-logic.aspx

http://technet.microsoft.com/en-us/library/cc753112(WS.10).aspx

You want to make sure when user disconnect from their AX session by clicking the 'X' on the top right corner of AX application, their remote session is also logged off - using group policy.

Hope above helps!

Jackie

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi everyone, thanks for the replies.

We have been able to remove terminal services from the issue, looks like it is ANY machine that is remote to the AOS.

Now looking into a possible DNS issue, which would explain why some users could connect but not others as there are multiple DNS server settings on each AOS.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Kelvin, did you ever find a resolution for your issue at that time? I'm looking at the same issue and currently going through some of the steps provided in this thread.

Thanks,

Jared

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Jared, we eventually got it down to:

- If the terminal server was physical it would fail.

- If the terminal server was virtual it would work.

We opened cases with Microsoft Business and our cloud hosting company but after 8 weeks no one was able to find a root cause for the issue.

We have since replaced all our terminal servers with virtual machines, the aos's/sql etc all run on physicals. From the information we gathered the physicals were running on blade servers and the virtuals all run on vmware esx hosts.

We pulled the nics apart on the physicals and tried everything we could think of, we even spent a week gathering as many debugs/logs etc as needed for Microsoft but no one was able to resolve the issue. It came to a stalemate with our hosting company saying it was a Microsoft issue and Microsoft saying it was due to the hosting company's cloud architecture but as a business we needed to move on so went with the work around.

Hope this helps in any way and if you ever find the cause please let me know :)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Check the all SQL Services or dependent services of AX which are running or not.

Was this reply helpful? Yes No