Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 2 virtual launch event
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 | Upcoming TechTalks
One of our French customers is having some strange errors in the event viewer every 25 minutes.
I don't know why because the session 65535 isn't listed in the online users.
Besides this error message, Ax is working perfectly. No issues have been reported by the customer.
I must admit that I've only started working in AX starting from version 2009 so might be overlooking something obvious.
Object Server Axapta: Dialog issued for client-less session 65535: Erreur d'exécution de code: Débordement de la pile d'exécution interne.
Suivi de la pile:(S) \Classes\xRecord\postLoad
Suivi de la pile:(S) \Classes\xRecord\Insert
Any idea's/suggestions would be welcome ...
Can you try to get at least the error messages in English?
This process might be a kernel process. Can it ve related to some batch processing?
I forgot to mention that they don't do any batch processing in AX, so you think this must be coming from the kernel then?
I did look for a translation and it would be : error executing code : stack overflow
The errors look quite strange, since xRecord is a kernel class. Some record manipulation seems to be failing.
Microsoft might already have a fix if it is a known problem for them, have you verified if your AX AOS and Client versions are on the most recent binary hotfix available for your specific release?
Maybe you could try to identify what processes are running at the time that the error message happens, to correlate it with a specific task (batch job running at that time, workflow, ad-hoc reporting, posting larger journals, etc.).
If that does not steer you in the right direction of identifying the problem, you should consider opening a support incident with Microsoft.
I'll start be checking the latest platform update ( binary hotfix ) available for AX3.
Opening a support incident will not be possible because AX3 is not supported any longer.
I'll get back to you once I've checked the binary hotfix option with the customer.
Since it is happening like every 25 minutes 24/7 and no batch processing is done, I think it will be quite hard to coorelate it with a specific task.
Might be the AOS that checks the cache of the tables or something like that.
I'll see if I can find any clues in that direction.
Try to stop AOSs, delete the AXAPD.AOI file in each AOS application folder and start the AOSs.
Are many year that I don't work with AX 3.0, but I remember something similar.
I will propose this solution because all other solutions failed.
The translation of the error seems to be "Overflow of the internal runtime stack", which means that you have a loop of method calls, which runs until the runtime runs out of all space on the stack.
The first message mentions postLoad(), so I would review all customized postLoad() methods to see if I can't spot anything suspicious. The same could be done with insert() (mentioned in the latter message), but postLoad() is overridden less often, therefore it's a better starting point.
By the way, SP4 is really old; I believe it's what I worked on already more than twelve years ago. Installing the latest kernel rollup and application service pack for Axapta 3.0 sounds like a good idea to me.
Business Applications communities