Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Users continuously experiencing slowness when switching between companies in AX.
The delay is in minutes and it is from both AX and Citrix clients.
But, when we tried to open AX instance from Server, the delay is just few seconds.
We are using AX2009-SP1 version.
Could anyone please help me to resolve this issue.
It could be related to many factors. It could be hardware, network latency, virusscan or others.
I have seen this kind of performance issues related to Citrix where also Citrix was virtualized.
If you have the ability for monitoring, look for indicators like Memory, Networking and also CPU. On the CPU watch for CPU wait times. If you have Multithreading on the CPU's the processes might wait on each other. Sometimes it is better to only use the physical cores of the CPU.
Further more, we used trace parser to analyse this issue.
Taken trace when opening AX and while changing company inside AX.
There were no user code and all the calls are to system/kernel classes.
During company change we got 2300 calls of ServerUtilLoad, there is no code to flush the cache yet it appears to be happening.
Do you guys have any idea about ServerUtilLoad?. Or Does any of Client/Server configuration setups calls the cache flush?
Thanks Dynamicspedia by André Arnaud de Calavon/UMESH PANDIT.
We have applied a hotfix for AIF time stamp issue, but this was done years ago.
Is it only for remote clients ? did you check it from LAN (which Server Connected to ) , do you experience in same when generating AX reports ?.
Amith Prasanna ,
This we are experiencing for all the clients.
We already looked into LAN connections and we found no issues.
Seems to it occurs because of band width.because in the LAN we have enough Bandwidth
(at least 100 Mbps).For to get clear understanding you can run network bandwidth Monitor for both LAN and (wan) remote clients PC.then you can compare band width utilization and confirmed that where is the Issue .there are so many bandwidth monitors you can find by simply with Google .
Let me clarify, the slowness is on most but not all clients. In all cases Client->Server is over WAN but ping time is 9ms and we have had no issues with this latency to date.
CLIENT1->SERVER. ChangeCompany (and initial login) are fast at ~3 seconds. TraceParser of client during CompanyChange shows 13 ServerUtilLoad calls (each takes ~9ms)
CLIENT2 (which is a TSS) ->SERVER. ChangeCompany (and initial login) are slow at ~30 seconds. TraceParser of client during CompanyChange shows 2,300 ServerUtilLoad calls (each takes ~9ms). AUC files are creating correctly on CLIENT2. Deleted and let AUC file recreate.
There seems to be something in both initial login and changecompany where CLIENT2 is invalidating and demanding a reload of a hug amount of objects.
http://dynamicsaxcloud.blogspot.co.uk/2012/12/dynamics-ax-trace-parser-quick-trace.html...refers to ServerUtilLoad : The kernel is caching metadata. If you see this it is more than likely that you are not analyzing a trace that was taken on a warm system. The kernel is building the caches and if you run the same trace again the cache building should not occur.
However the traces have been taken on a warm system - the traces were taken several times.
If you have a large number of security groups, and the user changing company is member of many groups, this is something that will significantly affect performance when you switch company and AX has to load the secuirity setup for that company. When reloading the security, a ton of statements go back and forth between client and server, that's is also why is seems faster when you do this on the server. Also if you try this as Admin you'll most likely only be member of one security group and that works as fast as expected.
Thanks Palle Agermark for your reply.
I belong only to Admin group.
I have tested for few other users as well, but the change company event is still slow.
Make sure your AX client build number is same as Server build number, i.e ax32serv.exe
Business Applications communities