web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

AX Client Very Slow

(0) ShareShare
ReportReport
Posted on by 452

Hello everyone,

We are facing a strange issue, AX client is very slow over some period of using the client, it is almost inaccessible beyond a point. but when we log the same user to server through RDP and restart the client again the speed becomes normal.

Clearing cache files does not help.

We do have a Complex Infrastructure, with Two Virtual Machines in cluster with Four Load balanced AOS. 

SQL server is also in Cluster, and separate SharePoint server.

 

The slowness is the most when trying to access Documents which are stored in DB for some file formats and SharePoint folder for some formats.

I would like to know  what happens when You  are accessing AX  in the  AOS server machine and a client.

Also we are using a Configuration file to access the clients.

 

Please advice on how can I troubleshoot this.

 

thanks

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Iulian Cordobin Profile Picture
    8,201 on at

    So, the slowness in the AX client application is happening to only one user? Or is it a general problem for all the users? Also, I understood correctly that the users are opening the ax client on their laptops using an .axc file?

    If sounds like you are running out of memory on the client, when working long times in the AX client. Opening documents from Sharepoint also adds an extra burden on the device itself.

    The question of what happens between the client machine and the AOS is rather simple: a communication channel is being opened and maintained to allow the data to flow between the two components. Although it is a rather old protocal (RDP) it should not cause such behavior on its own.

    I would suggest you look into the devices resources, and see if they come near depletion.

    Also, a final piece of advice: it is rather normal to close your client from time to time (on any devices) so it would clear the memory it occupies.

  • Karunakaran nainar Profile Picture
    452 on at

    Thanks for the response Lulian,

    I would like to add some more input on this,

    So, the slowness in the AX client application is happening to only one user? Or is it a general problem for all the users?

    It is a general problem for all users.

    Also, I understood correctly that the users are opening the ax client on their laptops using an .axc file?

    Yes, Users are using .auc  in their desktops

    But the issue occurs over a period of time say a month , and in this period they close the sessions everyday.

    I will check for the resources when we face this again, thanks

  • Suggested answer
    Brandon Wiese Profile Picture
    17,788 on at

    If you're serious about finding the root cause of this issue, you're going to have to start to divide and conquer the problem.

    Performance issues in a complex n-tier system like Dynamics AX are not always easy to figure out.  However, most performance problems related to some resource being severely constrained.  

    Most of the time the resource is either CPU, I/O, memory, or network.  In an n-tier system like AX, the resource can be either on the client machine (RDP server in this case), the AOS, or the database, and in some cases there can be quite a few machines in that mix.  In a virtualized environment, you have to consider the host(s) as well.  Yes, a host can have a severely saturated CPU and it will be felt by the virtual machines, and not be immediately obvious from any performance measurement done within the virtual machine itself.

    Because your problem seems somewhat random, start by setting up Perfmon to do standard logging to disk.  There are many good articles on technet regarding standard performance metrics to log.  This way if you can't figure it out while the problem is actually happening to you, there's a chance that enough information was captured that you can review it after the fact.

    You can gain some good clues by commonality.  For example, when one client is suffering, are others as well?  If so, what do they share?  Are they on the same Remote Desktop server, or are they connected to the same AOS?  Or, are they running reports that share the same data at SQL Server.  In each case, you can start to focus a little closer on a suspect machine based on how performance issues are shared among many users.

    Once you have figured out on what tier the problem lives, and what resource is constrained, you stand a good chance of solving it.  For example, if you knew for sure the problem was SQL Server and a poorly performing query, there are many ways to find, analyze, and improve the performance of SQL Server and specific queries.

    Start by ruling out what is not the problem until you understand better where it lies in your infrastructure or application.

  • Iulian Cordobin Profile Picture
    8,201 on at

    Ah, so it's a sporadic issue with a frequency not well defined. When this issue occurs, do you resolve it only by opening the clients on the server (as you mentioned in your first post), or you also restart other servers / services as well?

  • Karunakaran nainar Profile Picture
    452 on at

    HI Lulian,

    we don't restart any server, we just log the user in the server machine using rdp, we then close  the rdp.

    restart the client in the desktop now the speed is up.

    also I noticed now it is happening with only one department users ,  but there is no difference in terms of network connectivity with other users and this department users .

    HI Brandon,

    thanks for the reply , I would like to know would trace parser help in this case.

  • Brandon Wiese Profile Picture
    17,788 on at

    I didn't suggest trace parser at all, though that can be useful in specific cases.

    I suggested Perfmon to help narrow down the resource that is constrained and the machine on which it is a problem, both while it is occurring and even later in review using the logged performance data.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans