Common Problems In DYnamics Axapta & Solutions

• We have found that in a number of AOS crash cases they are resolved by installing the latest kernel hotfix. Therefore it is recommended that you consider implementing the latest kernel rollup as part of your maintenance. This could mean applying the latest kernel rollup once a quarter. Since the kernel hotfixes are cumulative, easy to uninstall, and do not include X++ fixes they are typically able to be installed with a lot less effort than an application hotfix. We do recommend that you apply the kernel rollup in a non-production environment and do some testing before applying it in your production environment. Please see the information from the AX Kernel Patching section on how to update to the latest kernel hotfix rollup.
• If you implement code when users are in the system you could have cache or data access issues that result in an AOS crash. Therefore, when implementing code in your production environment it is recommended that you do so when users are not in the system. If you are going to import an xpo make sure that you shut down all but one AOS during the process. You may also want to consider then shutting down that last AOS, deleting the axapd.aoi file, and restarting one AOS so that the axapd.aoi file gets rebuilt.
• Verify that all of your Microsoft Dynamics AX components are on the same build. We have found that if there are rpc call changes in a kernel build and a machine is inadvertently missed during the Kernel hotfix install that it can result in AOS crashes.
• If possible separate each AOS by process/component. So for example if you use Dynamics AX clients, Enterprise Portal, and you heavily utilize batch processing you could have each of these connect to its own AOS.