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
I suggest you to verify if the Oracle Database Maintenance Tasks are enable.
Also, try to check the memory used by the AOS service.
The posting problem is the same also after the AOS is restarted
how to check memory used by the AOS service.
You can run Task Manager on the AOS' host, find ax32serv.exe process and check its memory (private working set) consumption. In Axapta 3.0 an AOS cannot use more then 2 Gb; in fact it used to crash at about 1.8 Gb.
Axapta 3.0 actually runs Object Server Manager (ax32mgr.exe) process as a Windows service, and that in turn spawns AOSes as child processes.
Business Applications communities