Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
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)
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.
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?
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.
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.
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!
Check out these blogs: Read the first paragraph of the first blog.
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!
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.
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.
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 :)
Check the all SQL Services or dependent services of AX which are running or not.
Business Applications communities